Temporary measures in AssaultCube
Since the recent intervention from the developers to bring back the game to its original standards, there has still been a lot of backlash from players of the infamous maps bs_*, bs_dust2, ezjem**, *gema*. We have produced a small patch to the sourcecode of the AssaultCube server, which prevents these maps from getting voted and played.
The patch is available here: map_blacklist.patch.
How it works: it's just like any other blacklist file reloaded periodically. To enable map blacklisting, you have to edit 'config/mapblacklist.cfg'. Every new line denotes a separate entry. The lines are loaded, and when a vote for a map is called, it will be refused if the map's name contains text from any of those entries. For example, if the file looks like this:
Then if 'bs_dust2_night' is voted, it will be refused. Same goes for 'DUST2' or 'GEMA-IMPOSSIBLE' and so on.
To use this patch, you need to know how to do compilation and patching yourself. I will not provide any binaries.
A ridumentary blacklist file is available here: http://woop.us/files/mapblacklist.cfg. You should re-download it periodically like any other blacklists you have.
Update: here are the instructions for UNIX users on how to patch their servers (with a new patchfile).
$ cd AssaultCube/source $ cp -R src src.orig $ cd src $ wget 'http://woop.us/files/map_blacklist.patch' $ patch -p0
Hope this clarifies things
For those curious ones
Even if you use the '-PX' switch, and have a list of official maps, there is a small workaround to actually get any maps to be played at the start of the game, and continue them to run repeatedly. As an example situation, you are not connected and load
/ctf bs_dust2. Then you connect to any empty server, even with the switch enabled, and your map will suddenly be loaded. This is because the server requests the name of the next map from the client or so.
Posted on Monday, 20th July 2009 by Drakas