My was going for this encounter last night, but we encounters some "unexpected" issues. After wiping once, his aggro range got insane and we couldnt even enter the room without pulling him. This meant that we could get in without having him AND trash up our asses and we pretty much had to give him up for the day. The aggro range was DEFINATLY not that long when we entered the room before our first attempt. Has anyone else encountered any such issues, and if so, did you manage to solve them/is it a known bug?
I think everybody's running into this problem. We got a few attempts in today with the small aggro radius (where you can wipe recover) but it'd switch to the big aggro radius and we'd have to run back and do the trash clear again after the soulstoned rezzer got killed. A couple times we'd get there and the aggro radius would still be big and he'd aggro before we even got in the room, and then after the wipe it'd be small again. No rhyme or reason one way or the other that we could tell. I just hope the large radius is the bug and small one is the way it's supposed to be, because doing that trash for a 10 second wipe is going to get annoying.
This seems to be a persistant problem with their game mechanics. When properties of the mob change during a fight they do not get properly reset. We had a a smelly wipe on viscidus last week where he was at 1% and had shrunk down to his tiny model. When we tried again his hitbox was still that of the tiny model even though his visual model had reset. Our tank was literally standing in the middle of him just to hit him at all. The hit box did not correct itself until after we killed some blobs and his hitbox was programmatically reset. I am sure it is the same fundamental issue with the aggro radii described in this thread.
Seems that a reset will reinitialize hp, mana, position, buffs/debuffs, character model and the aggro list but that other properties such as detection distance / hit box are not reloaded.