Open GoogleCodeExporter opened 9 years ago
Found the following written up by Vittu in early 2006:
https://forums.alliedmods.net/showthread.php?p=205071#post205071
-----
That was an old form of custom map configs, using mapcycle like a server.cfg
(though I think server.cfg would overwite if it had the same cvars as in the
mapcycle).
Essentially it worked like this:
map_name "\servercvar\value"
For example:
de_dust "\minplayers\4\maxplayers\12\sv_alltalk\0\mp_
friendlyfire\1\mp_timelimit\45"
In the above example. What minplayers and maxplayers do is when the map changes
to that map in the mapcycle, it will check if there are between 4-12 players.
If there are not, it will go to the next map in the mapcycle that will allow
the amount of players that did not fit in that range. And so on and so on until
it finds something that will allow the amount of players. (Both parameters are
not required) Again I have no idea if this still works and I'm not gonna bother
testing. I know this is still used in NS, usually to skip less popluar maps in
the mapcycle if there are not enough players playing.
-----
Probably a good idea to follow an already established, if not deprecated,
standard when adding "per map" features to Galileo, like is being asked in this
issue.
Original comment by jones.p....@gmail.com
on 22 Dec 2010 at 2:34
If testing confirms that mods ignore information in quotations after the map
name, that'd be an optimal way to modify map list files (i.e. mapcycle.txt) so
as to not be a problem if someone modifies their file to take advantage of
Gal's per map features and then uninstalls Gal. The idea is that they could use
the same file they had marked up as the mods won't choke on the extra
information.
Original comment by jones.p....@gmail.com
on 22 Dec 2010 at 2:36
[deleted comment]
Accidentally closed wrong issue. Reopening.
Original comment by jones.p....@gmail.com
on 20 Jan 2011 at 7:37
Original issue reported on code.google.com by
jones.p....@gmail.com
on 19 Dec 2010 at 4:04