v0.1.0 - Initial public release

Arbiter v0.1.0

Initial public release of Arbiter, a Discord referee and tournament-operations bot for esports.

Highlights

• Multi-tenant Discord app with guild-installed org workflows and user-installed companion workflows.
• Components V2 match control panels for vetoes, match start, score reporting, pauses, warnings, evidence, rulings, disputes, referee claims, timelines, team rooms, and closing.
• PostgreSQL + Prisma storage with Docker Compose for local development.
• Org setup for admin/referee roles, match category, match-log channel, and evidence-vault channel.
• Built-in and custom rules presets for tactical shooters, SEL 2025 rulebooks, OW2 mode rotation, and format-only game presets.
• Referee score reporting with screenshot proof, player score report review, warnings, pause ledger, evidence vaulting, roster review, rulebook search, match history, and referee handoff logs.
• Battle-royale lobby workflow for Apex/Fortnite/Free Fire/PUBG-style events, including standings, prefilled game result modals, point adjustments, pauses, warnings, evidence, disputes, notes, and per-team categories with text/voice rooms.
• User-installed /ref-my and standalone /log workflows for referees working outside the bot's guild.

Reliability notes

• BR modal submissions defer immediately before slow score/log updates to avoid Discord interaction timeouts.
• BR team-room creation uses bounded concurrency and bulk permission overwrites to respect Discord rate limits better.
• Private rooms explicitly allow the bot so it can refresh panels, archive transcripts, and clean up channels.

Setup

See the README for full setup instructions:

1. npm install
2. docker compose up -d
3. configure .env
4. npm run db:generate
5. npm run db:migrate
6. npm run deploy:commands
7. npm start

Verification

This release was checked with:

• npm run check (31/31 tests passing)
• npx prisma validate

Known limitations

• Game API integrations are scaffolded as future work; automated Riot/Valve/etc. scoring is not included yet.
• Redis is intentionally not required at this stage.
• Production operators should rotate any test tokens and keep .env private.