Three games, one bot

Tournament brackets

Open a tournament and it gets its own thread, a short code people can join from anywhere, and a pinned card with the rules, entry fee and prize. When it starts, the bot draws the bracket and posts a match card for every round-one pairing, pinging both players.

A player can hold more than one entry, and the draw guarantees nobody meets themselves in round one unless the arithmetic makes it unavoidable — and then as rarely as possible.

How a match card looks in the channel.

Every live card carries a button per player. Press the winner's name: claiming your own win brings the card back to the bottom for your opponent to confirm, and conceding settles it outright. A tournament never stalls behind a player who has gone quiet. Organizers can settle a match outright, undo a result and everything downstream of it, or hand a dropped-out player's seats to someone else mid-tournament.

Or run it as an olympics and nobody reports anything: the bot deals every match as a dice game in the thread, and the winner advances the moment it lands. Which game a heat plays is drawn from the same sealed secret the tournament publishes when it ends, so that is checkable too — and the final is a best of three the two finalists pick themselves. Watch one play out →

Death Roll

A duel: roll from 1 to the last number rolled, and whoever rolls a 1 loses. Both players roll once at the start to decide who goes first, each on their own message with their own button, and every roll is sealed into the channel as a permanent line.

A turn, the record it leaves, and the result.

There are five dice games: Death Roll, and four settled in one throw each — /roll hi, lo, far and close. A game needs no stake at all — /roll dr user:@rival plays for bragging rights, which is the common case. Where there is a wager it moves a notional score: a number kept per player per server, with no money, purchase or exchange anywhere in it. Everyone starts at zero and can go as far into the red as their luck takes them.

Poker nights

The one thing here the bot does not play. A poker night happens at a table, or in a client the bot has no account on — what it runs is the arranging, which is the part that goes wrong in a channel. Open one with the buy-in, the payment link and the prize, and the roster card is reposted every time somebody joins, so it never scrolls away under the conversation.

The roster, the check-in, and what it leaves behind.

Check-in pings everybody and gives each player a button to press once they have paid — the host can press anybody's, for whoever pays in cash. The bot never touches the money: it displays a link somebody typed and records that a human said it arrived. As each player busts out the host presses Busted, so the finishing order builds itself — and every position scores: at a table of N the winner takes N points and last takes 1, so turning up every week can out-rank one lucky night. Points are kept by month, and a cancelled night counts for nothing. Watch one come together →

What it is like to run

Add it

The invite asks for the permissions listed on Setup, each with the reason it is needed. Nothing privileged: every game arrives as slash commands, so the bot never reads your server's messages. What it does keep is set out in the privacy policy.