[Carl Sagan]

Vote Blocker

Version: 1.3.4
Last updated: November 6, 2014

Special thanks to McFlurry and CrimsonGT.
I learned a lot from their plugins, Vote Manager 3 and Vote Guard.


Click the logo above to join the steam group!

Description:

Our servers needed a simple plugin that wasn't over the top and would be able to block certain votes to stop griefers, so I started working on this.
I expanded on the idea and added vote-kick immunity to replace an older plugin we were using.
Admins with the ban flag can also use sm_veto and sm_pass for votes currently taking place.

Features:

• Optional auto-updating! Please install the cURL extension and Updater plugin!
• Block players from calling whichever votes you want.
• Block spectators from calling votes (admins with the ban flag bypass this).
• Gives vote-kick immunity to players with the reservation flag (also immunity for tanks, if desired).
• Option to enable/disable any of the above features
• Admins can bypass blocked votes
• Logs blocked votes to vb_log.txt in sourcemod/logs
• Allows admins to sm_veto or sm_pass a vote currently taking place
• Respects immunity levels for admins

Cvars:

They're self-explanatory so I won't go into much detail. Check the autoconfig file for an explanation of each cvar.
You can edit VoteBlocker.cfg in left4dead2/cfg/sourcemod to permanently change these cvars (after the plugin is run once).

• vb_version

0 - Enable this feature, 1 - Disable this feature

• vb_enable (Default 1)
• vb_log (Default 0)
• vb_respectimmunity (Default 1)
• vb_adminimmunity (Default 1)
• vb_tankimmunity (Default 0)

0 - Allow this type of vote, x - Only clients that match one or more of these flags can call this vote (more than one flag is not necessary, use z to completely lock out the vote except for admins with root access)

• vb_spectatorvote (Default b)
• vb_kick (Default 0)
• vb_returntolobby (Default b)
• vb_changealltalk (Default b)
• vb_restartchapter (Default 0)
• vb_changemission (Default 0)
• vb_changechapter (Default 0)
• vb_changedifficulty (Default 0)

0 - Disable blocked vote limit for clients, n - Maximum number of blocked votes per client per map before they are kicked

• vb_blockcount (Default 3, kicked on third illegal vote)

Installation:

1. Place voteblocker.smx in your sourcemod plugins folder
2. Enjoy!

To Do:

• Nothing!

Changelog:

1.3.4 (06-Nov-2014)
	- Changed some formatting
	- Added comments throughout the source

1.3.3 (10-Sep-2014)
	- Added auto-update functionality
	- Adjust admin-flag overrides directly in cvar instead of admin_overrides.cfg
	- No longer lower the case of vote strings, instead making the comparison case insensitive
	- Removed option to kick client when a certain vote is called as it could be abused

1.3.2 (08-Jun-2014)
	- Fixed issue with multiple messages being sent to admins
	- Added cvar to block spectators from calling votes

1.3.1 (04-May-2014)
	- Added cvar to set maximum number of blocked votes per client per map
	- More specific chat messages regarding blocked votes
	- Added cvar to respect immunity levels
	- Added cvar to block kicks against tanks

1.3.0 (29-Mar-2014)
	- Added option to block additional votes
	- Added cvar to enable/disable logging
	- Condensed cvars
	- Limited number of blocked vote messages
	- General cleaning up of code

1.2.1 (09-Feb-2014)
	- Added pass and veto admin commands
	- Fixed bug where caller name didn't show properly

1.2.0 (31-Jan-2014)
	- Added config file for cvars
	- Added a log of blocked votes

1.1.1 (17-Jan-2014)
	- Changed color scheme

1.1.0 (15-Jan-2014)
	- Added cvars
	- Added kick immunity for admins

1.0.0 (06-Jan-2014)
	- Initial release.

Downloads:

• voteblocker.smx

Source:

• https://github.com/psbj/vote-blocker

[Mr. Man]

You might want to add a CVAR that makes banning/kicking after toggling lobby votes an option instead of being mandatory.

