[isotonic]

Introduction ;)
It was requested here. I took original Super Mapchooser v2.0 plugin well-known in Russia and rewrite about half of code to bring new functionality and to improve. It was not so easy task. I spent 16 hours ;)

Description
It is simple plugin for limit-based next map vote with one key feature and some effects.

Key features
Vote for next map occurs at the beginning of the last round. Screen is faded, players are frozen and vote begins… and some other effects. See screenshots.

Key improvements from v2.0
- true ML support
- pcvars
- support for round-based limits

Attention
My version of plugin is suitable for CS 1.6 only but not for CSDM, GunGame or other mods that are don't have rounds in general. It is because it relies on rounds.
Plugin requires AMXX nextmap base plugin (nextmap.amxx).

Notes
Plugin manipulates with mp_timelimit of map to make sure that last round will be and will be completed.

In case of ANY map management plugin if you have option 'extend map' you SHOULD restore mp_timelimit value using one of 2 methods:
1. Recommended Create such record into server.cfg file:
mapchangecfgfile mapchange.cfg
Then create text file named mapchange.cfg in the same folder. Then put into that file cvars that should be restored after EACH map change. I mean true HLDS cvars which are exist with AND without AMXX presence.
2. Put such cvars into amxx.cfg file.


Cvars
amx_extendmap_max - base AMXX cvar, default 90 minutes;
amx_extendmap_step - base AMXX cvar, default 15 minutes;
amx_vote_answers - show what players voted for, 1=yes, 0=no, default 1;
mapchooser_votetime - delay between when vote starts and when votes are tallied, default 15 seconds;
mapchooser_votemaps - how many maps offer for vote besides 'prolong current map' option, from 1 to 8, default 5 maps;
Color for vote results in RRRGGGBBB format, where RRR, GGG, BBB - numbers from 0 to 255, def. 000 255 100 - light green:
mapchooser_result_red RRR - red component;
mapchooser_result_green GGG - green component;
mapchooser_result_blue BBB - blue component.

Credits:
TRUE RED - for the idea and testing the plugin;
fysiks - advices, eforie - ML.

--

Current version: v3.0 04/26/2012
The most recent changed files are attached directly.

[IMG]http://img252.**************/img252/7198/smapinfo.th.jpg[/IMG] [IMG]http://img844.**************/img844/5042/smapvote.th.jpg[/IMG] [IMG]http://img706.**************/img706/9791/smapresults.th.jpg[/IMG] [IMG]http://img85.**************/img85/2637/smapfinal.th.jpg[/IMG]

[fysiks]

Originally Posted by isotonic Attention My version of plugin is suitable for CS 1.6 only but not for CSDM. It is because it relies on rounds. Plugin requires AMXX nextmap base plugin (nextmap.amxx).

So, it ONLY supports rounds then? You should change the following:

Originally Posted by isotonic Key improvements from v2.0 - true ML support - pcvars - supports ONLY round-based limits

Also, I generally only get cvar pointers in plugin_cfg() so that there is no chance that the cvars don't yet exist (since it's possible that get_cvar_pointer() is called before register_cvar() if you have them both in plugin_init()'s).

One cool thing that I learned:

You can change this:

set_hudmessage(_,_,_,_,_,_,_,_,_,_,2)

to this:

set_hudmessage(.channel=2)

[isotonic]

Thank you for your contribution! I moved get_cvar_pointer() to plugin_cfg() and simplifyed set_hudmessage.

But plugin doesn't support rounds ONLY. In 'Key improvements from v2.0' I meant plugin still checks timelimit but now also checks maxrounds & winlimit. And it relies on rounds in that sense that vote start and map change are triggered by 'Round Start' and 'Round End' in case if it is NOT round-based limit coming soon ;)
I'm ready to correct my short description if you help me to explain in English.

[fysiks]

Originally Posted by isotonic But plugin doesn't support rounds ONLY. In 'Key improvements from v2.0' I meant plugin still checks timelimit but now also checks maxrounds & winlimit. And it relies on rounds in that sense that vote start and map change are triggered by 'Round Start' and 'Round End' in case if it is NOT round-based limit coming soon ;) I'm ready to correct my short description if you help me to explain in English.

If it doesn't "ONLY support rounds" then why would it not work on CSDM? You need to change one or the other.

[isotonic]

It is because CSDM or GunGame don't have rounds in general.

[GarbageBox]

Can player rock the vote?

[isotonic]

No, he can't.
If there will be enough people interested in it I plan to implement last round vote and effects in 'Custom Nexmap' plugin witch has both rtv and nominations features as well as extremely customizable nextmap votes.

[kiki33hun]

Lool, this is umm mapchooser copy!

[isotonic]

What? ;)

[eforie]

PHP Code:


[ro]
INTERRUPTED = Votarea este intrerupta!
VOTE_NEXT_ROUND = Votarea pentru noua harta se face la inceputul rundei urmatoare.
VOTE_TITLE = Voteaza pentru urmatoarea harta
PROLONG = prelungire
PROLONGED = prelungit
VOTE_STARTED = Vot pornit!
MAP_EXTENDING = Votare terminata. !nAceasta harta este prelungita pentru !t%.0f!n minute.
MAP_EXTENDING_HUD = Aceasta harta este prelungita cu %.de minute.
NEXT_MAP_CHOSEN = Votare terminata. !nUrmatoarea harta: !t%s.
NEXT_MAP_CHOSEN_HUD = Urmatoarea harta: %s
LAST_ROUND = Ultima runda! Harta se va schimba la sfarsitul rundei.
LAST_ROUND_HUD = Ultima runda!
VOTED = !t%s!n voteaza pentru !g%s.
VOTED_EXTEND = !t%s!n voteaza pentru !gmap extindere.
VOTE_RESULTS = Rezultate voturi
VOTE_TOTAL = In total au votat: %d din %d