[Release] Votemap plugin

[zhp0083]

zhp0083, please source.
thanks.

added

Thank you I need source to traslate it (spanish)

enjoy

[sanjivsharma1975]

Working perfectly fine on tg.

Feature Request: Should have voting for game modes also

Thank you OP

[zhp0083]

Working perfectly fine on tg.

Feature Request: Should have voting for game modes also

Thank you OP

yes, it's already in schedule, but there is still a problem i dont know there is a rcon command in game or not? who can tell me ....thx

i known what it was....will add mode vote in next release

[sanjivsharma1975]

There are two things I understand.

1. Voting for a new map with !vm <name of map> command.
2. Voting for the nextmap (in the cycle) with !vn command.

No. 1 above should change the map immediately..ok i agree.
However, the No.2 Command is for nextmap so it should store the Nextmap voted in, and wait for the map timelimit to finish; and then change the map. It should not immediately change the map - you know but at the end of timelimit

PS: They both solve the same purpose, in present form

[zhp0083]

1.3 released

[divvy]

how do you add admin also i want to disable vote for game type only maps

[sanjivsharma1975]

1.3 released

Thanks for the update man. It is working perfectly.

However, you should change the style/structure of voting a little bit (if it is possible ).

1. Users should be able to vote only for NEXTMAP AND NEXTMODE and NOT CURRENT map or CURRENT mode. (The result of voting should be stored and wait till current timelimit ends.)
2. The NEXTMAP and NEXTMODE should change only when the current map's timelimit finishes.
3. Only Admins can change the CURRENT map or CURRENT mode or fastrestart immediately. (!map, !mode, !fr - which you have already given)

You have given Admins the command !nm to change map to next. What is the use of this command when the users can vote for any map and the map changes automatically (after 5 seconds); if you can understand what I mean.

Basically voting should be divided into two important HEADS.
a. NEXT MAP/MODE (for users and admin only)
b. CURRENT MAP/MODE or FASTRESTART (for admins ONLY)

Your current plugin is creating confusion in context of NEXTMAP voting. (ideally Nextmap means - after this current map. But your nextmap becomes current map in 5 seconds, after voting....please check this)

Once again...NEXTMAP and NEXTMODE <> CURRENTMAP AND CURRENTMODE
I hope i am clear.

PS: I have noticed, users keep on voting the nextmap and the current map changes and this way no one is able to play and use your Votemap plugin efficiently.

You can do this (i hope it helps)

Lets say Current Map is Mission and TDM. Users Start a vote for Dome and FFA. When this vote gets passed, Second voting should automatically begin. Change to Current or Nextmap?
The users can then vote !c for Current or !nm for Nextmap. Dome and FFA should get stored in a variable, which are used after this CURRENT MAP finishes.

[zraile]

source updated ? ur source not work with gametype support

[divvy]

why is every 1 admin? there no way of removing this?

[GrossKopf]

I would like to restrict the mode vote to only certain modes, or to disable the mode vote completely. Is there a way to do this?