If you try to write a string with MSG_WriteBitString that contatins characters whose code is >= 0x80 (f.e. Cyrillic), then 0xFF will be written instead of a needed characters. More on this described here: dreamstalker/rehlds/issues/150
The image shows the original MSG_WriteBitString function. We can see the type of the variable const char, which is the cause of the problem.
The solution is to use unsigned char *pch instead of char *pch.
The text was updated successfully, but these errors were encountered: