
Stopping mid-session when you cannot
Stop queuing rather than stop playing, tell your team at the start which game is your last, and put the exit somewhere your tired self cannot quietly cancel it.

Stop queuing rather than stop playing, tell your team at the start which game is your last, and put the exit somewhere your tired self cannot quietly cancel it.

Fill the exact hours you used to play, not the day in general. Expect to be irritable and bored in the evenings, and expect your sleep to be strange before it gets better.

Say it once, in about three sentences, without a reason you have to defend. Then expect the pull back, and have somewhere for those friendships to live that is not the game.

Move the people off the platform before you uninstall, then put enough steps between you and the reinstall that it takes an hour instead of ninety seconds.
Set a last queue, not a stop time. Say it to your team when you sit down, not at the end. Then put something physical at the far side of the exit so the stop is a thing that happens rather than a thing you decide. Mid-session is the hardest moment to make a decision in, so stop making it there.
You are inside a unit of the game that has not finished. There are four other people relying on you. The next match is already loading because the game loaded it for you. And the version of you who set the alarm is not the one holding the controller.
That is three separate problems stacked on top of each other, and willpower is being asked to solve all of them at once, at the worst hour, on no food.
The recognised definition of gaming disorder opens with "impaired control over gaming", which is a clinical way of describing this exact moment. It is worth knowing that the criteria also require gaming to be taking priority over other daily activities and continuing despite real harm, normally for at least twelve months, and that gaming disorder "affects only a small proportion of people who engage in digital- or video-gaming activities". Losing an hour to one more game is not a diagnosis. It is a design problem and a scheduling problem, and both are fixable.
This is the single change that does the most work.
"I'll stop at eleven" fails because at eleven you are twelve minutes into a forty minute match. You cannot leave, so you finish, and finishing puts you back at the lobby where the queue button is glowing.
"My last queue is at half ten" works because it happens at a point where stopping costs nothing. You press nothing. The match you are in ends, and the session ends with it.
Practical version:
Games without units are harder. Open worlds, survival games, anything with no natural end, sandbox builders. There the equivalent is an objective: one more quest, this base finished, this island cleared. Say what it is out loud before you start it, because "a bit more" expands to fill whatever is left of the night.
You are not imagining the pressure. Leaving four people a player down is genuinely rude, and in a ranked match it costs them something. That obligation is what "one more" hides behind, and it works because it is partly true.
So take it off the table before the session starts, when saying it is easy.
At the start, in chat or on voice: **"Heads up, I've got about two hours, last queue at half ten."** Nine words. Nobody argues with it. Nobody remembers it in a bad way. And when half ten comes, you are keeping your word rather than bailing.
What not to do:
If your group runs scheduled raids or ranked nights, sign up for the ones you can finish and stop signing up for the ones that start at ten. Being reliable for two hours is worth more to a team than being available for five and vanishing.
An alarm is a suggestion. Something in the room is not.
Pick one, and pick the one you would actually do:
The point is that the exit needs a next step. People do not stop, they go and do something. If there is nothing to go and do, the lobby wins.
There is one honest limit here. Nobody has run a trial on any of this. The closest thing to hard evidence in this area is a randomised study that blocked mobile internet at the network level on people's phones for a fortnight and found "the intervention improved mental health, subjective well-being, and objectively measured ability to sustain attention; 91% of participants improved on at least one of these outcomes". That is friction imposed at a level the person could not undo, on a different device and a different behaviour. The direction is encouraging. It is not proof that a last-queue rule works, and this piece is not going to pretend otherwise.
It will, some nights. Treat it as information rather than as a verdict.
Write two things down before you sleep: the time you actually stopped, and what you were feeling twenty minutes before the queue you should not have taken. Do that four or five times and a pattern shows up, and it is almost never about the game. It is Sunday. It is after a row. It is the night you had nothing on the next day.
Then change one thing, not everything. If the alarm was the failure point, the alarm is not the fix. If your team is the failure point, the start-of-session sentence is. If the failure comes when you are already exhausted and the loop is the only thing keeping you awake, the problem is [the shape of your sleep](/guides/gaming/sleep-work-and-getting-your-day-back) and it will not be solved in a lobby.
If a whole day has gone rather than an hour, [that is recoverable and it starts tomorrow](/guides/gaming/you-played-for-nine-hours-what-now).
**How do I stop playing when my friends want one more?** Say your last queue at the start of the session rather than at the end. "Last queue at half ten" is a plan people respect. The same sentence at half ten sounds like you are letting them down, which is why it never survives.
**Why can't I stop mid-game even when I want to?** Because you are being asked to make a decision at the point where stopping costs the most, to four other people, while tired. Move the decision to the lobby, where it costs nothing, and the willpower problem mostly disappears.
**Does setting a timer work?** On its own, rarely. A timer that goes off mid-match gets dismissed because you genuinely cannot act on it. A timer set to the last queue gets acted on, because at that moment stopping is free.
**What if the game has no natural stopping point?** Then name one before you start. One quest, one build, one run. Say it out loud. Open-ended games expand into whatever time is left, so the boundary has to come from you rather than from the game.
Renovyn is the app we wished existed in our worst weeks. Check-ins, protection, community, and a crisis button for 3am. Or if you just want the next piece in your inbox, we can do that too.
One email. No noise. Just work worth reading.