At some point, gaming to relax became something I had to learn

There’s a specific feeling I’ve started to recognise. I sit down to relax after a long day, open a game, play for an hour, and stand up feeling… worse. Not dramatically worse. Just slightly more frayed, slightly more depleted than when I sat down. The game wasn’t bad. I didn’t play badly. Something just didn’t quite land.

It took me an embarrassingly long time to understand what was happening. The explanation is almost annoyingly simple: I’d picked the wrong game for how I actually felt, or I’d spent the available time doing everything except playing, or I’d played while simultaneously trying to optimise the whole experience into something it couldn’t be. I had a lot of ways of making gaming less good than it should have been. Most of them looked, from the outside, like gaming.

The autopilot and what it costs

The automatic reach for a game isn’t a character flaw. It’s just how stress and habit work together.

When you’re tired or wound up, your brain doesn’t make careful decisions — it looks for shortcuts to relief. Games are genuinely good at providing that relief, which is part of why we love them. They offer a feedback loop of small challenges and small rewards that the brain finds deeply satisfying, especially when the rest of your day felt uncertain or draining. The controller represents a known quantity: a world where the rules make sense, progress is visible, and something good will happen if you keep going. Of course you reach for it.

The problem isn’t the reaching. It’s that the habit brain doesn’t distinguish between types of games, or between what you actually need in a given moment. It just knows “games feel better than sitting with this stress.”

There’s also a real difference between using a game to recover and using a game to avoid — and I don’t mean this in a preachy way, because I don’t think one is morally superior to the other. The difference is practical: they produce different outcomes. Conscious recovery means choosing something that addresses what you actually need. Avoidance means reaching for whatever keeps you from having to think about something you don’t want to think about. The game doesn’t resolve anything; it postpones it. You finish the session and the thing is still there, except now it’s later and you’re also tired.

I’m not here to diagnose which one you’re doing. But I’ve found it’s worth asking, genuinely, when I sit down: am I choosing this because it will help, or because it stops me having to think?

The browse, the guide, and the optimisation trap

Here is where I have to be more specific about my own failure modes, because they’re embarrassing in ways I find instructive.

The first is the browse that eats the evening. I’d sit down to play, open a launcher, scroll through the library, watch a trailer, read a few reviews, switch to YouTube to watch someone play something I was considering, and then it was too late to actually start anything. This happened in episodes spread across days — 20 minutes one evening, another stretch the next, never committing to anything. The choosing became its own activity, vaguely resembling the thing it was supposed to lead to but never arriving there.

At some point I had to be honest about what was happening. Part of it was decision paralysis. Part of it was something else: I was genuinely enjoying the content. Video essays, reviews, people talking enthusiastically about games — that’s actually interesting material. Once I accepted that watching gaming content is a legitimate form of entertainment in its own right — not a consolation prize for not playing, just a different thing with its own value — the guilt around it disappeared. I wasn’t failing to game. I was doing something else. Name it, own it.

The other thing I had to accept was simpler: most of the browsing wasn’t helping me choose. It was filling time with the feeling of being about to do something without doing it. The correct move was to pick something — anything reasonably suitable — and start. 20 minutes into an actual game is always better than 40 minutes of deciding.

The second failure mode is subtler and, if I’m honest, more developer-brained. I would sit down to play and immediately start optimising — reading about the best build before touching the mechanics, watching a guide for a section I hadn’t reached yet, looking up whether I was “doing it right.” There’s a well-known observation in game design that given the opportunity, players will optimise the fun out of a game. I am those players.

The problem is that optimisation replaces discovery with homework. The game stops being something you’re inside and becomes something you’re executing correctly. The first time you find a solution through genuine experimentation, or stumble into a moment the game was clearly designed to surprise you with, is irreplaceable — and I’d been consistently robbing myself of it by reading ahead. A suboptimal build that you actually played is better than the perfect build you spent an hour researching before touching the game. I know this. I still have to remind myself.

What different games actually do

Once I started noticing these patterns, I started paying attention to what different types of games actually did to my mental state — not in theory, but in practice.

Action-heavy games with fast feedback and constant stimulation are genuinely useful when I have energy I need to discharge. After a day where things went sideways and I’m carrying low-grade frustration, something loud and kinetic does something productive with that tension. The brain has somewhere useful to put the activation.

Slower, more atmospheric games — puzzle games, exploration games, anything with a calm pace and a gentle feedback loop — do something different. After a day that required a lot of decision-making and mental load, the last thing I need is more high-stakes decisions. A game that lets you wander, or think at your own pace, or solve small contained problems with no real consequences, turns out to be surprisingly restorative.

Story-driven games require emotional investment rather than simple relief, which makes them suited to a specific state: present enough to follow the narrative, calm enough to actually care. If I’m genuinely exhausted they don’t work — I end up half-watching and retaining nothing. But when the conditions are right, they provide something the other categories don’t.

And then there are games built around mastery and challenge — the kind where the whole point is to be bad at something until you’re not. These are energising in a completely different way. They require concentration and resilience to failure, which makes them the wrong prescription for a depleted evening but the right one for a Sunday afternoon when you have mental bandwidth to burn.

How you feel after is the data

The worst sessions — the ones where I stand up feeling vaguely worse than when I sat down — have a consistent pattern. I was overstimulated and played something that added more stimulation. I was exhausted but wanted to feel like the evening wasn’t wasted, so I picked something demanding, became frustrated, and achieved neither rest nor satisfaction. I was emotionally flat and needed engagement, but picked something mindless that left me more flat.

The game wasn’t the problem. The match between the game and my actual state was.

The useful data, I’ve found, is how you feel after. Not in the moment — the moment of playing is usually fine, because games are good at occupying you regardless of whether they’re helping. The question is whether you feel better or worse when you stop. If the answer is consistently worse for a specific type of game in a specific mood, that’s the game telling you something about when it’s the wrong prescription.

---

I wouldn’t call what I do now a system. It’s more like a habit of pausing for two seconds before opening something. Just long enough to register: how do I actually feel right now, and what does that probably need? And then — crucially — just starting. Not the perfect choice. Something reasonable, opened and played rather than endlessly considered.

Most of the time the answer is obvious once you ask. The asking is the part that took a while to become automatic.