Rust Server Variables

Give Item List →

Console commands for the F1 menu or RCON. Source: a community-maintained export of Rust's own generated command metadata - treat this as a helpful reference, not an exhaustive one.

Server configuration variables (convars) for server owners: set them in server.cfg, from the F1 console as an admin, or over RCON. Each shows its default value.

1,518 commands

Command	Description	Category	Type	Default	Permission
`rustnav.bakestatsenabled`	Collect navmesh bake statistics (rustnav.bakestats to read them). Defaults on in the editor, off on servers; flip on live to diagnose bake issues, then reset with rustnav.bakestats true	rustnav	variable	`False`	Admin
`rustnav.collectbudgetms`	Main-thread time budget per frame (ms) for navmesh tile geometry collection. The full-map bake wall clock is roughly tiles / (budget-worth of tiles per frame) / fps, so raise this while baking to trade frame time for bake speed	rustnav	variable	`1`	Admin
`rustnav.detailsampledistmult`	Detail mesh sample distance as a multiple of cellSize (Recast default 6). Larger = cheaper detail mesh, coarser surface height. Applies to tiles built after the change	rustnav	variable	`12`	Admin
`rustnav.detailsamplemaxerrormult`	Detail mesh max sample error as a multiple of cellHeight (Recast default 1). Larger = cheaper detail mesh, more height error. Applies to tiles built after the change	rustnav	variable	`1`	Admin
`rustnav.drawkbps`	Max KB per second of navmesh tiles streamed to each rustnav.draw viewer	rustnav	variable	`512`	Admin
`rustnav.drawmanifestinterval`		rustnav	variable	`10`	Admin
`rustnav.drawradius`		rustnav	variable	`100`	Admin
`rustnav.drawrefreshrate`		rustnav	variable	`0.25`	Admin
`rustnav.drawtilebudget`		rustnav	variable	`5`	Admin
`rustnav.enableverboselogs`		rustnav	variable	`False`	Admin
`rustnav.legacybuild`	A/B kill switch: build navmesh tiles with the stock pre optimization algorithms (clip rasterizer, full ledge and region rescans, unfused filters). Combine with detailsampledistmult 6 to approximate the old build end to end. Applies to tiles built after the change	rustnav	variable	`False`	Admin
`rustnav.maxshoredistance`	Metres of open water past which default navmesh tiles are dropped instead of baked. A tile only drops when every point in it is that far from land, so shores keep their navmesh and so do rivers and lakes, which are never that wide. Independent navmeshes (oilrigs, tropical islands, ghost ships) are never touched. 0 or less bakes the open sea like before. Applies to tiles queued after the change	rustnav	variable	`100`	Admin
`rustnav.numthreads`	Navmesh tile builder worker thread count. Applied when the builder is (re)created - at boot, or via rustnav.setnumthreads at runtime. ~half the cores is the sweet spot for full-map bakes	rustnav	variable	`4`	Admin
`rustnav.savecompression`	LZ4-compress navmesh saves (smaller .navmesh files, no extra save time)	rustnav	variable	`True`	Admin
`rustnav.savethreads`	Worker threads for navmesh save/load compression. 0 = auto	rustnav	variable	`0`	Admin
`sail.maxthrustmultiplier`		sail	variable	`1`	Admin
`samsite.autoreloaddelay`	Delay before SAM sites that haven't shot a target will auto-reload	samsite	variable	`45`	Admin
`samsite.staticrepairseconds`	how long until static sam sites auto repair	samsite	variable	`1200`	Admin
`santasleigh.altitudeaboveterrain`		santasleigh	variable	`50`	Admin
`santasleigh.desiredaltitude`		santasleigh	variable	`60`	Admin
`satellite.control_window`	Seconds of thruster control window	satellite	variable	`180`	Admin
`satellite.cooldown_hours_max`	Maximum cooldown between satellite events, in game hours	satellite	variable	`18`	Admin
`satellite.cooldown_hours_min`	Minimum cooldown between satellite events, in game hours (not real minutes) â€” converted to real time via the map's day length, same as the airdrop event scheduler.	satellite	variable	`18`	Admin
`satellite.crashing_fx_at_distance`	Run the crashing FX pass (FX Pass 3) through the whole phase-2 descent, including the distance-projected stretch, instead of waiting until the satellite enters real draw distance. The projected-mode fixup still applies â€” its particles simulate in local space and scale with the model; its trails stay gated until real rendering.	satellite	variable	`True`	Admin
`satellite.crate_fire_duration`	Seconds the crash loot crates burn and stay unlootable after impact. All crates unlock together when this expires.	satellite	variable	`300`	Admin
`satellite.debug`	Log crash-target search diagnostics (samples, blockers, reasons)	satellite	variable	`False`	Admin
`satellite.default_crash_radius`	Starting impact radius before thruster adjustments, in meters	satellite	variable	`300`	Admin
`satellite.descent_angle`	Angle (degrees from vertical) the satellite descends at. Higher = more horizontal streak across the sky. Clamped to 45 so it always reaches the ground within 45 degrees of straight down. Only used when flyover_altitude is 0 â€” the flyover path has its own geometry.	satellite	variable	`45`	Admin
`satellite.descent_seconds`	Descent duration in seconds (0 = use day length fraction; nonzero values are clamped to a minimum of final_descent_seconds so the phase-2 window always fits inside the descent)	satellite	variable	`600`	Admin
`satellite.final_descent_seconds`	Seconds before the scheduled crash that the satellite begins its phase-2 physics descent. Phase 1 slides in to the phase-2 start point up until then, then the satellite drops at a speed timed to hit the ground exactly on schedule. The start point is placed at the satellite's finalDescentSpeed times this window, so lengthening it starts the descent higher rather than slowing the fall.	satellite	variable	`300`	Admin
`satellite.final_descent_speed`	Speed (m/s) of the phase-2 physics descent (0 = use the satellite prefab's finalDescentSpeed). Together with final_descent_seconds this sets where phase 2 starts â€” speed times seconds back up the descent line â€” so e.g. 180s at 80 m/s starts the drop 14.4km out.	satellite	variable	`0`	Admin
`satellite.flyover_altitude`	Altitude (m above the crash target) of the phase-2 flyover cruise. The satellite enters near-horizontally at this height, streaks across the sky, then bends into a dive onto the target from flyover_dive_distance out. 0 = disable the flyover and use the legacy straight-line descent at descent_angle.	satellite	variable	`2500`	Admin
`satellite.flyover_dive_distance`	Horizontal distance (m) from the crash target at which the flyover bends into its terminal dive. Smaller = a longer level cruise with a steeper final plunge.	satellite	variable	`1500`	Admin
`satellite.free_fuel`	If true, firing satellite thrusters does not consume fuel	satellite	variable	`False`	Admin
`satellite.free_power`	If true, powering up the satellite computer does not require any items	satellite	variable	`False`	Admin
`satellite.fuel_large_max`	Maximum fuel rolled for large satellites (3000-5000kg)	satellite	variable	`16`	Admin
`satellite.fuel_large_min`	Minimum fuel rolled for large satellites (3000-5000kg)	satellite	variable	`10`	Admin
`satellite.fuel_max`	Hard maximum on generated fuel, applied after the per-size roll regardless of size	satellite	variable	`36`	Admin
`satellite.fuel_medium_max`	Maximum fuel rolled for medium satellites (1500-3000kg)	satellite	variable	`26`	Admin
`satellite.fuel_medium_min`	Minimum fuel rolled for medium satellites (1500-3000kg)	satellite	variable	`16`	Admin
`satellite.fuel_min`	Hard minimum on generated fuel, applied after the per-size roll regardless of size	satellite	variable	`8`	Admin
`satellite.fuel_small_max`	Maximum fuel rolled for small satellites (500-1500kg)	satellite	variable	`36`	Admin
`satellite.fuel_small_min`	Minimum fuel rolled for small satellites (500-1500kg)	satellite	variable	`24`	Admin
`satellite.initial_offset_attempts`	How many times to re-roll the initial random map position, re-checking the full crash-site acceptance each time, until a valid starting target is found. Guarantees the control phase never starts on an unusable spot.	satellite	variable	`8`	Admin
`satellite.kill_radius`	Radius (m) around the impact point cleared on crash â€” players killed, construction/deployables/vehicles destroyed, vegetation removed	satellite	variable	`10`	Admin
`satellite.lateral_distance`	Lateral offset multiplier per thruster fire (meters)	satellite	variable	`200`	Admin
`satellite.min_crash_radius`	Minimum crash radius in meters	satellite	variable	`100`	Admin
`satellite.nudge_distance_max`	Maximum random aim drift (meters) applied when tightening the impact radius	satellite	variable	`150`	Admin
`satellite.nudge_distance_min`	Minimum random aim drift (meters) applied when tightening the impact radius, at a fully random angle so it can't be cancelled out exactly by the cardinal-direction lateral thrusters	satellite	variable	`100`	Admin
`satellite.obstruction_tc_reorder`	Crash targeting: use the tool-cupboard grid to test likely-occupied samples last, so a clear spot is usually found with fewer physics checks. The physics check stays authoritative.	satellite	variable	`True`	Admin

Server configuration variables (convars) for server owners: set them in server.cfg, from the F1 console as an admin, or over RCON. Each shows its default value. Search by name, description or category; every row has a copy button.

Frequently Asked Questions

Press F1 in game. Type a command and press Enter; press F1 again to close it.

A community-maintained export of Rust's own generated command metadata. Commands change with game updates, so treat it as a helpful reference rather than an exhaustive one.

Rust Server Variables

Frequently Asked Questions

How do I open the console in Rust?

Where does this list come from?