I Am Ball. I Must Bounce.
- Year
- TBC
- Platform
- TBC
- Engine
- Godot










I Am Ball is a fast, unforgiving, incremental arena dodger built in Godot. You play a ball with momentum and bounce. You will die easily and you will die often, but you will come back stronger.
The Corporation did this to you, and you want revenge. Destroy all seven members of the Shadow Council and tear the Corporation apart from within. Enter each member’s domain, find their power source, a golden ball, and smash it. Survive their anger, then roll on to the next round. Reach round 10 and take down the final boss.
Bounce, roll, dash and smash your way through hordes of mindless pencil pushers, until they aren’t mindless anymore and start to grow personalities of their own. Once promoted, these balls grow stronger; remembering you and every encounter. Each time they kill you, they grow in power… and in cockiness. Kill them before they get too strong, or suffer under their ever-growing strength.
Core Loop
Each run is 10 rounds. Find the Golden Ball and smash it, then survive the Angry Red to clear the round and advance. Simple? Not quite. Every round brings more enemy balls and more kinds of them. You start slow and weak, so collect coins and spend them in the Upgrade Tree to turn yourself back into the unstoppa-ball you once were. Each time you die, you return a little stronger.
The heart of I Am Ball. I Must Bounce is the elite promotion system. At any moment, a nameless ball can be promoted, gaining abilities, a personality and a name. From then on it haunts you until you take it down. It will remember every encounter you’ve had, so don’t give it any more material than it already has.
LLM Explorative Integration
As an experiment, I integrated an LLM (Deepseek) to write dialogue lines for elites with the purpose of pushing the existing system to be more personal. I wanted elites that remember situations and comment on them, to alter the player's relationship with these enemies. Each elite will keep a persistent log of hits, near misses, explosions, kills, and escapes - a returning ball can bring up these previous encounters.
The system is designed with fallbacks, guardrails, stored previous encounters and authored personalities:
- Personalities: Data defined traits have a one-line voice instruction
- Fallbacks: Every generated line has hand-written fallbacks that play after a failed request
- Protected story: Authored characters and bosses ignore this system
- Bounded prompts: Generated with only a supplied packet of game data.
- Tuning: Every request and reply is logged for later prompt tuning.