Aggro LOS fix (maybe..?)

[cavedude]

Aye, I'll merge it on TGC next reboot

[eq4me]

I always thought that LOS had something to do with aggro range. For example you could pull the single mob near the ladder from the Ghoul Suppliers room in LGuk when you aggroed him as soon as you saw him while climbing up said ladder. Climb to high and the whole room would come. But maybe something has changed since then.

[Congdar]

I'm not sure if this is a good thing. If you want to link mobs, you should use the perl way to do it instead of a world wide change like this.

[greggg230]

Originally Posted by Congdar

I'm not sure if this is a good thing. If you want to link mobs, you should use the perl way to do it instead of a world wide change like this.

I'm not sure I understand. This should be a world-wide change, as this is how MOBs should always act.

This has nothing to do with MOBs being linked in the sense that was implemented in Velious and later.

[Congdar]

I said i wasn't sure. It seemed to me that assist is already working.

[Derision]

In testing this I would concentrate in dungeons, if you haven't already done this, bearing in mind there
is no pathing for aggroed mobs.

E.g. If I pull a mob and there is a mob around the corner that can't see me, but is within assist range
of the mob I am pulling, with this change, the unseen mob will run straight at me through the walls.

Should this second mob itself yell for help while it is 'running through the walls', possibly through
another room filled with mobs, there may be a chance of a chain-aggro event which pulls a load of mobs
through the walls.

I've not tested this or studied the YellForHelp code, but it is just a thought I had while wondering why
things are coded the way they are.

[greggg230]

Originally Posted by Derision

In testing this I would concentrate in dungeons, if you haven't already done this, bearing in mind there
is no pathing for aggroed mobs.

E.g. If I pull a mob and there is a mob around the corner that can't see me, but is within assist range
of the mob I am pulling, with this change, the unseen mob will run straight at me through the walls.

Should this second mob itself yell for help while it is 'running through the walls', possibly through
another room filled with mobs, there may be a chance of a chain-aggro event which pulls a load of mobs
through the walls.

I've not tested this or studied the YellForHelp code, but it is just a thought I had while wondering why
things are coded the way they are.

That most likely would happen, but the aggroed mob would have to run through the wall and go into line of sight with a mob in another room or something, which seems like it would be pretty rare and pullers could adapt to it in those situations in which it does apply. Obviously, it'd be best to have pathing for aggroed MOBs and proper aggro code, but I think one out of two ain't bad right now. hehe

[BWStripes]

Originally Posted by Derision

In testing this I would concentrate in dungeons, if you haven't already done this, bearing in mind there is no pathing for aggroed mobs.

E.g. If I pull a mob and there is a mob around the corner that can't see me, but is within assist range of the mob I am pulling, with this change, the unseen mob will run straight at me through the walls.

Should this second mob itself yell for help while it is 'running through the walls', possibly through another room filled with mobs, there may be a chance of a chain-aggro event which pulls a load of mobs through the walls.

I have to say I love this change, brings back in some skill required to pull properly. At least enchanters will have something to do other than VQ/VoQ.

I will comment it does behave as Derision speculated, on TGC, particularly in a lot of new style zones (Luclin+). Some walls and doors are not treated as non-LoS. Vex Thal has a few nasty spots now. We've had 9 pull and 12 chains with what should have been straightforward pulls. Other zones like Griegs were nasty anyway, but this makes it almost unplayable in places.