Addon Details

[img]http://www.ashbash1987.com/clansuite/clansuite_cv.png[/img] This is the first part of the ClanSuite series, called ClanVote. This aims to allow clan members to control the server, without giving all the clan members limitied admin priviledges. Each time that clan members want to change something on the server, then they can start a vote to change it, but only clan members will be able to vote for the outcome. The commands that they can vote for are editable via keygroup database files, which are easy to understand and maintain. [color=blue][size=16][b]Installation[/b][/size][/color] Extract the contents of the *.zip file into your [b]cstrike[/b] folder. Then add [b]es_load clansuite_cv[/b] to your autoexec.cfg, and restart your server. [color=blue][size=16][b]Using ClanVote[/b][/size][/color] To open the CV popup menu, say [b]!clanvote[/b]. You can then choose what command to execute, and what option to vote for. When done, all clan members on the server will receive a popup to vote Yes / No / Abstain on the request. If the vote passes (which requires over 50% of all possible votes), then the command will execute. Otherwise, it won't. [color=blue][size=16][b]Customising[/b][/size][/color] You will then want to edit the database files inside the [b]addons/eventscripts/clansuite_cv/[/b] folder. The first file you'll want to edit is [b]es_votemembers_db.txt[/b]: [code]"votemembers" { "STEAM_ID_LAN" //LAN { } "NEWSTEAMID" //Name { } "NEWSTEAMID2" //Name2 { } }[/code] In this file, add your current clan members with their Steam IDs. You can use comments like I do to keep track of which Steam ID is who's. Next, you'll want to edit [b]es_general_management_db.txt[/b]: [code]"general_management" { "sv_alltalk" { "name" "All Talk" "rcon" "sv_alltalk " "1" "On" "0" "Off" } "ma_balance" { "name" "Balance Teams" "rcon" "ma_balance" "1" "Now" } "sv_gravity" { "name" "Server Gravity" "rcon" "sv_gravity " "100" "Very Low" "400" "Low" "800" "Normal" "1300" "High" "2000" "Very High" } }[/code] The file supplied in the *.zip contains more examples of commands that you can add. You can add as many commands as you wish, making sure to follow this pattern: [code]"identifying_name" { "name" "Name of Command" "rcon" "console_command " "opt_var1" "Option Value 1" "opt_var2" "Option Value 2" }[/code] Each command must contain the [b]name[/b] and [b]rcon[/b] elements. Also note that for multiple-options, you should include [b][/b] in the rcon element, which is what will be replaced by the option value. All the other elements become the options that you can choose from (one option is required, but you can add as many as you want), with the first part being the variable that will replace [b][/b] in the rcon comand, and the second part being the option name that will be displayed in the menu. The es_general_management_db.txt file should contain commands that are not related to individual players. The [b]es_user_management_db.txt[/b] file is where you should put in commands related per player: [code]"user_management" { "ma_kick" { "name" "Kick Player" "rcon" "ma_kick " } "ma_ban_24h" { "name" "Ban Player (24-hours)" "rcon" "ma_ban 1440 " } "ma_ban_perm" { "name" "Ban Player (Permanent)" "rcon" "ma_ban 0 " } }[/code] Again, each command requires a [b]name[/b] and a [b]rcon[/b] element, and is required, as this will be replaced by the identifier for the player. No more elements are required, so if you want to do multiple options for commands like banning periods, you have to do them as separate commands at current.