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.

My server's IP keeps changing. Will it show up twice?

No. On first start the core makes up an id for the server and keeps it in oxide/data/BigKids/Instance.json ( carbon/data/ on Carbon). The site recognises the server by it, so a new IP or a new Steam id after a restart keeps the same entry and the same wipe schedule. Deleting that file makes the site see a new server. bigkidscore info shows the id.

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 What the wipe deletes → Clans to full . Everything the wipe touches is listed there, one line each, and each line takes never , full or always .

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.

Documentation

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

BigKidsCore

core v1.9.3 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, connection status and this server's id on bigkids.pro. Server console only.
bigkidscore heartbeat	Report to the site right now. Server console only.
bigkidscore mapdata	Re-read this world's ore, plants and player spawns and replace what the site holds. Server console only.

Discord Map Vote

v4.23.1 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 the winner when a vote finishes (ignored while Scheduled wipe is on)	true	Apply the winner when a vote finishes (ignored while Scheduled wipe is on).
Scheduled wipe → Enabled	true	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.
Scheduled wipe → Countdown warnings (minutes before wipe)	[60,30,15,5,1]	Minutes-before-wipe broadcasts.
Scheduled wipe → Restart delay after wipe (seconds)	30	Delay before the restart that applies the wipe.
Scheduled wipe → Restart automatically when Facepunch releases the monthly update	true	When bigkids.pro sees a new Rust server build on Steam, the server warns players and restarts so your panel installs it — the force wipe then runs on the next start. Turn it off to restart by hand.
Scheduled wipe → Minutes to warn players before that restart	10	How long players get between "an update is out" and the restart that installs it.
Scheduled wipe → Restart quietly to install hotfixes that are not the monthly update (no wipe)	true	A hotfix build between force wipes gets a quiet restart of its own so your panel installs it — no wipe warnings, no wipe. Turn it off to install hotfixes by hand.
Scheduled wipe → Roll a new random seed when a wipe wanted a voted map but there was 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. On a test server you may turn it off, and every edit applies by itself.
Scheduled wipe → Sync the in-game wipe timer (Nuclear Missile Silo countdown)	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.
What the wipe deletes → World	always	Buildings, sleepers, loot and deployables (<code>.sav</code>). Every entry below takes <code>never</code>, <code>full</code> (Full wipes only) or <code>always</code>.
What the wipe deletes → Learned blueprints	full	What players have researched (<code>player.blueprints.*</code>). This is the difference between a Map wipe and a Full wipe.
What the wipe deletes → Clans	never	Clan name, tag, logo, members and roles (<code>clans.*</code>). Rust means clans to outlive a map wipe: the clan table is destroyed with the world, the clan itself is not. Set this to <code>full</code> if a Full wipe should also break up the clans.
What the wipe deletes → Death markers	never	Where players last died (<code>player.deaths.*</code>). These point at places on the old map.
What the wipe deletes → Player state	never	Per-player state saved alongside the old world (<code>player.states.*</code>).
What the wipe deletes → Sign pictures	never	Images painted on signs and photo frames (<code>sv.files.*</code>). The signs go with the world, so this file only grows.
What the wipe deletes → Remembered players	never	Friend / foe / neutral marks and the faces behind them (<code>relationship.*</code>).
What the wipe deletes → Stale map files	false	Delete downloaded maps and occlusion caches that are not the map about to load. Each one is around 15 MB and nothing ever cleans them up.

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,
  "Restart automatically when Facepunch releases the monthly update": true,
  "Minutes to warn players before that restart": 10,
  "Restart quietly to install hotfixes that are not the monthly update (no wipe)": true,
  "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,
  "What the wipe deletes": {
    "World: buildings, sleepers, loot, deployables (*.sav*)": "always",
    "Learned blueprints (player.blueprints.*)": "full",
    "Clans: name, tag, logo, members, roles (clans.*)": "never",
    "Death markers, pointing at the old map (player.deaths.*)": "never",
    "Player state saved with the old map (player.states.*)": "never",
    "Pictures on signs and photo frames (sv.files.*)": "never",
    "Remembered players: friend, foe, neutral (relationship.*)": "never",
    "Delete downloaded maps that are not the one about to load": false
  }
}

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.