Tower Blast! began with levels.
There were goals, boundaries, and the familiar promise of a next stage waiting behind the current one. It was a sensible shape for a puzzle game. It was also getting in the way of the part we liked most.
The moment that kept pulling us back was not finishing a level. It was rotating the tower, seeing a ring almost close, dropping the right block, and watching the whole structure answer with a blast.
So we asked a dangerous production question: what if the rest of the game moved out of that moment’s way?
The level map was solving the wrong problem
Levels are useful. They can introduce mechanics, create authored challenges, and give progress a visible staircase.
But every structure has a cost. Our level goals kept turning attention away from the tower’s natural rhythm. Instead of asking, “What is the most satisfying move on this board?” we were asking, “How quickly can the player complete this external objective?”
The answer made each session feel segmented. A run would begin to flow, then stop because the level had done its administrative job.
That friction showed us the game’s actual promise: not a sequence of puzzles, but an endless conversation with one changing tower.
What we removed
Moving to endless mode was not a menu change. We removed assumptions from the entire loop:
- no fixed level endpoint;
- no map that dictates the next session;
- no authored wall that interrupts a good run;
- no energy timer deciding when the player can try again.
Taking those away exposed every weak transition. Without a level-complete screen, the core loop had to carry its own momentum. The difficulty curve had to grow without feeling like a staircase. Themes needed to make a long run feel alive without resetting the world.
Removing structure created more design work — but it was the right work.
What we gained
The tower became the progression.
As a run develops, the state gets more demanding, the visual themes move through different skies, and every cleared ring opens space for the next decision. The score is not a checklist; it is a history of how long you kept the system under control.
That makes failure cleaner, too. There is no feeling that the player missed a developer-authored solution. There is only the tower they built, the pressure they managed, and the high score waiting for another attempt.
The result fits the game in one sentence:
No levels. No walls. Just you, the tower, and one more run.
The courage to delete
Indie development is often described as adding the feature that makes a game special. Sometimes the most important decision is deleting the structure that keeps the special part from breathing.
We had already spent time on the level-based version. That work was not wasted. It taught us what the game was not.
The key was listening to repeat behavior. Which moment did we want to test again after the task was complete? Which interaction survived every revision? Which part still felt good without a reward screen explaining why it mattered?
The tower answered all three.
The loop now
Rotate. Read the gaps. Place the block. Complete a ring. Let gravity turn one clear into another. Watch the world shift as the run grows.
That is Tower Blast! now.
It is smaller on paper and much larger in motion. The structure no longer announces progress from outside the game. The game itself becomes the progress.