Just a thing I suggest you developers to think about, when the protocol will be changed for any other reason (I suppose this may imply a protocol change, but it is not enough to justify a protol change all alone... but maybe, at the same time of other changes...)
: I was wondering if it could be possible to enlarge the space available for the "sets" variables (those the server admin can use to give informations about his server -very useful-, see also http://openarena.wikia.com/wiki/Command_console#Set_variables
I have done some tests, and at the moment, it seems to me too easy to hit that limit! I haven't calculated exactly
how long a single variable can be, and how many characters the info string can contain before you get "info string length exceeded" error when starting your server or using the "serverinfo" command, but the proportion seems unfair anyway: I think that the info string should be able to contain some variables at their maximum lenght....
I don't know what that change would break about compatibility (third party server browsers, external tools, mods...), but please try to think if it is worth of spending some time.
There are many server settings that would be nice to set using "sets" (e.g. to allow people to know if special game options
are enabled or not, or to know server settings like sv_fps to be able to set their client in the best way to play there), but server admins have quite limited "sets" space available.
Or else, maybe better, it would be useful to invent a brand-new alternative system to let users know about server settings
like g_elimination, g_vampire, g_regen, g_friendlyfire, g_catchup, pmove_float, pmove_fixed, pmove_msec, etc. I would like to know if such features are enabled or disabled on the server, but at the moment it is not possibile, unless server admin uses "sets" with them (but there is little "sets" space), or I try to guess by myself while playing (quite hard for some of them, don't you think?).
In short, a new way (like a new client command, similar to "serverinfo", but with more/different data, populated with server settings chosen by the admin -how?- or maybe better, chosen by you developers talking with the community
) to know about game settings
. This solution would not have big network compatibility problems, I suppose, relying on a new command that maybe (if needed to avoid errors) could not be sent at all to old servers; anyway the system should be designed to allow to publish more variables in the future, as OpenArena will gain new features that will be controlled by new cvars.
If you think it would not bring too many compatibilty problems, maybe all such "public" variables could be integrated to the init string, to allow external tools to read them without updates from their authors, but if they expect for a maximum string lenght, it may cause problems, I fear...
At the moment, in theory server admins could use the message of the day
to inform users about some server settings, but it would be quite intrusive and would still rely on admins' good will (a problem that affets "sets", too).