Set up your Rust server

Core launch settings

Rust dedicated servers commonly use server.hostname, server.description, server.maxplayers, server.seed and server.worldsize. Runic exposes only the settings validated for its production Rust egg and keeps provider-managed networking separate from customer-editable settings.

Larger world sizes and higher populations increase memory, CPU and storage pressure. Facepunch specifically notes that larger maps use more memory and that larger player counts need more CPU, so do not assume a larger RAM plan fixes every Rust performance problem.

Map changes and wipes

1. Create a backup before changing the map seed, world size or wipe-related configuration.
2. Record the current seed and world size before making the change.
3. Stop the server before replacing or removing map/save data.
4. Start the server and confirm the intended map loaded before deleting the old recovery point.

Add administrators

Use the server console or validated RCON path and the player’s correct Steam64 identity with Rust’s ownerid or moderatorid command. Current Facepunch documentation states that these changes are persisted automatically; a separate manual save command is not required.

Do not share the owner account, panel password or RCON secret just to give someone in-game administrative rights.