What When2meet Does Well
If you run a competitive gaming team on Discord, you have probably used When2meet at some point. It is the go-to free scheduling tool when you need to find a time that works for a group. It is simple, it is free, and almost everyone already knows how to use it.
When2meet solves a real problem elegantly: you need to find a time window when multiple people are available, and you need to do it without everyone having to be online simultaneously.
You create a grid, share the link, and people drag to highlight when they are free. The overlap view shows you at a glance which windows have the most availability. Zero accounts required. Zero setup. Free forever.
For casual, one-time scheduling - a friend group trying to coordinate a movie, a class project team picking meeting times - When2meet is hard to beat. The friction is low, the output is clear, and it does not require any ongoing maintenance.
Where When2meet Falls Short for Gaming Teams
The issues start when you apply When2meet to a recurring weekly competitive schedule.
You have to reshare the link every week. When2meet events are not recurring. Each week is a new link, which means the captain creates a new grid, shares it in Discord, watches it get buried in chat, chases people to fill it in, and starts over the following Monday. It is a manual loop with no automation.
It does not know about roles. When2meet shows you who is available, but it does not know that you need a Tank, a Support, and three DPS for a full Overwatch lineup. It shows overlap, not composition. After you identify a time window, you still have to manually figure out whether you have a complete team for that slot.
It does not know about roster status. A team has starters, subs, and trials. When2meet treats everyone identically. If your starting tank marks themselves as unavailable and your sub tank marks themselves as available, When2meet has no way to surface that distinction.
It lives outside Discord. This is the biggest practical friction point. You paste a When2meet link in Discord. Some players click it, some ignore it. The captain pings people individually. Someone fills it in three days later after the decision was already made. The further scheduling lives from where your team already communicates, the more participation drops.
No lineup generation. When2meet's output is a heatmap. You still have to translate that heatmap into an actual lineup by hand - checking availability, cross-referencing roles, identifying who can play when. For a team that scrims four times a week, that is a non-trivial time cost.
What Supatimer Does Differently
Supatimer was built specifically for the team scheduling problem that When2meet was not designed to solve.
The availability calendar posts directly in your Discord channel. Players see it without navigating anywhere, tap buttons to mark their time blocks, and that is the entirety of what is asked of them. No link, no new tab, no account creation.
The structured output is the key difference. Because Supatimer knows each player's role and roster status, it can auto-generate the best lineup for each time slot with a single command. /weekplan shows you the optimal lineup for every day and time block in the week. /early-lineup focuses on a specific upcoming window. The captain's job shifts from building lineups manually to reviewing and overriding an automatically generated result.
Supatimer also handles what comes after the lineup - the scrim itself. You confirm the scrim with /scrim, which posts a formatted post with opponent details, time, map pool, and host side. After the match, /update logs the score. You end up with a searchable history of scrims that lives in your Discord without any extra effort.
Side-by-Side Comparison
Here is a quick comparison of the two tools across key features for gaming teams.
When to Use When2meet
When2meet is still the right tool for certain situations: you need to find a time once, not weekly. The group you are coordinating is not on Discord (external contacts, mixed platforms). You are scheduling something that is not a gaming session - a meeting, a call, a non-recurring event. You need the absolute fastest setup with zero configuration.
For a one-time coordination problem with a group of any size, When2meet is genuinely hard to improve on.
When to Switch to Supatimer
Supatimer makes more sense when: your team scrims on a weekly recurring schedule, you are spending more than fifteen minutes per week on availability tracking, you have enough players that role coverage matters (you need a full team composition, not just bodies), your team is already organized on Discord, or you manage multiple teams or rosters and want a single view.
The setup takes about ten seconds - add the bot, run /setup, configure your time blocks and roster. From that point, availability tracking and lineup generation are automated.
The Real Question
The When2meet vs Supatimer question is really a question about whether your team's scheduling needs are occasional or recurring.
When2meet is a tool for finding a time once. Supatimer is a system for running a team week over week. They are solving slightly different problems, and the right answer depends on how you scrim.
If your team has a weekly schedule, a defined roster, and more than one or two scrims per week, the overhead of the When2meet loop compounds quickly. A tool that automates the repetitive parts of scheduling does not just save time - it reduces the coordination tax that sits on the captain every single week.
Both tools are free. The switching cost is fifteen minutes of setup. If the recurring availability loop is already costing you an hour a week, that math resolves quickly.