Build a 16-bit beat 'em up in Godot over six months with Codex

A Redditor spent about six months building INVICTA 2034, a pixel-art beat 'em up set in a dystopian Porto, with Codex writing most of the Godot code. A playable demo is out for browser and Windows.

Done withCodex· Nov 10, 2026

What they did

The poster, a musician by background, directed the development of a 16-bit style beat 'em up and action RPG in the Godot engine while Codex wrote most of the code. They came up with the mechanics, tested builds and steered Codex through combat work such as enemy behaviour, lane positioning and critical hits. Backgrounds started as the poster's own photos of Porto, turned into pixel art with Nano Banana, and Codex helped fix the perspective so the scenes fit the character's scale. Character animations came from Google Omni green-screen videos converted to sprites in Aseprite. The poster wrote the whole soundtrack.

How it went

After roughly six months there is a public playable demo on itch.io, in the browser and for Windows, and the poster pushed version 0.1.10 with combat fixes during the thread. Commenters who played it liked the art and music. One found the combat slow, with enemies walking into punches, and the poster agreed it is still basic. They also say they lost time redoing things that already worked.

Worth knowing

Codex handled code and fitting the art into the engine, not the art itself: the sprites and backgrounds came from image and video models plus manual work in Photoshop and Aseprite. Getting consistent animation across one character's moves was the hardest part. Matching backgrounds to the character's proportions took a lot of trial and error.

Try it

With Codex· 5 parts to fill in

You are working in my Godot project for [game name], a [genre] game. Read the project structure and the scene for [level or system] first. Implement [mechanic, for example enemy lane positioning or critical hits] in GDScript, keeping existing behaviour working. Explain what you changed and which scenes I should playtest. Do not change art assets or scene layout outside [folder]. Stop after the change and wait for my playtest notes before the next mechanic.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related