Skip to content
Overheard

What do streamers struggle with most in indie games?

Published · Numbers as of

In 259 Twitch streams of 46 indie games in the week of 21 Sept 2026, we recorded 906 distinct problems. 211 of them (23%) were about unclear rules, controls and item effects: a key, a rule or an item the player didn't understand. They came up in 45 of the 46 games. Next came bugs, crashes and performance (13%) and hard-to-read screen or menu (13%).

A language model sorted our short problem titles into these categories. The titles say the player was unsure, not whether the game explained the thing somewhere they missed.

All problems by category

906 distinct problems from 46 indie games. A problem is counted once per game, however many streams it came up in. Shares are rounded.
What the player ran intoProblemsShareGames
Unclear rules, controls and item effects21123%45
Bugs, crashes and performance11813%41
Hard-to-read screen or menu11513%43
Economy, rewards and grind9911%33
Difficulty spikes and unfair moments9210%33
Controls and camera586%29
Not knowing what to do or where to go516%28
Tedious chores495%29
Multiplayer and lobbies455%20
Sound and visuals that grate364%24
Other324%17

What confuses streamers

Of the 405 distinct confusion problems, 194 (48%) were about unclear rules, controls and item effects. Typical ones from the list: whether taking a key ends the run, which items you lose when you die, what the icon above a character's head means, and why a flashlight recharges slowly.

What frustrates streamers

Frustration comes from somewhere else. Of the 400 distinct frustration problems, 94 (24%) were about economy, rewards and grind, such as money that runs out before the next upgrade or a battery that drains too fast, and 83 (21%) about difficulty spikes and unfair moments. These titles are mostly about prices, resource rates and challenge. Watch the minute in the VOD before you decide whether the fix is tuning, feedback or an instruction.

Examples that came up in several streams

One per category except Other, from our game pages. The titles are our summaries of what the streamers ran into.

Streams of the game in which the problem came up, out of the streams we analysed.
GameProblemStreams
PratfallBean and item pickup effects are not explained when picked upUnclear rules, controls and item effects4 of 8
How to FishHeld tools and caught creatures go missingBugs, crashes and performance2 of 3
DressmakerHard to tell pattern pieces apart and track which are cutHard-to-read screen or menu3 of 3
Species: UnknownFlashlight battery drains too quickly, leaving areas darkEconomy, rewards and grind4 of 7
a weird game about sausageWall level is far harder than every other levelDifficulty spikes and unfair moments4 of 8
Denshattack!Trick and jump presses get dropped or misreadControls and camera3 of 5
GraveboundTime limit, closing storm and extraction point are poorly signpostedNot knowing what to do or where to go3 of 4
How to FishHunger drops fast and forces constant eatingTedious chores3 of 3
Funnel RunnersFriends fail to join a multiplayer session due to invite errorsMultiplayer and lobbies4 of 8
the cabin gameClock and event sounds are too loud and hard to controlSound and visuals that grate3 of 8

What to check in your own demo

  1. List every key, rule and item effect a new player needs in the first half hour, and find the moment the game shows each one. Mark the ones you can't find, then watch a first-time player reach them.
  2. Look at your screen with the sound off and ask someone who hasn't played to say what each icon and number means. Hard-to-read screen or menu made up 13% of the problems in our sample.
  3. Play the first session with the resources a new player has. If money, ammo or a battery runs out before the next upgrade is in reach, a streamer will likely say so on camera. Economy, rewards and grind was the largest source of frustration in our sample.
  4. Watch for the problems that repeat across streams first (how to use Next Fest streams as a playtest).

How we counted

Every game page lists the problems streamers ran into, each a short title written from the transcripts. We took all 906 problems (confusion, frustration, bugs and quitting) from 46 games and had a language model put each title into one of 11 categories we set before sorting. It saw only the titles, not what the streamers said. An AI-assisted read of 50 random assignments flagged 1 clear error and 2 borderline cases; an independent review of 80 more found 2 to move. We changed 6 assignments by hand in total, including a few found outside the samples. We did not check the assignments against the VODs.

What this doesn't tell you

  • Shares a point or two apart are within the sorting error. Under these definitions the top category leads by a wide margin; the order of the smaller ones could change with a different sorting.
  • Most problems were seen once. Only 134 of 906 came up in two or more streams of the same game, so the counts are problems we recorded, not complaints confirmed by several players.
  • “Bugs, crashes and performance” includes things a player took for a bug. We didn't reproduce them in the games.
  • Games with more streams have more problems, so the numbers lean towards the games with the most streams. These are 46 games picked from Twitch in one week of September, not a sample of all indie games.

The numbers come from our own data, counted by a script on the date above. Overheard is run by Mateusz Woskowicz, an independent developer in Poland.

Overheard finds the Twitch streams of your Steam game or demo and tells you where streamers got stuck, what broke and what they liked, each with a link to the minute in the VOD. See a sample report.

Demo in the October Next Fest? Send us its Steam page (form on tally.so): we email you when enough streamers have played it, and you decide then whether the $49 report is worth it.