Inspiration
I came up with this game while making up a story with my son one evening. We were imagining what happens on a beach after everyone goes home, and the story we landed on turned into the opening of the game.
Two kids spend the whole day at the beach. They collect shells, look for starfish, and build a big sandcastle. When it's done they put their toys on top and start playing knights, like it's a medieval fortress. Then a cursed starfish crawls up to the castle. The kids get scared. A bunch of cursed crabs comes up behind it, and the kids run off home, leaving their toys lying in the sand by the castle.
You play as one of those toys (your avatar). A little figurine left behind, the last knight standing, defending the sandcastle while the cursed tide keeps coming in.
That picture, a forgotten toy holding the line on a darkening beach, is where everything else came from. It's the reason the game is cozy and a little silly instead of scary. The monsters are only as scary as a kid imagines them, and the hero is a brave little toy.
What it is
A cozy, comedic tower defense for mobile. You don't just place your weapons and watch them work. You run along the walls, hammer your cannons back together when they break, and decide whether it's worth leaving your spot to grab a power drop while the cursed tide rolls in. You hold the castle through one full day into night. Win the day and your sandcastle gets rebuilt bigger, and each time you play you keep growing it.

How I made it
This is a design entry, so instead of a playable build I put together a full design package: a Game Design Document with the concept, the core loop and the progression; a Player Journey Map that walks through the first 15 minutes step by step; a Production Plan that scopes a small first version, the build order and the risky parts; and a Visual Concept Package for the warm, golden afternoon look.
I started from the story and worked outward. The idea of a tiny toy defending the castle became the active core loop where you run, repair and take risks. That led to the two kinds of currency (shells you earn inside a run, pearls you keep between runs) and the castle that visibly grows as you win. After that I mapped out the first play session and figured out what a small team could actually build first.
The hard parts
Keeping the warmth was the tricky one. It would have been easy to turn a sweet little story into just another scary defense game, or a grindy mobile one, and I really didn't want either.
Making a tower defense you actually play was the other one. The genre pulls you toward setting things up and watching. The repairing and the risky power drops are there to keep your hands busy and your heart rate up.
I also wanted the reason to come back to feel fair. The pearls and the weekly tournament are things you earn by playing, never things you buy, so the game stays relaxed and friendly.
And then there was scoping. I had to decide what to cut so the main loop could be tested in a couple of weeks, and leave the bigger meta and social features for right after.
What I learned
A good story does a lot of the design work for you. Once I decided you're the toy that got left behind, a lot of questions answered themselves: why you defend a sandcastle, why the creatures are cursed, why it all stays cozy. I also saw how much keeping every document consistent forces you to think things through properly. The story ended up being the thread that ties all four pieces together.
What's next
Build the first version, then add the meta progression and the weekly tournaments. The opening story is just text for now, but I wrote it so it could grow into a short animated trailer later. And there's already a hook sitting in that first scene: there were two kids and two sets of toys, so a cooperative mode where a second figurine joins you to defend the beach is where I'd take it next.




Log in or sign up for Devpost to join the conversation.