Skip to main content

Which settings should your Rust worlds share?

Two worlds can share a standard welcome message and still play by different rules. Put the settings you maintain into a short sheet. Decide which ones follow a community decision and which belong to one world before you save a template.

Start with the reason each setting exists

Imagine Ridge runs a monthly survival world and a weekly practice world. The same support staff cover both. Practice offers different building rules and keeps a shorter season.

Start with the reason each setting exists
Choose one owner forRidge exampleHow to know
A community defaultThe address for private player reportsChanging it should send players from either world to the same current destination.
A world choiceWipe schedule, map size, difficulty and player capA player sees and experiences the rule that belongs to the named world.
An instance valueSave identity, endpoints and per-world credentialsA change or restart targets the intended world alone.
Player stateMaps, progression, plugin data and staff grantsEach record stays where its players and access rules expect it.

Give exceptions a reason and a person

Next to each shared setting, note who can change it, which worlds should receive it and what staff should check on each. Write out valid exceptions, such as ‘Practice players use a separate report channel during staff-run sessions.’ Keep passwords and connection secrets in the appropriate private controls. The shared sheet only needs to say where to manage them.

Try one harmless choice before adopting the sheet

Ask a helper to find where they would change the player help link. Have them name the expected value in each world, including any exception, and check what the player sees. If they cannot tell who owns it or what applies to which world, fix the sheet before copying more settings.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details