Update - Friday December 15!! perma-aggro fixed?

GuildWars.com: "Fixed a bug that caused some monsters to remain permanently aggressive toward their targets."



aaaah thats music in my ears!! tnx a lot for that fix im gonna go and try it out right away ;P

Tested. Avicara guiles no longer chase you nonstop.

yey, that started getting annoying, everytime i went fow forest farming that mob b4 the forest always snuck up on me

Oh goodie. At least now I can rez my party without a crapload of monsters suddenly come at us from off the radar screen lol

if perma aggro was indeed a problem, that can be attributed to players not killing the monsters. it's not the ai's problem.

They also removed XP from guild scrimage matches

I guess the Devs were finally able to duplicate the problem.

Yea, noticed that. No more Survivor from scrimmages lol.

(apparently one of the maps had some sort of exploit where it was very very easy to get Survivor quickly, I never did it because I don't want Survivor but I was told about it from allaince mates)

That why it says "Bug Fixed" then is it?

Shame really, it was kinda fun trying to reapproach an area and have them come aggresively after you. I guess it'll make hit and run, whittle 'em down tatics viable in some situations as groups will go back into their non-aggressive pose after a short period of time.

That was a funny comment on a funny situation. Thousands of people experienced it imo, but the devs (the creaters of this wonderful game) couldn't duplicate the situation.

Anyway, thanks for the update Anet and the upcoming winter event.

also the attacks ob spirits are fixed too it seems like. if you kill the spirit fast enough before the mob comes back.

I would like to say sort of "un" tested. I made an ids run with a guildie, and when he ran past a group of 2 wise and a few other avicara, we picked up a permanent tail of a guile and wise. Maybe I just have bad luck, but i don't think it's fixed.

Elona mission bosses will still follow you forever and even move FASTER now than before..........wtf

Normal mobs will follow you half way across the map even after you drop the crystal and stop to let them finish casting their spells.

You mean you didn't test it? That's what "untested" means, you know. Perhaps what you meant to say was that your test rather debunked the previous tests?

**sigh** not fix yet.... basic IDS run.... had 2 follow for a bit and then another two follow me from the small passage towards the cave.. SS of all 4




**Edit...**
Greatlich,

uploading another pick. i tired to break the Casting lock. even ran back towards the portal. after afew attemps i just killed them =)

Picture 1. I let him cast Deadly swarm on me.
Picture 2. I RUN FOR THE HILLS!
Picture 3. Both dead. seems to solve the problem

That's not aggro lock... that's "casting-lock" been around forever... basically those Avicara Wise (note that these are mesmers who are in the middle of hexing you) you are the one dragging them around the map stop a bit, let them finish the hex and be done with them

I had something strange just now, a little different though... my hench party wiped, all but Aidan (sp?), The res countdown started and Aidan teleports with me to the res shrine (I think this is new in Nightfall) but here the funny thing: one of the ruby djinni I was fighting had apparently just finished casting Savannah Heat on aidan, so right when we all ressed we were hit by the spell. the caster of course was way out of range...

charr followed me across the entire map still and would not break aggro as I was clearing map, also ice golems and such were doing the same

Same thing happens in the Deep, e.g. if the tank goes to an enemy group, someone starts casting Maelstrom on him and he recalls back right in the middle of his own casters. Quite funny

The question is whether or not they still DO go back. I've been attempting Drok's runs, and the Guiles will go away after they finish that Deathly Swarm they just HAVE to cast maybe 5% of the time. Otherwise they'll continue to chase me across the map and spam me with it.

Haven't tried since the update, but it sounds like this wasn't fixed.