Rootbound is a solo game jam prototype for the Gamedevtv 2026 jam. The theme for the jam was Connections. I'm using godot 4.6.

My core idea: 

Player is a potion shop owner. Potions are created by routing a magical companion AKA the bee through a magical garden, gathering nectar. The nectar each flower has stats that contribute to the potion, and the bee is able to ''pollinate'' each flower pair in the route, creating hybrid or better offspring. 

The starter flowers contain 1 stat, hybrids contain 2 different stats, and greaters contain 2 of the same stat.  

My original scope was meant to have more than 3 stats meant to mirror classical RPG stats, but that proved too hard to balance around in the jam's time, so I dropped it back to the 3 core stats most RPGs have.  The original amount was 6 stats with phys/magical defense and mana capacity as stats. The idea was to have full parties of adventurers past day 3. Customer requests were meant as vague phrases, like ''I need something  to impress my friends, they think i'm weak'' (+ATK) or ''we will hit the warlock's dungeon tomorrow, we know we can burst him down but we are worried about getting to the boss room at all'' (+Mana + defenses + hp).

What made it into the jam build

The final jam build is very prototype-y, but it does contain the core loop I wanted:

1. A customer asks for a potion.
2. You select a route through unlocked flowers.
3. The selected flowers add up into potion stats.
4. If the potion meets the customer’s needs, you earn score and advance.
5. The connections between selected flowers add progress toward unlocking new plants.
6. Over time, the garden opens up with hybrids and greater flowers. 

I took the jam as a learning oportunity, I'm an experienced dev that has worked in more ''traditional'' fields like FW optimization and computer vision, so this was interesting. The game is data-driven, customers, plants, unlocks and days are all godot resources. Spinning up a new customer for a day, or a new day for the run ended up being pretty easy as it's just creating a new resource. New plants are a bit more complex since the overall layout is meant to be a bit intuitive in terms of hybrids going between their relevant parents, so it's more of a geometry problem than just coding. 

The connection mechanic

The part I like most is that routes have two meanings.

A route is not just “what potion do I make?” It is also “what future flower am I working toward?”

For example, connecting Vitabloom and Fanglily progresses Vitafang. Connecting the right hybrids later can unlock a greater flower. This made the jam theme feel mechanical instead of just decorative.

The idea of “Connections” ended up existing in several layers:

• connecting flowers into a route
• connecting flower traits into hybrids
• connecting today’s customer request to tomorrow’s garden growth

What was hard

The hardest part was UI clarity.

This game asks the player to understand three things at once:

• what the customer wants
• what the current route will brew
• what the route will unlock

I'm terrible at anything UI related so I'm happy this ended up being understandable from playtests with some people. Balancing started out tricky but ended up being just another math problem. 

Art and assets

I ended up creating the plant sprites myself, which was a fun part of the process. I suck at it but I think they turned up nicer than anticipated.

The bee asset comes from Elthen (link), the character portraits are from CraftPix, and the sound effect is from Cyberwave Orchestra. No AI generated assets have been used. 

What I would improve next

If I continue RootBound after the jam, the first improvements would be:

• clearer tutorial/onboarding
• better route visualization
• more readable customer cards
• better feedback when a potion succeeds or fails
• clearer unlock progress presentation
• balance pass on hybrid and greater flower unlock costs
• more polished end-of-run score screen
• more customer variety

After that, I’d consider adding features that were cut from the jam version. I'd love to have a deeper stat pool and progression, and go back to vague requests so score actually means something. 

Final thoughts

RootBound is rough, but I’m happy with where it landed.

It started as a much larger cozy shop concept and became a focused little prototype about brewing potions through flower connections. It is definitely still a jam game: messy in places, under-polished in others, and full of things I would do differently with more time.

But the core idea made it in.

You connect flowers, brew potions, help adventurers, and grow a better garden for tomorrow.

For a chaotic jam sprint, I’ll take that.