Fairness first
Rules, kits, monetization, events, and admin actions must preserve player trust. No pay status should override governance or enforcement.
Operating Standards
Safe defaults for a live multiplayer operation.
These standards define how TIRust should build, operate, and evaluate systems across game servers, websites, Discord bots, automation, anti-cheat workflows, and future SaaS tooling.
Composite review
Use layered detection, correlation, and staff review. Avoid single-signal bans from VPN, account age, family share, private profile, or old bans alone.
Operational resilience
Prefer reproducible configs, backups, deployment checklists, monitoring, documented ports, service isolation, and rollback paths across the platform stack.
Auditability
Bots and triggers should log what they saw, what they changed, and why. Silent failures and hidden moderation actions destroy trust.
Least privilege
Protect RCON, API keys, bot tokens, deployment credentials, admin accounts, and server panels. No hardcoded secrets in public code or web roots.
Minimum necessary retention
Keep enough evidence for safety, appeals, and abuse prevention. Avoid collecting or exposing data that is unnecessary for operations.
Plugin and automation standard
Rust/Oxide/Carbon plugins should use event-driven design, defensive null handling, config validation, permission checks, cooldowns, concise logging, and low-cost hooks. Avoid heavy OnTick logic, blocking I/O, hardcoded secrets, spammy timers, and client-trusted enforcement.
Moderation standard
Preferred action model: flag, enrich, alert, review, document, act. Permanent bans should be reserved for strong composite evidence, confirmed evasion, severe abuse, or repeated violations.
Product standard
Any commercial anti-cheat or moderation product under Banh should be explainable, appeal-aware, false-positive resistant, and portable across infrastructure providers. See Research & Labs for the Banh direction.