Do I need BigKidsCore for other plugins?

Yes — DiscordMapVote and other BigKids.pro plugins go idle without it.

It’s stored only as a hash on our side and sent only over HTTPS. You can regenerate it anytime in the dashboard.

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.

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 Discord 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. Only rule CHANGES you make while it is down arrive late.

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.

Documentation

Configuration and commands for BIGKIDS.PRO Monitoring Rust plugins. Get the files on the plugins page.

BigKidsCore

core v1.0.8 Overview →

BigKidsCore is the hub every BigKids.pro plugin connects through. It authenticates your server with one secure token, talks to the BigKids.pro API, writes the chosen map into server.cfg and reports live server status (heartbeat). Install it once — feature plugins won’t run without it.

Settings

Setting	Default	Description
API base URL	https://bigkids.pro	Base URL of the BigKids.pro API. Must be https.
Server token (from your bigkids.pro profile)	—	Your per-server token from the dashboard. Sent as a Bearer header over HTTPS.
Heartbeat interval (minutes)	30	How often the server reports status (min 5 minutes).

Commands

bigkidscore info	Show core version, API version and connection status. Server console only.
bigkidscore heartbeat	Report to the site right now. Server console only.

Discord Map Vote

v4.11.0 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.

Settings

Setting	Default	Description
Check interval (minutes)	30	How often to poll the API for a new winner.
Auto-apply	true	Apply the winner when a vote finishes (ignored while Scheduled wipe is on).
Scheduled wipe → Enabled	false	Turn the wipe scheduler on.
Scheduled wipe → Re-fetch the site schedule every (minutes)	30	Safety-net full refresh of the rules. Minimum 5 minutes.
Scheduled wipe → Check for schedule changes every (seconds)	60	Tiny "did it change?" poll, so an edit in the dashboard reaches the server within a minute. Minimum 30 seconds.
Countdown warnings	[60,30,15,5,1]	Minutes-before-wipe broadcasts.
Restart delay (seconds)	30	Delay before the restart that applies the wipe.
Random seed if no winner	true	Roll a fresh procedural seed when a wipe asked for a voted map and there was no winner. A wipe with the map vote switched off never touches the map - it keeps the one you are running.
Scheduled wipe → Require mapvote approve before a new schedule takes effect	true	A schedule from the website is only a proposal until someone with console access approves it. Leave this on: it is what stops a stolen website account from wiping your server.
Scheduled wipe → Sync the in-game wipe timer	true	Point Rust's built-in wipe countdown (wipetimer.wipeUnixTimestampOverride) at your next wipe, so the Nuclear Missile Silo laptop and the endgame events follow the real date.

Example (DiscordMapVote.json):

"Scheduled wipe": {
  "Enabled": true,
  "Re-fetch the site schedule every (minutes)": 30.0,
  "Check for schedule changes every (seconds)": 60.0,
  "Countdown warnings (minutes before wipe)": [60, 30, 15, 5, 1],
  "Restart delay after wipe (seconds)": 30,
  "Roll a new random seed when a wipe wanted a voted map but there was no winner": true,
  "Sync the in-game wipe timer (Nuclear Missile Silo countdown)": true,
  "Require mapvote approve before a new schedule takes effect": true
}

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	Show the schedule waiting for approval, and the wipes it would run.
mapvote approve	Accept the waiting schedule - this is what arms the wipes.
mapvote reject	Discard the waiting schedule and keep the approved one.
mapvote info	Show the last applied map + status.