cl_parsegamestate: bad command byte
that error seems to occur by some special maps ... btw u know www.google.com ? (or whatever the multilanguage domain is like )when u put in the whole errorline in there and press enter u will find ALOT of stuff which (helps) you there, how said this bug seems to occur by some spcial custom maps (also heared about maps which only run on windows servers ect)
So just remove that maps where it occurs on your server and it should be ok, if not go a bit deeper into the forums u will find @ google while searching for "cl_parsegamestate: bad command byte"
edit: sure u wont find anything about q3 directly but that doesnt matter ... the error is the same, if dod, q3 or cod
www.xyz.DE may help him a lot
lol i needet 5 secs to get what u mean ye ... true but i think @ google it doesnt matter if .de or .hassenichgesehn it will always redirect you to google site in your language
mm.. any thoughts ?
Found info.
Reconnect..
ET has a bit of a bug that can cause the client to attempt to send commands to the server before the connection is setup; the net result of this bug is that the initial data the server sends will be decrypted properly. The incorrectly decrypted data will still be interpreted, and will result in messages like 'configstrings > MAX_CONFIGSTRING', 'CL_ParsePacketEntities: end of message', or 'CL_ParseGamestate: bad command byte'.
You can mitigate the problem by making a conscious effort to avoid pressing any keys or mouse buttons (including the wheel) that result in commands being sent to the server (e.g. weapnext, weapprev) between the 'Awaiting challenge...' message and the actual level-loading screen.
The majority of people think they think, when really they just change their prejudices. Understanding is a matter of will in most cases.
☻ Lietuvių excessiveplus draugija - Lithuanians National Team
☺ Linux (1st E17+Compiz powered ! Built on Debian GNU/Linux.)
MODDB.com all cool things for Quake III Arena @ one place from E+