Rust Applications & Role Protocols

Players should be able to come to us for help without worrying about who they know or which team they play with. Whether you're answering questions, handling reports or working on the servers, that's what we expect from the Rust team. Be patient with people. A lost fight, a connection problem or a missing item can be frustrating. Listen, find out what happened and give an honest answer. If you don't know, check with someone who does. Don't guess about a wipe, promise items back or announce a punishment just to end an argument. Follow the published server rules. If something isn't clear, ask before making up an answer.Keep player reports and staff discussions private. Se…

Helpers are often the first person a new player speaks to. The job is to help them get settled, answer everyday questions and make sure problems reach someone who can deal with them. Start by finding out which server they're on and what's going wrong. For a connection issue, ask what error they see and whether they've been able to join before. Check the current joining guide and server status before suggesting changes to their game. A simple, accurate answer is more useful than a long list of things to try. When you don't know an answer, say so. Check with the team and come back to the player. Don't guess about rules, wipe dates or whether someone will get their items b…

A good event is easy to join, fair to play and worth coming back for. Community and Events staff help come up with ideas, explain them to players and keep things running on the day. Start with an idea the team can realistically host. Work out where it will run, how long it should take, how players join and how a winner is decided. Talk it through with the team before announcing it. Any prizes, special commands or changes to the server need approval first. When the plan is ready, the announcement should give players the start time and timezone, joining instructions, rules and any agreed prizes. Make sure the host and any moderators you need are actually available. If tha…

Want to help out with Land of Ash, Detroit or both? We're taking applications for the Rust team. There are a few different ways to contribute, whether you enjoy helping new players, hosting events or working on servers. Player Support Helper: answer questions and help players get the right support. About the role · ApplyModerator: investigate reports and help enforce the rules, starting with a supervised trial. About the role · ApplyQA Playtester: test maps and changes, and help us track down bugs. About the role · ApplyCommunity & Events: plan activities and help run them for the community. About the role · ApplyDeveloper / Server Technician: work on plugins, settin…

Playtesters help us catch problems before they spoil someone's session. You might check a monument, try a plugin change or work through a bug another player has reported. You don't need to know how to write plugins, but you do need to explain what happened clearly. Before you start, check with the person running the test so you know which server to join and what needs checking. Don't try item duplication, deliberate crashes or destructive tests on a live server. If you find something that could be abused, stop and report it privately through the Support Center. A useful bug report tells us: Which server you were on and where the problem happened.What you did, in the or…

Moderators handle reports, help settle disputes and enforce the server rules. You'll sometimes be dealing with people who are angry with each other, so staying calm and listening matters as much as knowing Rust. Before taking action, find out what happened. Check the server, player names, time and the rule involved. Watch the full clip when it's available, and ask for the missing context. A suspicious shot or several people repeating an accusation isn't enough on its own to decide someone is cheating. Keep the report private while you investigate. If it involves your team, a close friend or someone you're already in a dispute with, ask another moderator to handle it. An…

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…