xVotemap v1.3.1

[ImportBot]

Originally Posted by Moli87*:

 

It wouldn't be too hard to put in that option but I think it's cleaner how it is, so that if you want to run maps for two rounds you can just have it set in the maplist to two rounds, otherwise just have one round set and it will call a vote every round.

 

Yes, as this is my first plugin and the only thing there is to work with is the small chat window, it is easy to be overzealous with the messages to start with. I've been toning back the default frequency values as the version progress. I have a few ideas on how to reduce the spamminess. I think I will add the nextmap command as it is the most effective way to get the information. However, for other users to find out about the command you must go back to the spammy messages. It's a vicious circle haha.

 

Once I get the majority of the functionality implemented I'll have time to tweak the interface to something more streamline.

 

Thanks for the support guys.

Hi

 

Ok im sorry i forgot that, that i can make 1 round in the maplist and then the plugin automatically works on the first round of a map. ;-)

 

but a command like @nextmap to disable the spam would be really nice. Anyway great work! thanks! ;-)

 

Greets

[ImportBot]

Originally Posted by Warwind*:

 

Hi

 

I have Exclude Current Map From Vote Options= True but it dosnt work! and my second problem is i have 7 Maps in the Maplist but the Vote Plugin shows every time the same 4 Maps for the vote ... it never shows the other maps.

 

Thx and greets

[ImportBot]

Originally Posted by Guy0510*:

 

I also have "Exclude Current Map From Vote Options_" set to "Yes" and it comes up as a vote option.

[ImportBot]

Originally Posted by Warwind*:

 

Oh sry it was my fault ... upps

[ImportBot]

Originally Posted by Guy0510*:

 

How are the four maps chosen for the vote? I've been running this full time tonight on a full server with 17 maps in the rotation. The same select few seem to come up in the vote over and over again. It isn't always the same ones but many are being missed and never show up in the vote.

[ImportBot]

Originally Posted by bordensize*:

 

Once bugs get cleared out of this plugin, a suggestion might be an adaptive vote option, such as if the player count is less than 15-20 or so, it's more likely that non-air maps like siene, metro, or bazaar will be on the list as long as they are on the servers maplist. Then the population is less likely to falter under lack of players on larger maps.

[ImportBot]

Originally Posted by teeth_03*:

 

or just have it setup with specific map lists depending on the amount of players

 

0-16 any map on TDM/SQDM

17-32 any conquest small/rush map

33-48 the smaller/non air conquest large maps

49-64 the biggest maps like B2K only

[ImportBot]

Originally Posted by HexaCanon*:

 

can we have an option in the settings where we can a specify a map or maps in the rotation that will never be voted for or shown in the vote list.

 

that is because i run emptymap plugin where a map is played only when the server is empty and i dont want player to have the option to vote for it.

[ImportBot]

Originally Posted by aether*:

 

I'd rather not convolute the votemap plugin with maplist settings based on players ect. I think the best option is to use this plugin in conjunction with another plugin that provides those features.

 

This plugin will only vote from the maps in the maplist. So a plugin which changes the maps in the maplist depending on player numbers or some other condition would work perfectly along side this. The idea is to keep it as simple and modular as possible. I'm not sure which of the other plugins offer the adaptive maps but it's a fairly simple task and if there isn't anything that offers this I could put a rough working model together quite quickly. Let me know.

 

 

There is currently a bug when the same map is placed in the maplist with two different modes. So I would hold off using it on mixed mode servers until I sort this out.

[ImportBot]

Originally Posted by HexaCanon*:

 

all i am asking for is setting like this :

 

Code:

map black list : MP_001 TeamDeathmatch0

this map will never be shown in the vote list even if it is in the map list

Code:

map white list : MP_012 ConquestLarge0 2 
                 MP_007 ConquestLarge0 2

these 2 maps will be played if the votes for a map did not exceed the threshold specified.

[ImportBot]

Originally Posted by aether*:

 

Why would you want a map in the maplist but not ever shown in the voting options?

[ImportBot]

Originally Posted by HexaCanon*:

 

Why would you want a map in the maplist but not ever shown in the voting options?

because i run TDM only when the server is empty. and i do not want to have 64 man TDM.

[ImportBot]

Originally Posted by Guy0510*:

 

because i run TDM only when the server is empty. and i do not want to have 64 man TDM.

