End of map voting for next map #145

Closed
opened 2015-09-07 10:18:47 -07:00 by GoogleCodeExporter · 0 comments
GoogleCodeExporter commented 2015-09-07 10:18:47 -07:00 (Migrated from github.com)
Attached patch extends the map rotation code and adds cvar g_mapRotationVote

End of map voting shows a vote menu to players after the intermission
scoreboard but before the server changes to the next map. Voting is done
with the attack (down), repair (up), and vote (F1) keys.

No client side changes are needed, this is done by abusing CenterPrint text.

* cvar g_mapRotationVote: number of seconds to show end of map vote menu
(default 15).

* maprotation.cfg additions:

A map rotation entry with the map name '*VOTE*' will start a vote for the
next map. Place the maps to include in the vote in brackets following the
*VOTE* line, it should look something like this:

mapRotation1
{
map1
map2
*VOTE*
  {
  atcs
  pushcannon_b3
  volcano
  ethereal
  karith
  tremor
  niveus
  nexus6
  }
map3
*VOTE*
  {
  voteset2map1
  voteset2map2
  }
map4
}

In this example map1, map2, map3, and map4 are always played. There are two
places where the next map can be voted.

A maximum of 8 maps can be included per *VOTE*, and are displayed on screen
in the same order as in the cfg file.

If no one votes, the first map will win.


* non-pqvm authors, this patch also depends on the patches for g_msg
(issue#50) and g_welcomeMsg (issue#118) to already be applied.

Original issue reported on code.google.com by Rez...@gmail.com on 11 Jul 2008 at 9:30

Attachments:

``` Attached patch extends the map rotation code and adds cvar g_mapRotationVote End of map voting shows a vote menu to players after the intermission scoreboard but before the server changes to the next map. Voting is done with the attack (down), repair (up), and vote (F1) keys. No client side changes are needed, this is done by abusing CenterPrint text. * cvar g_mapRotationVote: number of seconds to show end of map vote menu (default 15). * maprotation.cfg additions: A map rotation entry with the map name '*VOTE*' will start a vote for the next map. Place the maps to include in the vote in brackets following the *VOTE* line, it should look something like this: mapRotation1 { map1 map2 *VOTE* { atcs pushcannon_b3 volcano ethereal karith tremor niveus nexus6 } map3 *VOTE* { voteset2map1 voteset2map2 } map4 } In this example map1, map2, map3, and map4 are always played. There are two places where the next map can be voted. A maximum of 8 maps can be included per *VOTE*, and are displayed on screen in the same order as in the cfg file. If no one votes, the first map will win. * non-pqvm authors, this patch also depends on the patches for g_msg (issue#50) and g_welcomeMsg (issue#118) to already be applied. ``` Original issue reported on code.google.com by `Rez...@gmail.com` on 11 Jul 2008 at 9:30 Attachments: - [qvm_pq_svn66_rotation_mapvotes.patch](https://storage.googleapis.com/google-code-attachments/p-g-qvm/issue-145/comment-0/qvm_pq_svn66_rotation_mapvotes.patch)
Sign in to join this conversation.