Configure Map Votes
Similar to a map cycle, map voting puts the server on a continuous loop of games, but it also gives players the option to choose their next game. The map vote is also non-volatile (it’s saved to a file, thus retained when the server is reloaded), and you can edit map votes as they’re being played.
You can hide map voting entries if there are too many or not enough players. This will only hide entries, thus the number of votes displayed will be reduced.
Note: Make sure your map vote covers your entire possible range of players. If SAPP cannot find a game that can be loaded with the current number of players, the minimum or maximum player count may be ignored when picking the next game.
Note: Enabling map voting will disable a running map cycle.
To set up map voting, you can edit your mapvotes.txt, or use SAPP’s map votes commands. This is how each line in mapvotes.txt file is formatted:
map:game variant:name:minimum players:maximum players
| Command Usage | Effect |
|---|---|
|
mapvote [enabled] |
Enable map voting at the end of each game. Default: false |
|
mapvote_add <map> <game variant> <name> [minimum players] [maximum players] [index] |
Optionally, the minimum players and maximum players can be added (by default they’re 0 and 16, respectively), and the game can also be inserted at a certain index, moving games at the index and afterwards after the index. |
|
mapvote_del <index> |
Delete a map vote entry. |
|
mapvotes |
List map votes. |
| max_votes [count] |
This is the maximum displayed votes per round. However, if your map voting requires a certain number of players, then there may be less votes displayed if these games are unavailable. Default: 5 |