5 min read
Quotient alternative: run scrims from the web, not Discord
Quotient is gone and its self-hosted copies are unmaintained. Finalist is the web-first successor: hosts manage on web, players join from web or Discord.
Quotient was the Discord bot most Indian scrim hosts learned on. It is no longer running. Its code was public, so plenty of communities kept going on their own copies, but the public source has not been updated since September 2024, and a bot you host yourself is a bot you now maintain: the server, the database, every Discord API change.
Finalist is built by people who wanted a better version of that tool. Not a clone with a new logo: a different answer to the one thing Quotient never solved.
Managing everything from Discord is the problem
Quotient's whole interface was Discord. Creating a scrim, changing a setting, banning a team, fixing a slot: each one is a message with buttons, a wizard in a channel, a menu that expires. It works the first fifty times. Then you are scrolling a channel looking for the panel you used on Tuesday, and the settings you need are three menus deep.
Finalist splits the job along the line that actually exists:
- Hosts manage from the web and the app. One console for the event: settings, entries, slot board, check-in, room details, results, standings. Everything is a page you can link to, search and come back to.
- Players register on either side. From the event page on the web or the app, or from
Discord with
/event registerand the Register button. Same entry, same lineup, same slot list, whichever door they came through. - Discord stays where it is good. The bot posts the registration message, the live post, the room details when they unlock, the results. Hosts still bind channels and pause or resume a series from there, because that is quick. Nothing important depends on a message somebody has to scroll back to.
What carries over, and what changes
This is based on Quotient's public source code. It is a reference for what hosts were used to, not a claim about any copy someone is running today.
| Quotient | Finalist | |
|---|---|---|
| Where you manage | Discord, through buttons and wizards | Web and app console; Discord for quick actions |
| Registration | A message in a channel tagging teammates, checked by the bot | A team lineup with in-game names, on the web, the app or from Discord |
| Duplicate teams and players | Duplicate team names and tags can be blocked per scrim | One player, one entry across the event, enforced inside the registration |
| Slot list | Posted in a channel, with cancel, claim and reminder buttons | Slot board for the host to assign, swap and release; public slot list |
| Check-in | Not part of the scrim flow | Check-in windows. No-shows forfeit and the slot is refilled from the queue |
| Room ID and password | Posted by the host | Hidden until a set reveal time, then shown only to the lineup of slotted teams |
| Recurring scrims | An open time on chosen days; registration closes when the slots fill or by hand | Series with a timezone, generating each night, and pause or resume by command |
| Tournament formats | Groups with generated channels and roles | Battle royale points, round robin, single and double elimination, Swiss, gauntlet, and a manual bracket builder |
| Results | Points table image from entered numbers | Results sheet, confirmed standings with tiebreaks, a points table across a whole series, captain-submitted results with evidence and disputes |
| Public pages | None that we could find in the source | Every event, organizer and game has an indexable page |
| Staff and permissions | Moderator role | Host, referee and organization roles with separate permissions |
| Running it | Yours to host and update, or the hosted bot while it lasted | Hosted. Nothing to deploy |
| Price | Free tier with paid premium | Free for now, with paid plans possible later. No entry fees, no paid brackets |
Why a web console changes the rest
Rules are enforced rather than policed. One player in one entry, minimum lineup size, banned players, a minimum number of teams for the event to run, reveal times for room details: the system checks them, not whoever is hosting that night.
Events are pages. An event page works for a player who is not in your Discord yet, and it can be found through search. A message in a channel cannot.
Tournaments are first class. Stages, draws, schedules, check-in and advancement handle a multi-day bracket. Swiss pairing and a double elimination reset are built in.
You can rehearse. Test mode runs the whole event with fake teams and suppresses every message, so you find the mistake before your players do.
What you give up
We would rather you hear it here.
- Registration by tagging teammates in a channel. If your community loves that flow,
Finalist's Discord registration is a different shape: the team and lineup live in the app
and
/event registerties a Discord user to them. - Automatic screenshot verification. Quotient could check subscription screenshots for you. Finalist lets a team attach proof, and a staff member reviews it.
- Server tools. Lockdown, purge, autorole and tags were part of Quotient. Finalist only does events, and will not grow into a moderation bot.
Moving over
You do not have to move everything at once. Run your next series on Finalist and leave the old setup alone while players get used to it. A series needs a name, a game, a daily or weekly time and a registration window, and the first night is generated straight away.
Create an organization, publish a draft event and run it in test mode first. Finalist is free for now, and the page you share is the page your players will see.
Quotient is a trademark of its respective owners. Finalist is not affiliated with or endorsed by Quotient.