Best Beginner Server Settings for Rust Console: A Simple 2x Starter Config

How Server Settings Work on Rust Console

On Rust Console, the native server settings are your entire toolkit, and they do more than most new owners expect. There are no add-ons to install on PS4, PS5 or Xbox, so everything you tune runs through your in-game server settings and, for live control, a bot over WebRCON. Those built-in settings cover gather, decay, blueprints, PvP and worldsize, which is just about everything a first server needs.

You change these settings in one of two places. The first is your host control panel, either G-Portal or Nitrado, where edits are saved for you. The second is over WebRCON, the remote console a management bot connects to using your server IP, RCON port and RCON password. Panel edits stick on their own. Live changes made over WebRCON need one extra step to survive a restart, which we cover further down. If this is your very first server, our guide to running a Rust Console server for beginners walks through hosting and admin setup start to finish.

The Copyable 2x Starter Config

Here is a sensible starting point for a first PvP server. It feels fast and welcoming without turning the game into a sandbox. Set these, launch, then adjust once you see how your players behave.

Gather scale: 2. This doubles what you harvest from nodes, trees and animals, so a starter base comes together in an evening instead of a weekend. It is the single most important number for a first server.

Decay scale: 0. A no-decay build means bases never rot while people are offline, which removes the most common source of new-player frustration. If you want a stricter survival feel, leave decay at 1 and let players maintain their own bases.

Blueprints: unlocked. Turning the blueprint unlock setting on lets players craft without grinding research, which pairs well with a casual 2x. Leave it off if you want vanilla progression. Either way, read the section below on what this switch really changes.

PvP Mode: on. Player versus building: on. That is standard PvP, the easiest kind of server to fill. For a peaceful build server, turn both off.

Worldsize: 3500. A smaller map keeps a modest crowd close enough to actually find each other. Huge maps feel empty until you have a real population, and changing worldsize later forces a map wipe.

Slots: 30 to 50. Do not pay for 100 slots you will not fill on day one. You can size up later, and it keeps your monthly cost down while you grow.

A server name under 60 characters, so it shows up correctly in the console community browser. Leave fps.max at its default; there is no reason to touch it.

Gather Rate Without Over-Tuning

Gather scale defaults to 1, which is true vanilla. Useful values sit between 1 and 3. The setting multiplies what you pull from nodes, trees, hemp and animals. It does not change the loot inside monument crates, so a higher gather rate speeds up farming, not looting.

Two is the sweet spot for a console server. It respects people's time, gets a base off the ground in one session, and still leaves something to grind for. Three works for a very casual crowd. Once you climb into 5x or 10x territory, players hit fully upgraded bases on day one, run out of goals by day three, and the server empties out. Fast and fair beats extreme every time, especially with the smaller populations that console servers tend to run.

If your players are mostly weekend casuals who cannot no-life a wipe, a clean 2x keeps them coming back. That retention is worth far more than the novelty of a mega-rate server.

Decay and Upkeep, and How to Turn Off Decay

Decay is structures slowly losing health when they are not maintained. Upkeep is the resource cost you pay into your tool cupboard, the TC, to hold that decay off. The two are linked, and for a first server you mostly need to make one decision.

To turn off decay completely, set the decay scale to 0. Bases never rot, upkeep stops mattering, and nobody logs in to find their home gone. This no-decay setup is popular on casual and build servers. If you would rather keep a survival edge, leave the decay scale at 1 and let players maintain their bases by feeding the tool cupboard, or set it to 0.5 for a gentler middle ground. Console also gives you a tool cupboard upkeep toggle, so you can decide whether holding a base costs resources at all.

The one downside of no decay is clutter. Abandoned bases pile up because nothing removes them, so the map gets crowded by the end of a wipe cycle. That is one more reason to wipe on a regular schedule. No-decay servers also pair naturally with protection while players are away, so it is worth dialing in your offline raid protection settings alongside this.

The Blueprint Unlock Switch and What It Really Changes

By default, the blueprint unlock setting is off. Players learn blueprints the vanilla way, spending scrap at a research table or working up the tech tree at workbenches. Turn the setting on and every blueprint is unlocked for everyone from the moment they spawn. No researching, no tech-tree grind.

Here is the part most searchers miss. Unlocking all blueprints does not skip the workbench. To craft a tier 2 or tier 3 item, a player still has to be standing near a workbench of that tier. The switch removes the learn-it step, not the craft-it-at-the-bench step. So progression still exists, it is just shorter.

Unlock everything for a casual or build-focused 2x where you want people fighting and building quickly. Leave it off when the slow climb from stone to metal to tier 3 is the whole point of your server.

Make Your Settings Survive a Restart

This is the mistake that catches almost every new owner. Convars you set live over WebRCON do not persist a restart. Change your gather rate over RCON, restart the server, and it quietly reverts to the old value.

To make changes permanent, they have to be written to the server config. Running server.writecfg saves the current settings to the config file, and changes made in your host panel are written for you automatically. When in doubt, set it in the panel or write the config, then restart once and confirm it held.

This matters more on console than you might think. G-Portal reboots your server on its own whenever Facepunch ships a patch, which also knocks your bot offline until it reconnects. If your settings only ever lived in a live RCON session, that patch reboot wipes them. A WebRCON bot such as Vantic can push these settings and reconnect by itself after a patch reboot, so your config and automation come back without you watching the panel. If a change refuses to hold, our walkthrough on why your admin commands are not sticking covers every cause.

PvP or PvE, and Getting Your Server Found

The PvP Mode and player-versus-building toggles decide the feel of your server. Leave both on for standard PvP, which is the easiest type of server to fill and the safest default for a first launch. Turn both off for a peaceful PvE server where players cannot damage each other or each other's builds. You can run a friendly 2x either way.

Once your settings are in, players need to actually find you. Your name should stay under 60 characters, with the word players search at the front. Players open the console community browser with Y on Xbox or Triangle on PlayStation. A brand-new server takes about 15 minutes on G-Portal, or 5 to 8 on Nitrado, from starting to joinable and listed, so do not panic if it is not there the second you boot it. If it still refuses to show, work through the reasons your server is not appearing in the community browser.

Last, pick a wipe cadence before you open the doors. Most console servers wipe weekly, often Thursday around 18:00 UTC, or every two weeks. A server that goes longer than a month without a wipe tends to get unstable, and the first 24 to 48 hours after a wipe are your peak population and your best shot at keeping new players.

Frequently asked questions

Keep reading

Running a Rust Console server for beginners · Why your admin commands are not sticking · The best ORP and ZORP settings for Rust Console · How much a Rust Console server costs · Your Rust Console wipe day checklist