Vanilla Rust admin commands

Seconds the crash loot crates burn and stay unlootable after impact. All crates unlock together when this expires.

Log crash-target search diagnostics (samples, blockers, reasons)

Starting impact radius before thruster adjustments, in meters

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.

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)

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.

Technical attributes — these are not permissions:

• Registered in the client console client
• Included in saved settings saved
• Replicated to clients replicated

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.

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.

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.

If true, firing satellite thrusters does not consume fuel

If true, powering up the satellite computer does not require any items

Maximum fuel rolled for large satellites (3000-5000kg)

Minimum fuel rolled for large satellites (3000-5000kg)

Hard maximum on generated fuel, applied after the per-size roll regardless of size

Maximum fuel rolled for medium satellites (1500-3000kg)

Minimum fuel rolled for medium satellites (1500-3000kg)

Hard minimum on generated fuel, applied after the per-size roll regardless of size

Maximum fuel rolled for small satellites (500-1500kg)

Minimum fuel rolled for small satellites (500-1500kg)

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.

Radius (m) around the impact point cleared on crash - players killed, construction/deployables/vehicles destroyed, vegetation removed

Lateral offset multiplier per thruster fire (meters)

Dev: search for a safe crash site around the calling player using the exact same acceptance checks a control computer's lock-in uses (topology, water, unevenness, safezones, obstructions), then launch the full orbital descent there. Not a full session replica: searches around the player rather than a computer's semi-random targeting center, always does a fresh scan (no thruster-history reuse), and has no owning computer (no countdown screen, radius floor still enforced, no-build volume self-despawns after impact instead of being computer-managed): satellite.launch [radius]

Dev: exactly satellite.launch - same crash-site search and validation - but skips the wait: the satellite spawns already in phase 2, 30 seconds from impact, at the point of the descent path it would normally reach then: satellite.launchquick [radius]

Minimum crash radius in meters

Maximum random aim drift (meters) applied when tightening the impact radius

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

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.

Extra distance (m) further out, along the descent line, that phase 1 starts. The satellite slides steadily from there in to the orbit point over phase 1, then phase 2 continues along the same line.

Multiplier the orbiting satellite's glow billboard grows to by the end of phase 1 (starts at 1x). Purely a visual telegraph; replicated because the grow runs client-side.

Technical attributes — these are not permissions:

• Registered in the client console client
• Included in saved settings saved
• Replicated to clients replicated

Trigger a satellite crash at a random valid position on the map

If true, the satellite control computer can only be powered up while the power plant is active (powergrid stage 1+). Ignored when the powergrid system itself is disabled.

Crash targeting: before scanning, re-test the previously found crash spot. Small thruster nudges usually leave it valid, returning in a single check.

Heading rotation per thruster fire (degrees)

Impact radius change per thruster fire (meters)

Also raycast the crash-site footprint against real collision geometry, rejecting spots with rocks or scenery the heightmap can't see

Clearance (m) the crash-site search demands around a candidate - rejected if any player building, prevent-building volume or safezone is within this range. Kept separate from kill_radius so targeting standoff can exceed what the impact destroys; 16 matches the building-privilege radius, so a valid site is never inside a base's TC influence.

Radius (m) around a candidate crash spot sampled for ground shape - roughly the crash remains footprint. Used both to reject unsuitable spots and to fit the spawned remains to the ground.

Max overall ground slope (degrees) across the crash footprint before a spot is rejected

Max terrain height deviation (m) from the crash footprint's best-fit plane before a spot is rejected as too uneven (cliff edges, crests, dips the remains meshes can't hide)