New Rule: Flagging Hostile NPCs

[Shendare]

Apparently we could use the same change.

I just did some testing, and while a grey-con Level 40 hostile NPC will not attack a Level 75 character, it will attack its Level 2 pet, and then turn to the owner once the pet is dead.

Guard Legver glares at you threateningly -- You could probably win this fight.
Guard Legver hits Zarartik for 120 points of damage.
Zarartik has been slain by Guard Legver!
Guard Legver tries to hit YOU, but misses!
Zarartik tells you, 'Attacking Guard Legver Master.'
Guard Legver bashes YOU for 33 points of damage.

Also, pets can speak from beyond the grave. OooooOOOOOoooooh. Heh heh.

[ChaosSlayerZ]

hehe, but yeah this was a huge annoyance on LIVE, we realy need to get rid of it =P

[Shendare]

Grr. There's still a slight problem with this feature.

It does the proper processing when a player zones in, FillSpawnStruct(&ns, Client) gets called for the particular client entering the zone, so they get the customized version of the NPC's lastname.

However, any new NPC spawn packets that get sent to the client after zoning in don't get processed in the same way... the same spawn packet gets sent to all clients in the zone, so NPCs that spawn after zoning in, via normal respawn cycles or #repop, won't have the customized lastname.

I'll have to do a little more work before this is 100% functional.

I'll probably have to move the processing into the QueuePacket() function, and things will get a little more complicated.

[trevius]

Definitely an interesting option once the code issues are all worked out. Can you maybe just do an IsPet check before doing the case switch?

[Shendare]

The pet problem isn't actually related to this at all, I just noticed it while testing. An IsPet check isn't part of the hostile NPC flagging.