ThunderVote is a QuakeWorld server-side patch that makes map voting possible for any mod. It was first developed for TeamFortress but support for other mods can be made available. It uses the "sv_gamedir" command (included in QW since version 1.64) to have the server switch gamedir directories back and forth (thus allowing it to run the ThunderVote qwprogs.dat in between maps) but leaving sv_gamedir constant, so the client won’t be told to change gamedir every time.

1. Download the latest version of the ThunderVote mod (http://www.planetfortress.com/tvote/files/files.htm)
2. Unzip the files in a new quake subdirectory called /thundervote (it can be called whatever you like, as long as you change all references to the default "thundervote" gamedir in the .cfg files)
3. Move the files from the thundervote/themod directory to the server’s default gamedir directory (if it’s a TeamFortress server, put them inside /fortress)
4. If you want to have the server run ThunderVote when it starts, add this command to the server.cfg: "exec thundervote.cfg"
5. Set your own list of maps by editing the voting map’s entities (check the "ThunderVote Map Entities" section for details). The map will go inside thundervote/maps.
6. Define default settings for all maps in the standard.cfg and vote settings in the thundervote.cfg.
7. Make sure you enable settings on the mod you’re using to have it run ThunderVote again -- with TeamFortress, you can do so by including a "exec thundervote.cfg" line in qwmcycle/map1.cfg and setting qwmcycle/map2.cfg to do a "serverinfo n 0". See "TF-Specific Configuration" section and TF docs for more info.

This is the script file that has the voting configuration commands. It usually looks like this:

gamedir thundervote
sv_gamedir fortress // assuming it’s a TeamFortress game
localinfo min_votes 10
localinfo nuf_votes 20
localinfo min_approval 0.5
localinfo nuf_approval 24
localinfo min_time 1
localinfo nuf_time 3
localinfo no_since 5
...
map vote40

"Min" conditions

• min_votes: voting evaluation will not occur unless there is this minimum amount of votes. If it is assigned a value > 1, it assumes you are defining number of votes. If you assign a number between 0 and 1, it assumes you're defining a percentage of number of voters in relation to the number of players currently connected (i.e., a value of 0.1 = 10% voters, 0.67 = 67% voters, 12 = 12 voters). If unassigned or assigned a value of 0, evaluation can occur with any number of votes.
• min_approval: voting evaluation will not occur unless the map with most votes has at least this minimum amount of votes. If assigned a value > 1, it assumes you are defining number of votes. If you assign a number between 0 and 1, it assumes you're defining a percentage of number of votes for a certain map in relation to the total of votes. If unnasigned or assigned a value of 0, evaluation can occur whatever the approval.
• min_time: voting evaluation will only happen after a certain amount of time has passed since the first player arrived in the server (timer is reset if there are no players in the server). Value corresponds to # of minutes. If unassigned or assigned a value of 0, evaluation can occur anytime.

"Nuf" conditions

• nuf_votes: voting evaluation will occur if there are a certain number of votes. If assigned a value > 1, it assumes you are defining number of votes. If you assign a number between 0 and 1, it assumes you're defining a percentage of number of voters in relation to the number of players currently connected -- NOTE: using a percentage for nuf_votes can lead to undesirable premature results if a server starts and the first player that joins in votes immediately (resulting in 100% voters and therefore satisfying the condition).
• nuf_approval: voting evaluation will occur if the map with most votes has at least this amount of votes. If you assign a value > 1, it assumes you are defining number of votes. If you assign a number between 0 and 1, it assumes you're defining a percentage of number of votes for a certain map in relation to the total of votes -- NOTE: using a percentage for nuf_approval can lead to undesirable premature results if a server starts and the first player that joins in votes immediately (resulting in 100% approval and therefore satisfying the condition).
• nuf_time: voting evaluation will happen after this certain amount of time has passed since the first player arrived in the server (timer is reset if there are no players in the server). Value corresponds to # of minutes. If unassigned or assigned a value of 0, evaluation can occur anytime. If there is a draw, anarchy mode is enabled.

Evaluation occurs if at least one "nuf" condition is satisfied and there are no draws.

The STANDARD.CFG

This script file is executed before any map is chosen. It MUST have this line:

gamedir fortress // assuming it’s a TeamFortress game

timelimit 60 // whatever value you use for your maps
fraglimit 100 // whatever value you use for your maps
etc.

Mod-Specific Configuration

exec thundervote.cfg

serverinfo n 0

Rocket Arena and CTF

You must use special versions of these mods available in the Files section. Currently there are special versions of Clan Arena 1.3, Final Arena 1.2, Threewave CTF 4.1, Expert 1.31, ThunderWalker 5.0. They offer a simple added feature that allows them to be used with ThunderVote: the "exec_cfg" serverinfo key. Use it in the STANDARD.CFG to specify what script the mod should exec instead of changing levels, like this:

localinfo exec_cfg thundervote.cfg

Support for Other Mods

ThunderVote Map Entities

Map Candidate