25 aggro limit

[bodom]

maybe this could be removed from instances, ldon's specifically. the reasoning is if i crash a zone that only me and my party can be in, i haven't affected anyone else. plus now it takes 4 times as long to do a slaughter ldon.

another thing that might be considered is the arch mage event in pofire. i'm fairly certain he spawns over 25 adds in that fight. i could be wrong, i've never counted, but i know there are a lot of adds.

[Brontu]

o Arch Mage Yozanni's script reworked. More entertaining and won't trigger the anti train code anymore.

thats from the update a few days ago.

i would like to see it removed from instances myself but after talking wtih mikuz seems like its gonna stay a general serverwide issue 8(.

[Lillu]

Yep, please keep reading the server updates or at least search the forum before posting. AM script was fixed long ago for this particular reason.

About the agro limit. It's already been explained that it's for server stability. If you crash a zone, it might not affect anyone else but you..AND the server itself, resulting in lag, instability and malfunctioning.

[bodom]

well i'm sure they know what they're doing, although i have no clue what the benefit is. personally i've pulled 60+ mobs in slaughter type ldons and never had a single crash. come to think of it, i've done the same in FG and PoV and never had a single crash there either.

[bodom]

yeah i could see how crashing a zone several times could affect the whole server, i've just never witnessed a zone crash. and i've pulled some pretty big trains

[kaelee]

Arch Mage is Broken now.. he goes invul when first adds pop and then stays invul when they are killed. he only then takes dmg from DS and pets. after what seemed like forever with pet doing all the work, second set spawned. We killed those he still stayed invul.

[Mikuz]

Fixed, I forgot to change it to the new diviners ID's specifically for the event so other trash diviners in the zone could not trigger his invul, should work as intended now.

[Thenrin]

Thank you SO much for the warning messages!!!
I know that some times I will go over, but at least it won't be a big surprise now, and I can effectively manage the number of mobs

[Grey]

Its pretty helpful since most zones got a pathing face lift awhile back.
I was messing around in seb and agro chained almost the whole top part of sebilis onto me down in the crypt.
The warning was nice, let me know when I had to push some dps to keep from being expelled from the zone.

[Muck]

If this was implemented for server stability, I can't wait to see a change in server stability. Crashing on atleast 4/6 boxes each time I zone, if I had changed clients I could see this being related, however I didn't. I finally got tired of logging my boxes back in, thinking it would help but now I can zone twice, three times if I am lucky without crashing and this is with just 1 window open.

I understand the reasoning behind the aggro limit, it sucks but if it is hurting the server it's understandable. It's also understandable why everyone is against it though, for obvious reasons. If the server became less laggy and resulted in fewer crashes I would think people would have no problem sacrificing 15 more minutes per ldon. I just don't see any difference, yet..

I would generally let it go without commenting but the constant crashes are beyond frusterating.