CoD 4 'nextmap' / 'vstr' Combination

[Jeff Wilges]

Hi,

     If I'm not mistaken, it seems that the 'nextmap' variable is
locked (perhaps hard-coded) to favor the value 'map_restart'. I'm
aware that 'sv_maprotation' is checked when the server's current map
ends, so that the next map can be determined from the list of game
types and maps that 'sv_maprotation' specifies. For large game type
and map variations, it is not possible to list all of the game type
and map information in a single string stored in a single variable
such as 'sv_maprotation' (unless the variable's static size was
increased, which I imagine would involve simply upping the size of the
array); with this not being possible (for us end-users), it might
instead be more convenient for us to try to use the 'nextmap' variable
to rotate through maps intelligently using the 'vstr' command and
several variables in a round-robin fashion. This does not seem
possible in the current server release, however, as 'nextmap' does not
seem to be checked with priority over 'sv_maprotation'. For instance,
even if 'sv_maprotation' is unset, 'nextmap' will not control what the
next map is; instead, the next map will be the current map,
indefinitely. Is there any way to use 'nextmap' in the way that I have
outlined above?

Thanks in advance for any information,

Jeff

EDIT:

     As I was typing this, I was notified by a friend that in a recent
patch you have upped the cvar size to 32 KB, which is ridiculously
large and likely solves this problem. I would, however, still like to
know if the 'nextmap' and 'vstr' combination will ever work in the
future, or if 'nextmap' has been tossed in favor of 'sv_maprotation'.