I never noticed it before, but a player pointed out to me that they cannot see other players in warmode stance. They see themselves go into fighting posture, but not others.

Doesn't the core tell clients if someone is in warmode to change the animation? Tried this on v4 and v5 clients.

That's right, tested myself too (v5).

On the 097 RC5 core this bug does not exist. So, something related changed between 097 RC5 -> 097 2008-02-26?

Oh darn. And I am now on 097 2008-02-26 too......
Well too late, I need Ilshenar. It would be nice to get this fixed asap though.

Can a Dev please acknowledge they have this bug in the list?

BTW, nice to see you again Adam....

*BUMP*

Try this out if you dare: http://forums.polserver.com/sutra10912.php.

You don't sound too confident.
It *seems* to work on my test shard, but I am guessing you did that much too
Where did you figure out the 0x40 to AND with the status?

I did some testing on POL 097 RC5 and using results I got, did the conclusion and the packet hook script.

- If player is visible and in peacemode, flag is 0x00.
- If player is visible and in warmode, status flag is 0x41 (probably the +1 is because of core's warmode toggling, which, afaik, does not work like it should).
- If visible, mounted and in warmode, flag is 0x41 (no difference in the look, comparing to peacemode rider, but should there be any? I did not see difference on the RC5 server).
- If hiding or concealed and in peacemode, flag is 0x80.
- If hiding or concealed and in warmode, flag is 0xC1.
- If hiding or concealed, mounted and in warmode, flag is 0xC1 (again, no difference).

These are the documentations I based my scripts on. And so far tests show that things work like they should, but, I cannot say it for sure because I did not find anything besides mentioned test results I collected that claim how status flag really works. I just hope that +0x40 does the trick in every case.

waves at Madman and Luth and anyone working on the core.
Please don't forget this one.

Heh. Hi.

At some point when I have time I'll try to compile a list of the bugs in this forum. So hopefully we'll get to this one.

Its already fixed in core cvs.