• Player Support Helper: answer questions and help players get the right support. About the role · Apply
• Moderator: investigate reports and help enforce the rules, starting with a supervised trial. About the role · Apply
• QA Playtester: test maps and changes, and help us track down bugs. About the role · Apply
• Community & Events: plan activities and help run them for the community. About the role · Apply
• Developer / Server Technician: work on plugins, settings and server maintenance. About the role · Apply

Read about the role you're interested in and our team expectations, then sign in and use its application form. Each form has 13 questions about your availability, experience and situations you could run into. Tell us what you can comfortably help with; you don't need to promise every spare hour.

Your answers go to the application reviewers. Please don't post them in a public thread. We need your public Steam profile or SteamID, and a Discord username is optional. Never send login details. For a correction or question about your application, use the Support Center.

If we think it's a good fit, we'll follow up and discuss a supervised trial, the time you can give and any payment arrangements before you start. Acceptance doesn't automatically give you staff permissions. Senior staff and leads are chosen internally. There are no application fees, and purchases or donations won't buy a place on the team.

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

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 that changes, tell players promptly.

During the event, keep instructions clear and apply the same rules to everyone. Ask a moderator to deal with cheating or harassment. If a dispute involves you or your friends, have another staff member review it. Pause the event if a server problem or missing staff makes it unfair to continue.

Afterward, confirm the results, make sure approved prizes reach the right players and ask what people enjoyed or found confusing. If something went wrong, discuss it with the team before planning the next one. Check before sharing footage, and keep private messages and reports out of it.

Apply for Community & Events

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 order you did it.
• What you expected and what actually happened.
• Whether it happened again, with a clip or screenshot if that helps show it.

For example, “the door doesn't work” leaves a lot to guess. Naming the monument, showing the door and explaining what happens when you interact with it gives someone a place to start.

After a fix, try the same steps again. If it needs another player or a restart to check properly, say that instead of calling it finished. Report what you actually tested, including anything you couldn't complete.

Apply to be a QA Playtester

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. Anything you learn through staff tools stays out of your own gameplay and team chat.

When you do take action, leave a short note explaining why, which rule applies and where the supporting clips or logs are. Include when a temporary punishment ends. Explain the decision to the player without identifying the reporter or sharing private staff discussion. Appeals go through the Support Center and need a reviewer who wasn't responsible for the original decision.

New moderators begin with a supervised trial. Your supervisor will walk through reports with you and agree which commands you can use. More access comes after review; it isn't included automatically with an accepted application. Ask before acting if you're unsure about a punishment.

Apply for a moderator trial

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 back.

Reports about cheating, harassment or an exploit should go through the Support Center. Help the player include the server, approximate time and a clip or screenshot if they have one. Don't argue the case in public chat or promise a ban. A moderator will need to look into it.

You'll start alongside a staff member who can answer questions and check your replies. Helpers don't have punishment or server-management powers. If you can't finish helping someone before you leave, pass along what you've checked and what still needs an answer.

Apply to be a Player Support Helper

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. Send sensitive reports to the Support Center, rather than discussing accusations in chat.
• Let someone else handle a report involving your friends, your own team or a player you're personally arguing with.
• Never use staff commands or information to help yourself or your teammates in-game. Keep your account and staff access to yourself.

If you make a mistake, tell the team so it can be put right. If you need to leave during a report, let another staff member know what's still waiting. And if real life changes your availability, just speak up so we can plan around it.