Edit voting on an Arma 3 server allows players to collectively decide on critical gameplay factors, such as the next mission map or the current time of day, without needing a live administrator. This system promotes a more democratic environment by ensuring the active player base remains engaged with the content they find most enjoyable. However, server owners often restrict these permissions to prevent "vote-spamming" or disruptive changes that could interfere with organized tactical operations.

1. Log in to the BisectHosting Starbase panel.

2. Stop the server.

3. Select the Config Files tab and choose Server Config.

4. Navigate to the // === VOTING === line.

5. Edit the desired global settings. These settings are also used when allowedVoteCmds[] is not set.

• voteMissionPlayers = 1; - The value that determines how many connected players will start mission voting.
• voteThreshold = 0.33; - A percent-based decimal value that determines how many votes are needed to confirm the vote.

6. On the allowedVoteCmds[] = {}; line, delete the comment lines (//).

7. Input the desired vote commands within the curly brackets{} using the following format: allowedVoteCmds[] = {{<commandName>, <preMissionStart>, <postMissionStart>, <votingThreshold>}, ...};

Note: Invalid values will default to global settings.

8. Press the Save button.

9. Start the server.

How to Edit Voted-Admin Commands on an Arma 3 Server

1. Log in to the BisectHosting Starbase panel.

2. Stop the server.

3. Select the Config Files tab and choose Server Config.

4. Paste the following format in a new line at the bottom of the file:

allowedVotedAdminCmds[] =
{
  { "mission", true, true },
  { "missions", true, true },
  { "restart", true, true },
  { "reassign", true, true },
  { "kick", true, true }
};

5. Edit the desired voted-admin commands with the following format:
{ "commandName",    <pre-init>, <post-init> }

Note: Voted admin commands are not affected by server admins.

6. Press the Save button.

7. Start the server.