Working on the Rust servers

The technical team looks after plugins, settings and the tools that keep our Rust servers running. Players build hours of progress on these servers, so even a small change deserves a careful check.

Start by explaining the problem and what you plan to change. Test it away from the live servers first, then have another team member look it over. Check the thing players will actually do in-game; a server starting without an error doesn't tell us whether a door opens, a command works or progress survives a restart.

Before a live change, agree on it with the owner, take the relevant backups and make sure you know how to restore them. Check which server you're connected to. If something unexpected happens, stop and let the team know rather than stacking more changes on top.

After a Rust or Oxide update, check that the map and plugins still work before allowing automatic wipes to run again. Leave the wipe on hold if you haven't checked yet, even if it's due. If recovery might lose player progress, explain that before restoring an older backup.

Leave a short record of what changed, what you tested and anything still unresolved. Keep passwords and access keys out of posts, screenshots and shared logs. Report a leaked credential privately so it can be replaced.

New technical staff start with a supervised task on a test server. Live server access is arranged separately for the work they're trusted to carry out.

Apply as a Developer or Server Technician