Levelling that follows you
Messages and voice minutes earn XP against the same account your website profile reads from. Boosters and bonus roles earn more; a cooldown keeps it from being farmed.
/rank/leaderboardLoading Gamers' Strife
Discord Application
The whole ladder,
from your server.
Challenge a team, play the match in its own thread, report the score with proof attached — and have it count on the site the moment it lands. The bot is not a mirror of Gamers' Strife. It is Gamers' Strife, with a Discord front end.
40
Slash commands
1
Privileged intent
0
Messages read
0
Database keys held
What it does
Six things, done properly.
Everything below writes to the same records the website does. A result reported in Discord is not a copy of a result — it is the result.
Rosters you can run in chat
Browse teams, ask to join one, and — if you lead a roster — invite a free agent or remove a member without opening the site.
/teams/team-inviteChallenges on the board
Name an opponent and a time. The other leader gets a card with Accept and Decline on it, and an accepted challenge becomes a scheduled match on the ladder.
/challenge send/challenge listResults, with proof
Report a score and attach a screenshot in the same command. Both sides' submissions are compared, and a disagreement goes to a referee instead of to an argument.
/match report/match proofTournaments end to end
Registration, check-in and a bracket message that redraws itself as results land. An admin can have the bot build the whole tournament space — category, channels and participant role — in one command.
/tournament register/tourney spaceIt comes to you
Match threads open themselves, results are announced where they happened, and a challenge you need to answer arrives as a direct message you can act on from the notification.
/match list/whoamiCommand surface
Every command, grouped.
All 40 of them are slash commands. There are no prefix commands, because reading the messages that would carry them is a permission the bot does not hold.
Every message and every minute in voice counts toward the same XP total your website profile shows.
- Everyone
/rankCheck your or another member's rank and level
- Everyone
/leaderboardView the XP leaderboard
- Everyone
/levelhelpHow XP, cooldowns and bonuses work
- Everyone
/whoamiShow your linked website account and teams
- Everyone
/premiumCheck your premium subscription status
- Staff
/setlevelManually set a member's level
The loop
From challenge
to record.
Four steps, and only the first one happens on the website.
- 1
Sign in once
Signing in to the website with Discord is what links the two. From then on the bot knows which account you are and which rosters you can act for — there is nothing else to connect.
- 2
Send the challenge
A leader runs /challenge send with an opponent and a proposed time. The opposing leader gets a card in their DMs with Accept and Decline on it.
- 3
Play in a thread
An accepted challenge becomes a scheduled match, and the bot opens a thread for it with both rosters in the header — so the match has one place to live.
- 4
Report and settle
Both sides report a score with /match report. Agreeing results complete themselves and pay out MMR, SP and achievements; a disagreement is handed to a referee with both submissions side by side.
What it can see
Less than you'd expect.
A bot asks for permissions once and keeps them forever, so the honest thing is to say plainly which ones were never asked for. These are the real gateway intents, not a summary of them.
It cannot
- Read your messages
- The Message Content intent is not requested, so Discord never sends the bot the text of anything you write. It is told a message happened, which is all XP needs.
- See what you are playing
- The Presence intent is not requested either. Online status, game activity and Rich Presence are invisible to it.
- Hear a voice channel
- It counts the minutes you are in one and never connects to it. No audio reaches the bot, ever.
- Read your DMs
- It sends direct messages — a challenge card, a result notice — and ignores every one sent back to it.
How it is built
- Acts as you, never above you
- Every competitive action runs against the website's own API carrying your Discord ID, so it applies exactly your permissions. The bot's token grants it no authority to act as a leader, referee or admin.
- Holds no database keys
- Nothing is written to the database directly. A compromise of the bot host cannot reach your data, because the host has nothing to reach it with.
- Stores nothing for strangers
- If a Discord account has never signed in to the website, its activity is discarded rather than recorded. No account, no data.
- Heals itself
- State is pushed to the bot and re-derived on a timer, so a restart or a deploy mid-tournament catches up on its own instead of leaving a dead bracket.
The long version, with retention periods and how to have everything deleted, is in the Bot Privacy Policy.
Sign in once.
Play from Discord.
Linking is a single sign-in with Discord — after that the bot already knows who you are and what you can act for.