Vote Commands 0.2.0

Let players choose what happens next

Vote Commands lets players vote on server actions, then runs the commands assigned to the winning option. Offer a vote to skip the night, choose an event or settle a server decision. Create separate votes with their own choices, duration and chat commands.

• Start a vote as an administrator or run it at regular intervals.
• Show images, remaining time, vote counts and the player's selected choice.
• Run server commands or a plugin's no-argument hook when an option wins.
• Use five built-in interfaces, with no PimpMyCUI or ImageLibrary dependency.

Codefling download: VoteCommands 0.2.0 — native edition.

Five interfaces included

Choose Operations Console, Civic Ballot, Relay Grid, Arctic Council or Broadcast Panel for each vote. Operations Console is the default. Each template shows three options per page, with arrows for additional choices. Images are optional and retain their configured aspect ratio.

Prefer your existing custom layout? Select legacy to keep the UIConfiguration interface. The native edition includes these layouts inside the plugin; it does not load a custom PimpMyCUI Editor project.

The five images use sample vote data. Illustrated ballot topics show what you can build; the download does not supply maps or blueprint-reset functionality.

Configure Vote Commands on PimpMyRust

Import your existing vote files or start from a supplied example. Edit the settings, preview the interface and export the files for your server. Choose the native/stable version for the 0.2.0 download on this page.

Configure Vote Commands on PimpMyRust →

Installation and configuration guide →

Run your first vote

1. Install VoteCommands.cs. If the vote configuration folder is empty, the plugin creates a safe Example.json with winner actions disabled.
2. Join as a server administrator and enter /vote_start, then /vote in chat.
3. Grant VoteCommands.Example.Vote to the players who should participate. Choose an option and wait for the 60-second result.

Each vote is a separate file in oxide/config/VoteCommands/, not a section in one VoteCommands.json. The permission contains that file's name without .json. Use the corresponding configured directories on Carbon.

Choose the actions, not just the winner

Assign server commands or supported plugin hooks to each option. For example, the supplied skip-night vote uses env.time 6 when Day wins; Night leaves the time unchanged. Test actions before enabling them. Plugin callbacks take no arguments.

The ZIP includes four complete examples:

• Safe example: a manual three-option vote with all winner actions disabled.
• Skip night: let players decide whether to advance the time to morning.
• Next wipe's map: collect a preference; applying the map or seed is a separate administrator action.
• EventManager event: choose among events you have already configured in a compatible EventManager installation. This example needs EventManager and the optional supplied adapter; the core plugin does not.

Specialized examples start disabled. Review their settings and actions before enabling them.

Voting rules

Each player votes once per session. The highest count wins; a tie with votes selects the first tied option in configuration order. If nobody votes, no winner action runs. Automatic sessions continue on their schedule even when a session receives no votes.

Native vote starts are administrator-only. Reloading stops active sessions without winner actions and resets their schedules. The repeat interval is measured between session starts, not after the previous result.

Optional PimpMyCUI beta

Separate beta on PimpMyRust — not the native Codefling download above.

Want to redesign the voting window in the visual CUI Editor? A separate beta is available on PimpMyRust to verified Vote Commands buyers. Sign in, link your Codefling account and refresh your purchases to access it.

Explore the Vote Commands beta →

That edition requires the free PimpMyCUI plugin, installed separately. It has its own UI and voting settings. Install only one VoteCommands edition at a time; native configuration files are not automatically migrated. The Codefling download described above is the native 0.2.0 edition.

Compatibility and support

For Rust servers running Oxide or Carbon. Back up your configurations and language files before updating, and keep your customized votes. External commands and hooks require their owning plugins.

Codefling support · PimpMyRust Discord

The illustrated interfaces are offline previews with sample vote data over a Rust screenshot, not recordings of live voting sessions. Configurator images are software captures; decorative artwork is illustrative.