[chundo]

New version attached - if some of you brave ones could help test it a little before I release the next version, I would appreciate it.

Fixes/features since 0.4:

• sm_cvote is now an admin command. Users must now use !votemenu or vote chat triggers. Admins using chat triggers are treated the same as any other user; to launch a vote immediately they should use sm_cvote <votename> or the Voting Commands menu. Only votes that users can initiate directly (determined by "admin" vote parameter) will show up in !votemenu; votes requiring chat triggers don't appear there (yet).
• Deprecated "triggers" value in config file, added "triggers" section (still backwards-compatible). See playervotes.vote.cfg for an example. Available trigger parameters:

• "command" - the chat trigger keyword
• "delay" - equivalent to previous "playerdelay" parameter, which has been deprecated.
• "notice" - the chat message to display when a user types a trigger (only used if multiple requests are required to start a vote). "%u" is replaced with the player name. You can also use parameter and expression replacement. If omitted, will default to vote title (not desirable except for chat-type votes.)
• "count" - the minimum number of players that need to request a vote before it is launched.
• "percent" - the minimum percentage of players that need to request a vote before it is launched. If this number evaluates to be larger than "count", it is used instead.

• Chat triggers ignore the "admin" vote parameter. It provides a group-consensus alternative to requiring an admin to launch it.
• Added playervotes.vote.cfg to the default config directory, and moved basevotes/funvotes to "disabled" directory since most are duplicates of existing votes (the few new votes were moved into core.vote.cfg).
• Two new parameter types: "yesno" and "onoff". See "votealltalk" in playervotes.vote.cfg for an example.
• New vote type: "chat". If this vote type is used, you must define a "trigger" section, and users must vote by typing the trigger in chat. Once the trigger threshold is reached, the command is automatically executed. See playervotes.vote.cfg for examples.
• Added "sm_cvote_reload" command to check for config changes and add any new votes. Also executed on map change.
• Added "sm_cvote_resetonmapchange" CVAR which clears all pending votes on map change (as opposed to retaining the status of chat-votes like votekick, voteban, etc). Defaults to 0.
• Fixed vote status panel (sm_cvote_showstatus = 1) blocking weapon changes until it disappeared.
• If users close the vote status panel with "0", it will not reappear as new votes come in.
• Allows votes targetting users that have already disconnected (useful for voteban/etc.) A vote targetting the user must have been started before they disconnect, however. Disconnected targets should show up at the end of the player menu with an asterisk (*) before their name.

In theory this version has all the changes needed to support votekick / voteban from PlayersVotes (thanks to help from The Resident), and all existing base/funvotes. It also can support votemap easily enough, with the exception that it wouldn't have an "extend map" option.

If this tests well enough on some live servers I'll roll a 0.5 for release in the next couple days.

EDIT: posted 0.5 to main post, removed attachment.