GOVERNANCE // PUBLIC STANDARD
Player trust is fragile. Admin power is easy to misuse. Rust communities fall apart when enforcement feels random.
TIRust governance is the public operating standard behind Treasure Island Rust: how we think about moderation, appeals, fair-play enforcement, supporter neutrality, staff conduct, and evidence handling.
The player-facing server rules, maps, connection details, and shop belong on tirust.fun. This page explains the standard behind the rules.
OPERATOR NOTEA fair server is not one with no bans. It is one where serious decisions can survive daylight.
PRINCIPLES // DECISION HYGIENE
Rust produces heat: rage reports, suspicious clips, private profiles, fresh accounts, shared IPs, proxy flags, old grudges, and players who are either cheating or simply better than the person yelling in chat.
TIRust governance separates signal from spectacle. A report can start a review. A pattern can raise priority. A tool can enrich context. Serious enforcement should still be explainable after the adrenaline is gone.
Staff should avoid single-signal punishment. Reports, server logs, BattleMetrics context, Discord records, server-side observations, alerts, connection history, and prior notes should be combined before severe action.
One weird datapoint is a question. A reviewed pattern is a case.
VPN use, proxy detection, private Steam profile, low hours, recent account age, family sharing, old bans, suspicious ASN, or unusual IP movement can justify review. None of those signals automatically proves wrongdoing.
VIP, MVP, purchases, donations, Discord reputation, or staff familiarity must not buy immunity. Support keeps servers alive. It does not rewrite the rules.
FAIR PLAY // WHAT WE MEAN
Cheaters should be removed.
Ban evasion should be expensive.
Clean players should not get crushed by lazy automation, angry chat, or a moderator having a bad night.
REVIEW LADDER // DETECT, ENRICH, DOCUMENT
Low-confidence signals should create flags, watch notes, Discord alerts, or staff review tasks. Medium-confidence patterns may justify closer observation or temporary restrictions. High-confidence composite evidence can justify kicks, mutes, temporary bans, or permanent bans depending on severity and history.
The goal is not to make every decision slow. The goal is to make serious decisions durable.
CASE REVIEW // CONTEXT STACK
review: steam_id account_age profile_privacy family_share_status rust_ban_history game_ban_history proxy_signal ip_and_asn_context battlemetrics_history server_reports staff_notes clip_or_log_evidence
Anti-cheat intelligence is decision support, not a replacement for judgment. Tools should make review sharper. They should not turn staff into spectators.
APPEALS // FACTS BEAT VOLUME
A good Rust ban appeal includes Steam ID, Discord ID if relevant, server name, approximate time, the action being appealed, and a concise factual explanation.
Appeals are not improved by threats, spam, staff shopping, public drama, or essays about unrelated grudges. The best appeal is short, specific, and checkable.
When practical, staff should preserve decision notes so future review does not depend on memory or chat archaeology.
ADMIN CONDUCT // PRIVILEGE HAS A JOB
NEXT // PUBLIC STANDARD, PRIVATE CASEWORK
TIRust should keep improving public rules, moderation summaries, appeal guidance, responsible disclosure, incident runbooks, and server status visibility.
Private player data, staff notes, security details, and active investigations should remain protected. Public trust comes from standards and outcomes, not leaking every receipt.