Quote:
Originally Posted by jolanar
[You must be logged in to view images. Log in or Register.]
I'd guess they know about it but just for whatever reason can't get the coding to work right, maybe a titanium client issue.
|
No reason why it would be a client issue. The only things about FD and sneak that are client-side are the way they make you immobile and self-snared, respectively. Everything about aggro is purely server-side.
Unless the devs decided to do something radically different, when you successfully FD you are taken off the mobs' hatelists and put into their separate "FD memory" lists. Then there would be certain events where a mob will check its FD memory list and maybe remove players from it (time based, when they reach their spawn point, whatever). And when you stop feigning, FD memory lists would be checked to decide if stuff should aggro you again.
It's unlikely that sneak would interact with the FD memory list at all unless it is deliberate. The only other thing I can think of its the code mistakenly calls a function that should only be used for proximity aggro when trying to add a player that was on the FD memory list back to the hatelist, rather than adding them back to the hatelist more explicitly. Which would make the process look like this:
- FD'd player stands up
- Player is removed from mob A's FD memory list
- Mob A tries to aggro the player, but the player is behind them and sneaking, or they are out of LoS, so it is blocked.
- Player gets away scot free.
when it should probably look like this:
- FD'd player stands up
- Player is removed from mob A's FD memory list
- Player is unconditionally added to mob A's hatelist with some amount of aggro (either the initial proxy aggro amount or a remembered value, whatever it's supposed to be).
But that would be both a really obvious mistake and really easy to fix.