Skip to main content

What should a Rust event host be able to decide?

Give the host control of the event they are running. Write down who handles player conduct and server changes so a disputed round reaches the correct person without stopping the whole night.

Put a real dispute on the job sheet

Say a player at Birch Arena crosses the start line before the bell and claims another player disrupted the heat. The host can rerun the heat from the written contest rules. If someone reports harassment, the host passes that part privately to a moderator. Define those paths before deciding which accounts or permissions the host needs.

Match each action to the person who needs it

Write one result a volunteer should be able to produce on event night.

Match each action to the person who needs it
DecisionBirch assigns it toPractical check
Pause or rerun a heatEvent hostPost a ruling and start the next heat in the event space.
Investigate a conduct reportModeratorOpen a private report and acknowledge it without copying it to the event channel.
Change game settings or restartServer operatorReceive a clear request with the affected world and decide whether a change is needed.

Remove access that the exercise does not use

Discord roles can add access to individual channels. Give the event host the event space they need. In a Rust management tool, check the actual role capabilities rather than using the job title as a permissions checklist. If they can keep score and post a rerun through Discord, that job may need no management access at all.

Simulate the dispute with ordinary accounts. The host posts the new start in public and hands the conduct part to the moderator privately. If the host needs live player controls just to stop a heat, see whether event boundaries or a separate steward can meet the need before granting additional access.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details