Lord leaving the keep

[Dunmar]

How can the destro lord just get aggro when we are fighting to enter the first floor, run out of the entire keep and oneshot the entire order wiping an entire siege?

If it is AOE that provokes him how come destro has never aggrod an order lord out of the keep who would oneshot them? This is ridicules and very frustrating that an even siege battle ends before we get into the first floor because the NPC lord decided to wipe the entirety of order.

[Rydiak]

- Keep lords can now be fought on both the bottom and top floors. However, if he is moved away from his designated floor, he will get a stacking enrage bonus until placed back on his floor.

It was a recent change with the last patch.

And I was at that fight. There was only a slightly above-zero chance that Order was getting into that keep even without the lord being pulled and then aggroed by the healers. Destro had a picture-perfect bottom-floor funnel. Maybe the new mechanic needs some tweaking as far as maximum range the lord can be pulled (I heard he was out in the courtyard towards the outer wall at one point), but at least the new mechanic is indeed working and a lord will contribute in a meaningful way to the defense of his own keep.

[Dunmar]

Idk if you saw it or not but he left out the door and went on a rampage outside the keep and ran halfway through his courtyard. I was close to the front gate watching that whole thing unfold.

I honestly don't think an NPC that already takes forever to kill rushing out of the keeps to oneshot 2 to 3 warbands solo and never resetting is not the healthiest mechanic.

Not a single destro went outside while he was doing his onslaught, they all stayed inside while the lord did everything solo

[Natherul]

This is currently intended and we are discussing internally if something needs change or not.

[Easysteps2]

I was there too but didn't see it. No one on order meant to aggro the lord (that I could tell). Losing that many players changes everything. We were very close, it made a huge difference.

I like that he enrages if someone pulls him out of his room, but I think he needs to leash back to his room when he leaves the keep. That's how it used to work before.

[Easysteps2]

It happened again today, in Troll Country. I'm not sure why this is "intended", we weren't even close to attacking the lord and I doubt we could have even beaten the destro inside the keep.

In my raid UI, I noticed lots of my WB dropping quickly. I turned around and there were 2 WBs dead outside the keep in only a few seconds. No destro outside, just dead bodies. The Lord just one shotted everyone. I wish I took a screenshot.

Is that the intended gameplay, where the lord just randomly kills 1-2 WBs outside of a destro keep?

[Natherul]

It is / was intended that if you pull him down there would be consequences yes.

However, we have made some changes that are pending that should alleviate some of this that is pending deployment.

[tefnaht]

It is / was intended that if you pull him down there would be consequences yes.

However, we have made some changes that are pending that should alleviate some of this that is pending deployment.

Keep with open gate and stalemate on 1st floor, someone on second floor get DoT with AoE tick, go to Lord, Lord pulled by DoT sender, Lord run to him through 1st floor get some damage from AoE there, Lord has long list of targets and we have wipe out setup for attackers... It is not a pull on purpose. Simplest solution - if Lord has hp above 99%(probably 98%), Lord can't leave the 2nd floor room.

[Nameless]

It is just not fun to being one shotted by barely done anything so this intended concept is not good imo. Got one shotted by lord by randomly healing out of group so kinda meh

[Rubius]

Hotfix has gone live which prevents the Lord from triggering their enrage state until 98% - so should be no more random Lords wiping entire warbands while they try to push into keeps in the first place, etc.

If additional issues appear even with the 98% requirement, please continue to let us know and we'll keep our eyes on it for possible future updates.