How to run a Rust server: wipes, maps, and plugins

Setup and configuration

The map is set by a size and a seed. Sizes around 3000 to 3500 suit small and medium populations, while 4000 and up suit large servers. A seed gives you the same layout every time, so you can pick one with good monuments and fair spawn areas.

Facepunch releases a forced wipe on the first Thursday of each month, when every server must reset the map. Many servers also wipe weekly or every two weeks between forced wipes. Blueprints can reset on forced wipes only or on every wipe, and that choice shapes how casual or hardcore the server feels.

1. 01Pick a map size that fits your expected player count.
2. 02Choose a seed, or a custom map if you have one.
3. 03Decide on weekly, biweekly, or monthly wipes, and when blueprints reset.
4. 04Set the group limit, such as solo, duo, trio, or no limit.
5. 05Set up RCON so admins can manage the server remotely.

Mods and plugins

Rust plugins run on Oxide (uMod) or Carbon. Popular additions include gather rate changes, kits, clans or team limits, better chat, and admin tools for spectating and banning.

Rust updates monthly with the forced wipe, and plugins can break on that day. We update the framework and test the plugin list as soon as the update lands so the server comes back quickly.

Discord connection

Most Rust communities run from Discord. A status bot shows player count and the next wipe, a channel announces wipes, and reports go to admins through a ticket channel.

Linking Discord and Steam accounts lets you give in-game perks or roles to verified members.

Support after launch

Wipe days are the busiest moment for a Rust server. We schedule the wipe, update Oxide or Carbon, check every plugin, and confirm the server is listed again before players arrive.

Performance drops later in a wipe as bases grow. Entity cleanup settings and decay rules keep the server smooth until the next reset.