Did latest steam update change TextMsg states too?
 

Wanted to double check my findings with you guys. I noticed that radio message trapping was broken for some reason (joebot + cs1.6/steam). I did a bit of logging and found the following:

CS1.5
1, #Game_radio
2, PlayerName
3, #Need_backup

CS 1.6
1, 7
2, #Game_radio
3, PlayerName
4, #Need_backup

It seems there's an extra beginning state for CS 1.6 (I think this is the player index).

Has anyone run into this finding or is this just old news and I'm late to the party? I really didn't notice this until recently and I'm wondering if it's because of a steam update.

Re: Did latest steam update change TextMsg states too?
 

I would prefer intercepting the menuselect command in ClientCommand() (like the POD-Bot). It doesn't need those strcmp()'s and may be much faster.

Re: Did latest steam update change TextMsg states too?
 

They did change a lot of things recently with the network messages. I wouldn't be surprised if it were so.