[Carl Sagan]

Originally Posted by Mr. Man You might want to add a CVAR that makes banning/kicking after toggling lobby votes an option instead of being mandatory.

That's a good idea.

[Carl Sagan]

Updated to v1.1!

Added kick-immunity for admin-flagged players as well as a few cvars to enable/disable features.

[Powerlord]

I find it odd that's you'd block the vote for players who want to, you know, leave your server. Here's hoping L4D2 supports the blacklist better for its matchmaking than TF2 does.

[Carl Sagan]

Originally Posted by Powerlord I find it odd that's you'd block the vote for players who want to, you know, leave your server. Here's hoping L4D2 supports the blacklist better for its matchmaking than TF2 does.

You're misunderstanding here. What happens is people join our modded servers and call a vote to return to lobby even though we already have a game going on to grief.

We're not stopping people from leaving our servers. Not sure what you mean by that.

[s.m.a.c head]

did not work I have returntolobby "c" and still players can call the vote ?

I put
vb_enable | Default = 1
vb_returntolobby | Default = 1
vb_changealltalk | Default = 1
vb_kickimmunity | Default = 1
vb_changealltalkkick | Default = 0
vb_returntolobbykick | Default = 1
vb_kickimmunitykick | Default = 0
in the server.cfg

"vb_returntolobby" = "| Default = 1" ( def. "1" ) min. 0.000000 max. 1.000000
ss_added
- 0 = Disable, 1 = Enable

did not work +(

Originally Posted by Powerlord I find it odd that's you'd block the vote for players who want to, you know, leave your server. Here's hoping L4D2 supports the blacklist better for its matchmaking than TF2 does.

Its a common vote that griefers use after it passes they then leave, but no need to explain what someone does on the server THEY PAY FOR if you dont like it you know what to do.

[Dr. Greg House]

Originally Posted by Carl Sagan You're misunderstanding here. [...] We're not stopping people from leaving our servers. Not sure what you mean by that.

No, he is not misunderstanding. Not only can't people call a returntolobby vote anymore thus trapping the entire lobby into staying on this server, you also kick those people by default without any warning.

This should not be allowed and might even violate the Policy Of Truth by forcing players to stay on the server if they want to play with those people, although they don't like the server for whatever possibly justified reason (this plugin for example).

[Dr. McKay]

Originally Posted by Dr. Greg House No, he is not misunderstanding. Not only can't people call a returntolobby vote anymore thus trapping the entire lobby into staying on this server, you also kick those people by default without any warning. This should not be allowed and might even violate the Policy Of Truth by forcing players to stay on the server if they want to play with those people, although they don't like the server for whatever possibly justified reason (this plugin for example).

Players are always free to leave a server at any time. I can understand why you'd want to block the "return to lobby" vote on a server that's modded and doesn't use lobbies in the traditional sense.

Forgive me if I'm wrong, as I don't play much L4D2, but it sounds like people are joining a server that doesn't use lobbies and relies on server browser joins, as with other games. People are coming onto this server and calling votes to return to the lobby, which disconnects all players. The only reason to call this vote on such a server would be to grief, and kicking the player is an appropriate response.

Of course, I could be totally wrong.

[Dr. Greg House]

Originally Posted by Dr. McKay Players are always free to leave a server at any time. I can understand why you'd want to block the "return to lobby" vote on a server that's modded and doesn't use lobbies in the traditional sense.

This kicks those people by default. If you want to kick an "admin" you don't know of, you get kicked.
You don't play L4D, so I'll try to explain the situation: There's a slot of servers using plugins with the same functionality, you join them from lobby by random, you have a bad ping, the server is bugged, there are other mods you don't agree with (perkmod, etc.) and the 8 people are all trapped on the server. Now you can leave as one person, yes, but the lobby itself breaks apart and it is oftentimes very difficult to find the same interesting lineup of players as pubs, or even get a full lobby. To sum it up, it is incredibly frustrating.
Server owners abuse this (actually do this on purpose rather than "abusing") to keep their servers full.