Sit aggro

[casdegere]

Is this still a question at this point? There is definitely a separation between live and P1999 as far as Sit agro and faction hits.

[Colga]

Over the past couple of days, I have made some errant pulls and informed my party to just let me die (warrior so no FD). So the party does nothing, and the mobs will run to them if they're sitting down.

This definitely isn't right since the party shouldn't even be on the agro table. Example, I was pulling an Orc Centurion from the tents in CB to my party at the bridge by trainer hill, and accidently grabbed 3 legos. I died at the tents, and the pull ran all the way around by the cabin to the bridge to kill my party who was just sitting down.

I didn't start playing EQ until Dec 99 so maybe this was "classic" for March 99, but it sure as hell isn't Kunark mechanics. I had to play ghetto monk many times when I would screw up a pull in KC/Seb.

[fadetree]

It's not classic. Sit aggro is putting pc's on the wrong list.

[Ofaelol]

In East Commons, I've accidentally trained orc camp groups by running to close to them with my wolves, spiders etc. They do not touch the mobs, but are sitting and aggro when mobs that I've damaged path too close.

[Swish]

Originally Posted by Colga [You must be logged in to view images. Log in or Register.]

Over the past couple of days, I have made some errant pulls and informed my party to just let me die (warrior so no FD). So the party does nothing, and the mobs will run to them if they're sitting down.

This definitely isn't right since the party shouldn't even be on the agro table. Example, I was pulling an Orc Centurion from the tents in CB to my party at the bridge by trainer hill, and accidently grabbed 3 legos. I died at the tents, and the pull ran all the way around by the cabin to the bridge to kill my party who was just sitting down.

Seems fishy to me. I took a faction hit the day after the supposed fix from just sitting near drolvargs being killed in KC (ungrouped). For those preserving their faction that'll sting if it happens too often. Maybe something got patched in but sit aggro still needs a tweak :s

[You must be logged in to view images. Log in or Register.]

[Yumyums Inmahtumtums]

Originally Posted by Swish [You must be logged in to view images. Log in or Register.]

Seems fishy to me. I took a faction hit the day after the supposed fix from just sitting near drolvargs being killed in KC (ungrouped). For those preserving their faction that'll sting if it happens too often. Maybe something got patched in but sit aggro still needs a tweak :s

[You must be logged in to view images. Log in or Register.]

Iirc that should happen if you sit around max-kos NPC's. You get added to their agro list as a result of being close regardless of whether you engage. It's broken if you get added to the agro list when the mob is non-kos to you.

[Colga]

Originally Posted by Swish [You must be logged in to view images. Log in or Register.]

Seems fishy to me. I took a faction hit the day after the supposed fix from just sitting near drolvargs being killed in KC (ungrouped). For those preserving their faction that'll sting if it happens too often. Maybe something got patched in but sit aggro still needs a tweak :s

[You must be logged in to view images. Log in or Register.]

I thought it was weird, too. Now I tell my friends just to stand up when I give my incoming message. Kind of a pain in the ass for the casters, but we have to make lemonade with the lemons until it gets fixed.

[Tzeriel]

Just gonna say. This sit aggro is NOT classic, it IS stupid, and it IS making playing a caster on this server not fun at all.

[Volkier]

Originally Posted by Yumyums Inmahtumtums [You must be logged in to view images. Log in or Register.]

Iirc that should happen if you sit around max-kos NPC's. You get added to their agro list as a result of being close regardless of whether you engage. It's broken if you get added to the agro list when the mob is non-kos to you.

I've worked on a crap tonne of factions in 99's and 2000's playing EQ. And I don't ever remember having someone else screw my faction up just by me sitting near where they kill a mob, or near where they pathed a mob and killed it. Don't know about max KOS, but people have had faction hits from mobs which where threateningly (though I don't really haven't been in a situation where this would have been possible in the last few days since the advertised fix).

Point is, if the P99 devs like the change and want to keep it - that's great, it's their project, their server, and ultimately their decision. But can we please quit lying and pretending this somehow resembles "classic" ? To be fair, it does feel like it's being tweaked, but with that it feels like all that the tweaks are doing, is decreasing the sit aggro range instead of fixing the actual sit aggro problem. So you still have the same broken mechanic - just within a lesser radius - which is not really fixing anything imho.

[Flip]

I am more curious as to why this was ever considered to be placed on P99 in the first place.

I came to play on P99 due to the overwhelming attempt the staff has made on preserving the integrity and game play of the original classic EverQuest. As many have already mentioned, the amount of threat that sitting now generates was never this high on live, at any given point.

So really, what was the main reason for doing it?


~Flip