This is on TF2.
I have been having a issue recently with people spamming the extend map vote/sv_vote_issue_nextlevel_allowextend cvar, with the result that I have seen map times of over 2200 minutes, driving everyone off the server. To counter this, I set the cvar sv_vote_issue_nextlevel_allowextend 0 to remove the extend map vote from the list, but the vote option is still there and works. Then we disabled sourcemod/metamod entirely to confirm there is no interaction, and vote extend still works. In other words, no matter if sv_vote_issue_nextlevel_allowextend is set to 1 or 0, it functions as if it is set to 1/enabled all the time. I then tried setting it in the launch command line just to see if there was some timing issue (+sv_vote_issue_nextlevel_allowextend 0) with the same result. Any ideas? Or am I using a cvar that is known dead. I did a search and only found problems with other source games like insurgency, but not TF2. My vote cvars: sv_vote_issue_nextlevel_allowextend 0 //Allow players to extend the current map? Defaults to 1 (enabled). sv_vote_issue_scramble_teams_allowed 0 //Can people hold votes to scramble the teams? Defaults to 1 (enabled). Everything else is default
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
