blitzzz, on 26 January 2014 - 12:17 PM, said:
~[UTSC]Ape
P.S. ... Also, why not make it so that in g_gear we don't type what we want the server to omit from weapon/gear choices, but instead have it so that, we can type in the code for what we want to be allowed (thus omitting everything else)?
I can agree on this one. Though, programmatically, the math might be easier, we're talking about who is using the command here...humans. It seems far more intuitive that g_gear says, "What gear would you like to set," not, "What gear would you like to unset?" Precisely what the gear load out client side does. Why make this behave in reverse logic?
I haven't tried anything yet, but is g_gear smart enough to understand the old integer values along with the newer char* [] values? Or did we break all of the current server configs and mapcycles?
Second flag sound & server_info string length are some annoying bugs when you get to them. Also, can you reconsider the old callvote fix that strips ALL semi-colons from client command args? Still cannot type one in normal game chat. Lastly, when you disabled binds during radio menu, you broke binds like (bind e "ui_radio") for being able to close the window. Verrrrrry annoying when you are in a firefight and a wild finger hits the e key. One has to either find the xzero or escape key to remove the menu UI.
Thnx again for a great update,
-Flux