Discord Map Vote

v4.23.1

Let players vote the next map in Discord — auto-applied on wipe.

Download DiscordMapVote.cs Full configuration →

Requires BigKidsCore — install it first.

Overview

DiscordMapVote turns a BigKids.pro Discord map poll into the next map on your server. You plan the wipes in your dashboard, the plugin fetches that schedule and runs it: it clears the save files at the right moment, applies the map your players voted for, and restarts — no launcher scripts, no cron editing by hand.

This website cannot wipe your server

A wipe schedule you build in the dashboard is a PROPOSAL. The plugin downloads it, shows you what it would do, and changes nothing until someone with access to the server console accepts it. Even if your bigkids.pro account were stolen, the attacker could not wipe you: approving is not something the website can do.

  • Nothing takes effect until you run mapvote approve in the server console. Until then the server keeps wiping by the schedule it already approved.
  • mapvote pending shows exactly what a proposed schedule would do — the rules and the dates they produce — before you accept it. mapvote reject throws it away. Both it and mapvote approve ask the site for the latest version first, so you never accept an older draft than the one you just saved.
  • Every command is console-only. There is no in-game permission to grant, so no admin rank and no stolen account can approve a schedule or trigger a wipe.
  • The plugin works out the wipe dates on your server, from rules cached on disk — timezones and daylight saving included. If bigkids.pro is down, or gone for good, your wipes still run on time.
  • The server holds a token that is only ever sent over HTTPS, is never written to logs, and can be revoked from your dashboard at any time.

Features

  • Wipes are planned in the dashboard — weekly, every N weeks or monthly.
  • Runs Rust's monthly force wipe (first Thursday, 19:00 London) — off, standing as a wipe of its own, or merged with a nearby wipe of yours. Your call, and you choose whether it clears blueprints too.
  • Tells the monthly, wipe-forcing update apart from an ordinary hotfix — restarts to install the real one and wipes on the next start; a hotfix in between gets a quiet restart of its own, no wipe warnings, no wipe.
  • The plugin computes the wipe dates ITSELF from the rules cached on your server - if bigkids.pro is down, or gone, your wipes still run.
  • Applies the Discord vote winner as the next map automatically.
  • Map wipe (world only) or Full wipe (world + blueprints), per wipe.
  • Voted map applied only at the wipe — never on a random restart.
  • The winner is downloaded hours ahead and parked on your server, so the wipe applies it without needing the site at that moment.
  • Move a wipe and the vote moves with it. Players choose the map of the next wipe, not of a date, so rescheduling never throws away a poll that has already run — or starts a second one for a map that is already chosen.
  • In-game countdown before every wipe.
  • Remembers the moment the save files were actually deleted and hands it to BigKidsCore — a wipe that failed is never reported as done.
  • Syncs Rust's own wipe timer (the Nuclear Missile Silo countdown) to your real wipe date.

Installation

  1. Install BigKidsCore first and connect your server.
  2. Drop DiscordMapVote.cs into oxide/plugins/ (or carbon/plugins/).
  3. Run oxide.reload DiscordMapVote — look for Linked to BigKidsCore.
  4. Check that Scheduled wipe → Enabled is true in DiscordMapVote.json (it is by default), then plan the wipes in your dashboard.
  5. That is it. After editing the schedule, run mapvote approve in the console — it fetches the latest version from the site first, so there is nothing to wait for. Left alone, an edit reaches the server within a minute and waits there for approval.

Commands

mapvote check Fetch the latest vote winner.
mapvote apply Apply the winner now (no-wipe mode).
mapvote wipe [map|full] Trigger a wipe now.
mapvote nextwipe Show the next scheduled wipe.
mapvote schedule List the approved wipe rules and the next date each one produces.
mapvote pending Fetch the latest schedule from the site, then show the one waiting for approval and the wipes it would run.
mapvote approve Fetch the latest schedule from the site and accept it - this is what arms the wipes. Lists what was accepted. If the site cannot be reached, accepts the one already waiting on the server.
mapvote reject Discard the waiting schedule and keep the approved one.
mapvote info Show the last applied map, the winner parked for the next wipe, and the current build and protocol.

FAQ

Do I need a launcher or panel script for wipes?

No. The plugin clears save files at startup before the world loads. You only need the normal restart loop every server already has.

Do clans survive a wipe?

Yes, by default — that is how Rust itself works. A clan lives on the server, not on the map: the clan table is destroyed with the world, but the name, members and roles stay, so nobody has to rebuild the roster after every wipe. If you would rather start a season with clans broken up, set <code>What the wipe deletes → Clans</code> to <code>full</code>. Everything the wipe touches is listed there, one line each, and each line takes <code>never</code>, <code>full</code> or <code>always</code>.

Will the voted map load on a normal restart?

No — with scheduled wipe on, the map is applied only at the wipe, never on an incidental restart.

What happens on a wipe with the map vote switched off?

Only the world is wiped. The map stays exactly as it is — a custom map you are running is kept, and no random seed is rolled. Turning the vote off for a wipe means "do not change the map", not "pick a random one".

Can the website wipe my server?

No. A schedule you build in the dashboard is downloaded by the plugin and parked - it changes nothing until someone with access to the server console runs mapvote approve. Even a stolen website account cannot wipe you: it has no way to approve anything.

Where do I plan the wipes?

In your dashboard, under Bot → Wipes. The site works out the exact dates (timezone and DST included), the plugin fetches them and computes them again on your server - and then waits for your approval.

What if bigkids.pro is unreachable?

Nothing stops. The plugin holds your rules on disk and works out the wipe dates on the server itself, timezones and daylight saving included, so it never depends on the site being up. The vote winner is fetched hours ahead and parked on your server too, so even a wipe during an outage still loads the map your players voted for. Only rule CHANGES you make while it is down arrive late.

What if the site is down and no winner was parked?

The wipe runs on time and the map is left exactly as it is. A random seed is only ever rolled when the site actually answered and told us the vote produced no winner — never because we could not reach it.

The server was offline when a wipe was due — what now?

A wipe is still run if the server comes back within 15 minutes of it. Later than that it is skipped, so you never get a surprise wipe hours after the fact.

Does the in-game wipe countdown match?

Yes. Rust normally derives its own countdown from wipetimer.wipeDayofWeek/wipeHourofDay (Thursday 19:00 London by default), which would show a wipe that never happens. The plugin overrides it with the exact date of your next wipe, so the Nuclear Missile Silo timer and the endgame events line up with reality.

See all settings in the documentation.

We use analytics cookies to measure traffic and improve the website.