Earlier this year I wrote about Sango: The Thunder God, the mythology-inspired platformer I first built in 2018. Since then I have rebuilt the whole game from scratch in Godot 4. It’s out now on Android, iOS and Windows, and you can play it in your browser.
The game
The eternal flame that kept evil spirits out of the village has been stolen, and Ṣàngó, god of thunder, takes up his axe. You play through four worlds and twenty levels to recover the flame, cleanse a poisoned river, break a warlord’s gate and climb a mountain no one has climbed, with a named guardian waiting at the end of each world.
Combat is a three-hit axe chain, a heavy blow, a ground slam, a dash, and two screen-clearing ultimates: Call the Storm, which drops a dozen bolts across the screen, and Ruin, a detonation of fire. Each guardian fight has phases and an arena that turns against you, with a flood, falling spears or rolling boulders. Alongside the story there is a Survival mode with online leaderboards.
I wanted the mythology handled with care. Ṣàngó’s axe is modelled on the real òṣé Ṣàngó, the carved double-bladed wooden axe held in museum collections. Thirty-two collectible scroll cards each carry a fact about Ṣàngó and the Yoruba world and name their source. The villains are original inventions, and no òrìṣà is cast as a demon.

Why Godot
For the reboot I wanted full control over combat feel, level design and tooling, and builds for several platforms from one project. Godot 4 gave me that. It’s open source and light, it exports to Android, iOS, Windows and the web, and typed GDScript is easy to read at a glance.
How it’s built
The architecture follows a few rules I set at the start:
- Composition over inheritance. Behaviour lives in small component nodes (health, hurtboxes, hitboxes, movement, abilities) attached to each character, not in deep class hierarchies.
- Data out of code. Tuning values live in Godot resource files, so balancing a boss or an ability means editing data, not scripts.
- Presentation follows gameplay. Animation, effects, audio and camera shake react to gameplay signals. Gameplay never waits on an animation to know whether a hit landed.
- Few globals. Five autoloads for things that really are global, like saving and audio, and no global event bus.
- Small enough to change in one or two files, whether the change comes from me or from an AI assistant.
The game has 20 levels in 4 worlds, 4 boss fights, a 12-panel intro and cutscenes for each world, 14 music tracks, 3 ambience beds and around 40 sound effects. Sponsorships, redeem codes and other online features run on a small Cloudflare Worker backend in TypeScript, with a D1 database and R2 storage.

Testing a game with a bot
A platformer has plenty of ways to go wrong that only show up when someone plays it. Besides headless unit tests, the project has an automated play harness: a bot that walks every level, fights, jumps and reports where it died. It found real level problems, like a ranged enemy on a low shelf that turned the space under it into a cage, and a wide pit that killed every time its run-up was broken. It also found faults in itself that looked exactly like level bugs, which taught me to check the bot before blaming the level.
Bugs worth remembering
Some bugs only appear on a real device or in an exported build. A few from this project:
- An enemy’s corpse floated above the floor because its sprite was anchored on the weapon it dropped.
- A footstep sound was wired correctly and fired on time, and measured -51 dB, so nobody could hear it.
- A menu passed 42 automated checks while being drawn zero pixels wide.
- On iPhone only, a level loaded on a background thread came back with a tileset that had no source, so there was no ground under the player. The same build ran perfectly on a Mac.
- A body crushed by a moving platform ended up at a position of NaN, and stayed there.
Each one became a written rule in the project’s notes, so it would not be rediscovered the hard way.
Building it with Claude
I built the reboot with Claude as a working partner: a project context file, prompts that ask for evidence instead of guesses, and the habit of measuring things instead of arguing about them. I wrote up what worked in two courses, Zero to Hero for beginners and The Advanced Masterclass for experienced developers.
Play it
Sango: The Thunder God is on Google Play, the App Store and the Microsoft Store, and in your browser. The launch was covered by THISDAY, Techpoint Africa, P.M. News and Vanguard.



