SCUM bans, strikes and moderation

Bans, strikes and moderation give a team one consistent way to handle rule violations. Instead of separate notes and manual lists, every player action can retain a reason, evidence, points, state and decision history.

Context moderators need for a decision

A sensitive action uses stable player identity and authorised evidence.

• ban, unban and reason with traceable history
• strike points, category, notes and available evidence
• shared community policy with per-server delivery
• ticket or appeal handling without exposing internal notes

Consistent rules for the whole team

Moderation becomes more predictable when similar violations follow a similar process.

• issue a temporary or permanent ban with a clear reason
• use strike points before stronger action
• protect several community servers with one policy
• review history during an appeal or new report

Structured action instead of a raw command

Nodera creates a server-targeted request and NODERAgent executes only the explicitly permitted command through local NODERA-RCON. The web has no direct console access and the result returns to audit.

Repeated result delivery does not create duplicates and every server keeps its own status. Internal evidence and notes remain in authorised administration, not in public player requests.