So use this plugin ( www.phogue.net/forumvb/showth...-12-31-11)-BF3* )along side this one. It is called the Ultimate Map Manager.

[ImportBot]

Originally Posted by Guy0510*:

 

Can you give us the option to start the vote at a set ticket count of the losing team instead of using time?

[ImportBot]

Originally Posted by Zinoviev*:

 

I have not yet sorted out but it is a dream and not the plugin thank you!!!!

[ImportBot]

Originally Posted by Moli87*:

 

thanks for the command.

 

and a happy new year! ;-)

[ImportBot]

Originally Posted by Zinoviev*:

 

Can I do in the voting display mode, conquest or rush?

Thank you!

[ImportBot]

Originally Posted by Legate*:

 

It's weird, I set a 600 seconds to rush the vote but the plugin shows this:

 

 

[15:13:03 39] xVotemap Enabled!

[15:13:33 01] [xVotemap] Info: Estimated voting start in 4 minutes, 32 seconds @ 15:18:05

[15:13:38 76] [xVotemap] Info: Estimated voting start in 2 hours, 42 minutes, 39 seconds @ 17:56:17

[15:14:03 42] [xVotemap] Info: Estimated voting start in 47 minutes, 15 seconds @ 16:01:18

[15:14:10 20] [xVotemap] Info: Estimated voting start in 37 minutes, 39 seconds @ 15:51:49

[15:14:33 84] [xVotemap] Info: Estimated voting start in 26 minutes, 12 seconds @ 15:40:45

[15:14:40 93] [xVotemap] Info: Estimated voting start in 32 minutes, 44 seconds @ 15:47:24

[15:15:04 28] [xVotemap] Info: Estimated voting start in 7 minutes, 6 seconds @ 15:22:10

[ImportBot]

Originally Posted by Zinoviev*:

 

It's weird, I set a 600 seconds to rush the vote but the plugin shows this:

 

 

[15:13:03 39] xVotemap Enabled!

[15:13:33 01] [xVotemap] Info: Estimated voting start in 4 minutes, 32 seconds @ 15:18:05

[15:13:38 76] [xVotemap] Info: Estimated voting start in 2 hours, 42 minutes, 39 seconds @ 17:56:17

[15:14:03 42] [xVotemap] Info: Estimated voting start in 47 minutes, 15 seconds @ 16:01:18

[15:14:10 20] [xVotemap] Info: Estimated voting start in 37 minutes, 39 seconds @ 15:51:49

[15:14:33 84] [xVotemap] Info: Estimated voting start in 26 minutes, 12 seconds @ 15:40:45

[15:14:40 93] [xVotemap] Info: Estimated voting start in 32 minutes, 44 seconds @ 15:47:24

[15:15:04 28] [xVotemap] Info: Estimated voting start in 7 minutes, 6 seconds @ 15:22:10

I mix mode, so, everything works just wonderfully!!

http://i015.radikal.ru/1201/7d/8695bf7d5721.jpg

[ImportBot]

Originally Posted by Legate*:

 

Ok, the issue is the mix mode. thanks for the data Zinoviev.

 

aether, could be possible use a different list of maps to the vote (no the current mapcycle) ?

 

Good job ;-)

[ImportBot]

Originally Posted by Zinoviev*:

 

Ok, the issue is the mix mode. thanks for the data Zinoviev.

 

aether, could be possible use a different list of maps to the vote (no the current mapcycle) ?

 

Good job ;-)

If I correctly have understood you

www.phogue.net/forumvb/showth...-12-31-11)-BF3*

But itself put I know.

[ImportBot]

Originally Posted by Legate*:

 

My idea is a little bit different:

 

Use a normal mapcycle (ex. caspian CQ, Firestorm CQ, etc) but use another map list (ex. just B2K maps or rush maps, etc.) just for the vote.

 

Why this? it's simple: you can use the vote system to offer something different without force to the players to play it all the time.

[ImportBot]

Originally Posted by Legate*:

 

Another suggestion: start the voting when one of the teams has less than X tickets (very common on CS servers).

[ImportBot]

Originally Posted by aether*:

 

Another suggestion: start the voting when one of the teams has less than X tickets (very common on CS servers).

I avoided this as the rate at which the tickets decrease varies wildly in conquest. If one team is dominating the other there may not be enough time for a vote to complete. Or if the teams are close it may take 10 min more for the round to end.

