What broke on stream, and why you saw it
We streamed a mid-week build session on Wednesday. I opened campaign mission 14 to show the new corridor lighting, and the door at the end would not open. The trigger volume was firing but the animation state was stuck on the closed loop. You saw the screenshot of the door, the console log, and the time on the patch file. Nobody edited the stream. Nobody hid the error. That is the part most studios would cut before posting.
The fix took 40 minutes. A teammate found the real problem in a state machine transition that we broke the night before while cleaning up old events. We pushed a patch and the timestamp on that file is 15:42 Tunisia time. You can compare the stream comment timestamps to the patch timestamp and see nothing was staged. That is not a marketing line. That is just what the file says.
The win for you is not that the door opens now. The win is that you never have to sit on a forum guessing whether the game is still being worked on. You saw the build fail, you saw the log, you saw the fix land. If someone asks how long does indie game development take, the honest answer is that it takes a lot of Tuesdays where the door does not open and then a Wednesday where it does. You get to watch both.
We could have skipped the stream. The door was broken before we started. We could have shown the working build from Monday and pretended nothing happened. That would have been easier and you would have learned nothing. The team agreed on the call that showing the broken door was more useful than a polished slice. You get to root for the fix instead of wondering if the fix exists.
Why a broken door is the answer to how long indie game development takes
People ask how long does indie game development take like there is one number. There is not. There is the time it takes to build a feature and the time it takes to find the bug that feature created. Mission 14's door worked for three weeks. Then it did not. The bug was not in the door. It was in a cleanup commit from the night before that touched a shared event system. That is normal. That is not a sign of a team falling apart. That is a sign that the team is still touching the code.
On the indie game development forum threads, you see two kinds of answers. One kind says it takes years and the other says it takes a weekend. Both are talking about different scopes. Our scope is a browser shooter with a 24-mission campaign, a wave mode called RUSH, and a territory mode called DOMINION. That scope takes time. But a single broken door in that scope took 40 minutes. The lesson is not that development is slow or fast. The lesson is that development is uneven. You need to watch it happen to understand the rhythm.
We started tracking hours on shared docs after a vote on the idea board asked for it. A player wanted to know how long a campaign mission takes us to build versus how long it takes to fix. The numbers are not heroic. One mission takes roughly a week of student hours spread across classes and late nights. One fix can take 40 minutes or three days. The door was on the lucky end. The lighting pass on mission 9 was not. You saw that one stall too.
None of this is a promise about dates. We do not promise dates we have not cleared with the team. What we can promise is that you will see the timestamp. If a patch ships, you see when. If a door breaks, you see the console. That is the only honest answer to the question. The speed is public because the work is public.
What the idea board has to do with a door in mission 14
The door fix did not come from a vote. It came from a player in chat saying the door looked wrong in the stream, and a teammate saying the log was already red. But the idea board is why the stream exists. Last month the top-voted idea was to show in-progress builds more often. It moved from Planned to Building in two days and we scheduled the Wednesday session. You voted for visibility and you got a broken door. That is the trade.
One vote per player. The board reorders live. If you want more streams, vote for more streams. If you want us to stop streaming and ship, vote for that. The board does not care about our feelings. We had a favorite weapon on the roadmap that got voted out and we cut it. A door fix is smaller than that, but the mechanism is the same: the community sets what we work on next and then watches us do it.
The other reason the door matters is that it keeps the studio honest. If we only posted trailers, you would never know how much of a week goes to bugs. When someone asks how long indie game development takes, we can point at the stream and say look at the last 40 minutes. That is not a number. That is a record. You can watch it again if you want.
For students reading this who want to break in, the idea board is also your window into the day to day. You do not need a studio job to see how a state machine breaks. You just need to watch someone fix it. That is more useful than a post-mortem written six months later. It is also cheaper. It is free in a browser tab.
What you get to watch next, and what still breaks
We are not done with mission 14. The door opens now but the animation is still stiff and the sound cue fires late. That is a separate task on the board and it is not at the top. The top right now is a pass on DOMINION matchmaking because players in India and on Mac are getting longer queues than they should. You can see the board. You can move it with your vote. You can watch us break that next.
For readers outside Tunisia, the time zone is not a barrier. The streams stay up. The patch timestamps stay up. If you are in India or on a Mac in a shared lab, you get the same log we do. Indie game development in 2025 and 2026 is going to look more like this for small teams: not polished reveals but public working sessions. We are just doing it earlier and with less budget.
What still breaks: the lobby occasionally drops a player on reconnect, the RUSH difficulty curve spikes at wave 12, and the Classic 2020 build has a shader warning we have not chased down. None of that is hidden. We talk about it every week. The door was just the one that got a screenshot because the stream was live.
If you want to see the next one, join the next session. Bring a bug. Bring a vote. The point is not that we are good at this. The point is that you can see us try, and you can tell us what to try next. The door opened. The timestamp is public. That is the win you get.