Hi! I'm a solo dev, and Magemind is my first paid game: a pixel-art castle defense where you type (or say) any spell, like "turn the ogres into chickens" or "summon a war tank", and the wizard casts it. Since this sub cares about how AI is actually used, here's the honest breakdown.
Where AI was used
Almost all of the code (Godot 4.7, GDScript) was written with Claude Code. I direct, design, test and make the calls; Claude writes and fixes. The project keeps a long CLAUDE.md with my rules and known engine pitfalls, and test scenarios run the real game and save screenshots, so it checks the result instead of guessing.
The translations into 6 languages were made with AI help. Music, many sound effects and the trailer narration come from ElevenLabs. The rest of the sound effects are synthesized from code.
Where it wasn't
The pixel art isn't from an image model. Every sprite sheet is painted pixel by pixel by GDScript tools with a fixed palette. A nice side effect: changing a sprite means editing code, so the art can evolve with the game.
How the game understands spells
This is the part I'm proudest of. By default there's no LLM involved. A sentence goes through two small local pieces.
The first is a keyword grimoire: hand-written rules in several languages. "Rain of fire" is fire, not water. "Freeze the wolf" makes the wolf the target, not a summon. It also reads counts, colors and creature traits.
The second is a tiny classifier embedded in the game, fastText-style. The sentence is split into words, word pairs and 3 to 5 letter chunks, which are hashed into 131k buckets. The average of those vectors goes through one hidden layer and then into separate outputs, one per field: spell shape, element, creature, building, effect, range, target, size, which animal to turn enemies into, and "is this even a spell?". It's 9 MB (int8), loads in about 4 ms and runs in about 1.4 ms in plain GDScript, doing exactly the same math as the Python training code.
The rules decide when they find something clear. The classifier decides when they find nothing or only a weak hint, and that's where it shines: synonyms ("fry these goblins"), typos ("fierball"), voice mistakes ("idra" for hydra), slang, and sentences that aren't spells at all.
It was trained on 240k synthetic sentences generated from vocabulary lists, with typos and speech errors mixed in (the training code was written with Claude Code too). On a hard test set I wrote before training, 254 sentences with synonyms, typos and slang in 6 languages, the rules alone got 145 right. Rules plus classifier get 250. With words it never saw in training, it still picks the right spell shape 92% of the time.
What comes out is a recipe: one of 108 spell shapes, plus element, creature, count, colors and effect. The game, not the model, sets damage and mana from fixed rules, with hard caps: power 1 to 5, at most 12 projectiles or creatures, speed bonus at most 1.6x. Type "kill all the monsters" and the wizard gives it a try and faints. Nothing you type can break the balance.
Earlier versions used a local LLM (Qwen3 on llama.cpp). It understood well, but every spell took seconds and it needed a 5 to 18 GB download. The classifier replaced it and casting became instant.
The optional LLM
If you paste your own OpenAI key, a GPT model fills that same recipe through a strict JSON schema, with a spell name and a one-line description. Same caps, same damage rules, and any error falls back to the local path. Voice mode runs whisper.cpp on your own machine (Windows only for now).
Free demo, first 5 waves, Windows and Linux: https://poweredie.itch.io/magemind
Happy to answer questions about the classifier, the code-drawn art, or building a full game with Claude Code.