Bedroom Builders, Café Coders: The Quiet Game-Making Scene Growing in Gateshead

Gateshead does not have a games industry landmark. There is no giant publisher headquarters on the skyline, no neon sign advertising a studio campus. What it has is quieter and more interesting: a scatter of solo developers, modders and tiny teams making games in bedrooms, cafés and borrowed corners of co-working spaces.

You will not find them all in one directory. Some are students at Gateshead College. Some are hobbyists who started by modding racing games and never stopped. Some are two-person teams meeting weekly in a Low Fell café, prototyping on laptops and arguing about whether the jump feels right. The scene is small, but it is real. And it is at the stage where a little infrastructure could make a big difference.

The modder who puts local landmarks in the map

One maker I spoke to builds racing maps. Not the slick, branded kind, but tracks stitched together from memories of the borough: a tight corner near the Tyne, a stretch of road that feels like Dunston, a shortcut that only makes sense if you grew up around there. The tools are free. The audience is small. The feedback is immediate.

Modders are often the first game-makers a young player meets. They learn level design, balancing and community management before they ever call themselves a developer. Gateshead has plenty of people who can take a game apart and put it back together. What they need is somewhere to show the work without feeling like they have to pretend it is a startup.

The solo dev building in the gaps

Then there is the solo developer. They have a day job, a notebook full of ideas and a build that has been nearly finished for eight months. They test it with friends, then with strangers at a café table. They are not looking for a publisher yet. They are looking for ten people who will play the first twenty minutes and tell them where they got bored.

Solo development is lonely by design. You make the art, the code, the sound and the marketing. You also make the doubts. A regular playtest night changes that. It gives the work a deadline and gives the developer a room full of people who are not obliged to be nice.

The small team with a shared desk

The third group is the small team: two or three people, maybe a programmer and an artist, maybe a designer and a sound person. They meet in cafés because they do not have a studio. They use co-working spaces when they can afford it. They are the most likely to grow into something sustainable, but they are also the most likely to drift apart when life gets busy.

What they need is boring and practical: affordable desks, reliable wifi, a room that is open in the evening, and a reason to keep meeting. A regular showcase or a shared development night would do more than another online course. The borough does not need a flashy hub. It needs a front door.

What playtesting actually looks like

If you want to support local game-making, the easiest entry point is playtesting. Turn up. Play the build. Fill in the form. Describe what confused you, where you got stuck and what you wanted to do but could not. Do not just say it was fun. Fun is useful, but confusion is more useful.

Good playtesting is specific. Note the moment you stopped reading the tutorial. Note the button you pressed by mistake. Note whether the text was big enough on a laptop screen. If you have access needs, say so. Small teams often cannot afford dedicated accessibility testing, and a thoughtful note from a player can change a design decision.

You do not need to be an expert. You need to be willing to be honest without being cruel. The best feedback sounds like: I liked this bit, I got lost here, I would have stopped playing if I had not been asked to finish.

How to support without being weird

You can wishlist a game on Steam. You can follow a creator on itch.io. You can share a demo with one friend who likes that genre. You can buy a small game for the price of a coffee and then actually play it. You can offer a venue for a playtest night, or volunteer to take notes while someone else plays.

If you run a café, a community centre or a library, you can offer a table and a power socket. If you teach, you can invite a local developer to talk to students. If you have a skill, from accountancy to audio, you can offer an hour. The scene does not need saving. It needs people to treat it as part of the borough's culture, not as a hobby that happens behind closed doors.

What Gateshead still needs

The gaps are not mysterious. A regular showcase with late opening and decent power. A playtest night that is not in a pub, so under-18s can attend. Affordable co-working that does not require a commute to Newcastle. A bridge between Gateshead College and local makers. Simple advice on grants, tax and collaboration. And a shared calendar so people stop missing each other.

Most of all, Gateshead needs a front door: one place, physical or online, where someone can find out who is making games locally and how to join in. That is not a grand ask. It is the difference between a scatter of bedroom builders and a scene that can welcome the next one.

The game-making map of the UK often skips places like Gateshead. It should not. The borough has the people, the ideas and the stubbornness. What it lacks is a bit of connective tissue. That is a problem we can fix locally, one playtest, one shared desk and one open door at a time.