A gap in the games market isn’t a green light
Arcade combat racing raises a useful question: does a quiet genre contain an opportunity, or an assumption you have not tested?
In this article
First, look beyond the labelGive the awkward explanation a seatMake the test capable of disappointing youKeep the next commitment small enough to changeSources and scope“I do not know yet whether the gap is big enough to carry a company.” That line comes from Project Turbo Combat’s discussion of arcade combat racing. The team describes a game it wants to play, then admits the commercial question is still open. That is a much more useful starting point than declaring a genre ready for revival.
A quiet shelf can make a pitch look wonderfully tidy. Fewer rivals. Room to stand out. But where are the players, and what are they choosing instead?
A small competitor list does not establish unmet demand. Before committing to a genre gap, test the player need, the substitutes your search may have missed and whether your team can deliver the experience.
When I was tasked with building a mobile studio inside a legacy publisher, greenlight meetings brought budget pressure without enough data behind our game choices. I’ve shared that experience before. An empty patch on a market map would not, on its own, have answered the difficult question.
Can we justify the next commitment? That is the question I would bring into the room.
First, look beyond the label
Take arcade combat racing on Steam. For this discussion, the proposed experience is recognisable cars, accessible racing and weapons. That is a research boundary, not a claim that every player uses the same genre name.
GRIP: Combat Racing describes weapon-equipped racing with wheeled and airborne vehicles, including driving on walls and ceilings. Wreckfest describes demolition derbies, vehicle damage and track racing. They offer different experiences, but both complicate a simple story about an empty space between simulation and kart racing.
Those descriptions are verified store evidence. Whether either game satisfies the audience you want is still a hypothesis. Neither listing establishes how many people would buy your game.
Valve’s tag documentation explains that developers, players and moderators contribute tags, with only the top twenty visible. One tag search is a place to begin. Ask players which games they actually turn to, including ones that never appeared in it.
Give the awkward explanation a seat
Project Turbo Combat’s post does something worth borrowing: it invites the strongest counterargument. Its uncertainty is public. Its eventual results are not established by the post.
I would put several explanations beside the attractive one before funding more work. The point is to make each explanation earn its place, including the one you hope is right.
Proposed tests, not findings. All demand explanations remain unresolved.
| Possible explanation | Evidence to look for | Contrary evidence / next test |
|---|---|---|
| An audience is waiting | Players describe a specific unmet experience and choose to return to it. | Existing games already satisfy that need. Ask players to compare, then observe a replay choice. |
| The search missed substitutes | Players name relevant games outside your chosen label. | Wider searches still miss the experience. Search by activity and ask what players use instead. |
| Nostalgia exceeds appetite | People praise the idea but choose something else when given a playable build. | They return without prompting. Test behaviour as well as the remembered favourite. |
| The promise exceeds the scope | The required handling, content or online experience exceeds your team’s plan. | A bounded prototype delivers the appeal. Test the expensive dependency before adding content. |
These possibilities can coexist. You may find interested players and an unaffordable production plan. You may find a viable smaller game serving only part of the audience. A genre verdict hides those decisions.
Make the test capable of disappointing you
Suppose the claim is that racing players want recognisable cars with weapons but find current options unsatisfying. That is specific enough to challenge. “There’s a gap” is not.
Recruit people who play the neighbouring games as well as enthusiasts for your idea. Find out what they currently choose and what frustrates them. Show a playable slice of the promised experience. Then give them a genuine choice about playing again.
A compliment is encouraging. A voluntary return answers a different question. Record who was invited, who played, who returned, the build and the observation window. Keep the people who declined in the record. A handful of keen volunteers cannot tell you the size of a market.
Set a time and spending limit before testing. Write down what would make you change course. If players understand the offer but keep choosing their existing game, that is evidence to investigate. If they cannot get through the controls, first resolve that failure; you have not yet tested the appeal cleanly.
The useful outcome is permission to make a better next decision, including a smaller one.
Keep the next commitment small enough to change
Continue when the intended players demonstrate the behaviour you set out to test and the next milestone fits your resources. You have a reason for that milestone, not proof of a successful launch.
Narrow when interest centres on one mode, audience or part of the experience. Preserve what the evidence supports and reduce the promise.
Stop or change direction when repeated tests weaken the core need, or delivering it exceeds what the team can sustain. Record what would justify revisiting it.
For a sequel, port or new IP, the discipline is the same: say which decision the evidence supports. Do not let enthusiasm for a genre approve the whole production plan.
Blank worksheet · enter your own verified inputs
The case you can challenge
Hypothesis
Which players lack which experience?Supporting evidence
What did you observe, from whom?Contrary evidence
What weakens the claim or supports a rival explanation?Source / date
Record the link or test, build and observation window.Limitation
Who is missing? What can this evidence not establish?Next test
Name the owner, time/cost limit and result that changes the decision.
Before your next greenlight discussion, write one competing explanation and one test that could disprove your favourite. Give both to someone willing to challenge you.
An interesting gap deserves investigation. Your team deserves a reason for the time and money you ask them to put into it.
Sources and scope
Public sources checked 12 October 2026. This is an opinion and proposed decision method for indie creators and small/medium studios, using arcade combat racing on Steam as the example. It is not a genre-demand study. No complete competitor count, sales estimate or claim of oversaturation is made.
- Project Turbo Combat: why this genre? Project Turbo Combat, LinkedIn. Opening quotation and the team’s stated uncertainty. Displayed “1d” when checked; exact publication date not independently verified. A developer’s own account, not validated demand or published test results.
- The Silverback greenlight account. Gameloom company page, LinkedIn. Source of the brief personal account; supplied as Dougie’s voice sample. Displayed “3w”; exact date not independently verified.
- GRIP: Combat Racing - Steam. Caged Element / Wired Productions. Described vehicle, racing and weapon mechanics; page publication date unstated.
- Wreckfest - Steam. Bugbear / THQ Nordic. Described demolition derbies, damage and racing; page publication date unstated.
- Steam Tags - Steamworks Documentation. Valve. Living documentation on tag contributors and visibility.
Game descriptions establish advertised mechanics, not audience overlap or commercial viability. Examples are deliberately selected, not a representative sample. The illustration, hypothesis table and worksheet are original editorial aids; none contains measured market quantities.