[ImportBot]

Originally Posted by aether*:

 

0.0.7 Beta (03/01/12)

 

• Fix: Mixed-mode bug. Needs testing to check if it succeeded.
• Added: Customizable number of vote options.
• Added: Option to display the gamemode in the vote options.
• Added: Admins with mapchanging privileges can initiate/restart the Votemap in-game with /votemap.

[ImportBot]

Originally Posted by Legate*:

 

Could be as you say but using the time as the rate you can have similar situation: depend on the map, team skill balance, tickets, etc...

 

I think that the real issue using the tickets as the rate is on the rush mode.

 

BTW: I saw if a map won the vote, the map cycle follows his current position and no the normal cycle, ex.:

 

Normal cycle:

caspian

firestorm

G. Bazaar

Wake Island

 

 

Current map: firestorm

Won the vote: caspian

 

When caspian map starts I see on maplist that the next map will be firestorm (if it no one win the next map the vote).

 

After the won map, could be possible continue with the map on the next position when the the vote started? (G. Bazaar on the example).

 

 

Good job ;-)

[ImportBot]

Originally Posted by aether*:

 

I think that the real issue using the tickets as the rate is on the rush mode.

Rush is a bit of a bitch because there is no way for the plugin to know if an MCom has been destroyed (indicator of attacker's progress). So the attacking team may push and destroy all the Mcoms without losing many tickets so no vote would be called for that round.

 

BTW: I saw if a map won the vote, the map cycle follows his current position and no the normal cycle, ex.:

 

Normal cycle:

caspian

firestorm

G. Bazaar

Wake Island

 

Current map: firestorm

Won the vote: caspian

 

When caspian map starts I see on maplist that the next map will be firestorm (if it no one win the next map the vote).

 

After the won map, could be possible continue with the map on the next position when the the vote started? (G. Bazaar on the example).

 

Good job ;-)

Yes, I'll look into an elegant way to implement this.

[ImportBot]

Originally Posted by Legate*:

 

0.0.7 Beta (03/01/12)

•Fix: Mixed-mode bug. Needs testing to check if it succeeded.

Now works fine

 

•Added: Option to display the gamemode in the vote options.

Excelent (On my mapcycle Caspian can be CQ or Rush)

 

Great plugin

[ImportBot]

Originally Posted by Zinoviev*:

 

wow, I'm just mad glad this news!!!

will test!

Thanks for the excellent work!!!

 

 

now truly displays the mode!! It's a great, great fix!! Thank you!

[ImportBot]

Originally Posted by Legate*:

 

[10:11:50 29] [xVotemap] Info: Voting duration: 3 minutes, 55 seconds.

[10:11:50 68] [xVotemap] Info: Voting duration: 3 minutes, 56 seconds.

[10:11:51 39] [xVotemap] Info: Winning vote tie, random map selected as winner.

......

[10:11:51 64] [xVotemap] Info: Votemap failed. The total number votes (0) did not exceed the threshold (3)

[10:29:21 93] [xVotemap] Work: Round Over: Stopping voting system

[10:30:44 87] [xVotemap] Work: Level loaded: Last round detected, starting voting system

[10:32:24 90] [xVotemap] Info: Estimated voting start in 2 hours, 42 minutes, 39 seconds @ 13:15:03

[10:32:28 53] [xVotemap] Info: Estimated voting start in 4 minutes, 58 seconds @ 10:37:26

[10:32:55 31] [xVotemap] Info: Estimated voting start in 8 minutes, 47 seconds @ 10:41:42

[10:32:58 65] [xVotemap] Info: Estimated voting start in 14 minutes, 31 seconds @ 10:47:29

[10:33:25 75] [xVotemap] Info: Estimated voting start in 50 minutes, 55 seconds @ 11:24:20

[10:33:28 92] [xVotemap] Info: Estimated voting start in 2 hours, 42 minutes, 39 seconds @ 13:16:07

[10:33:56 18] [xVotemap] Info: Estimated voting start in 7 minutes, 27 seconds @ 10:41:23

[10:33:59 76] [xVotemap] Info: Estimated voting start in 4 minutes, 17 seconds @ 10:38:16

....

But the vote starts on time (Rush voting start time is set in 900 sec.)