Staff panel
Overview
Recent activity
Board depth
Activity
How much the site and the bot are actually being used.
Last 14 days
Website
Discord
Busiest hours last 7 days, UTC
Community
Top pages last 7 days
Top commands last 7 days
Top testers last 30 days
Most tested gamemodes last 30 days
Site status
Put a holding page in front of the public site. Staff keep full access while it is up.
Holding page
Visitors see the launch page instead of the tier list. Anyone signed into the panel still sees the real site.
What visitors see
While it is on
- The staff panel, its API and the sign-in flow stay reachable, so you cannot lock yourself out.
- Signed-in staff see the real site, which is how you check work before reopening.
- Visitors get a 503 with
Retry-After, so search engines treat it as temporary rather than dropping your pages. - The page checks back every 30 seconds and returns on its own once you turn this off.
- The Discord bot is unaffected and keeps serving commands.
Data backup
Download a copy of the roster and the database. Keep one somewhere off this server.
Downloads
Players spreadsheet
Every player with their region, role, linked account and placements. Opens in Excel or Sheets.
Roster data
The same records with full placement history, in a form the site can read back.
Whole database
A consistent copy of everything — players, tests, comps, transcripts, clips and staff points.
What is in the database
Handling these files
- They contain every linked Discord id and gamertag. Treat a download the way you would treat the bot token.
- To restore, stop the site and the bot, put the SQLite file back at the configured database path, then start them again.
- The server keeps its own nightly copy, but that copy lives on the same machine — a download is what survives losing it.
| Player | Region | Role | Placements | PTS |
|---|
Win ladder
Blacklist
Compose
Live preview
All promotions
Post a clip
Clips
Select a ticket to read its transcript.
Staff leaderboard
| # | Staff | Tests | Comps | Points | Adjust |
|---|