A developer has recreated Contra using a custom NES game engine built from scratch, and the engine itself is the real story. The project, posted to Hacker News by user normalocity, demonstrates a tiny engine called `neo8` that compiles to native binaries on Windows, Mac, and Linux with zero dependencies. It cannot run NES ROMs. It was never meant to.
Why Build a New Engine for Old Hardware
Original NES games were written in assembly without game engines. The developer wanted to create new games that feel like NES titles but run on modern hardware, using a high-level language instead of 6502 assembly. Existing emulators preserve the original experience perfectly. Porting Contra directly from ROM to Rust would achieve the same result. Neither approach helps someone build something new.
The goal was a minimal foundation: sprite rendering, input handling, sound and music, a basic camera, entity modeling with animation state machines. Just enough to start building. The Contra recreation served as a stress test to prove the engine could handle that specific gameplay style.
How the neo8 Engine Works
The engine centers on a few core systems. A polling and event-based input handler maps physical inputs to in-game events. An event-driven sound system handles music and effects. Entities carry attributes, rendering logic, and animation state machines. A basic camera system follows the action. The whole thing compiles to a single binary per platform.
To build the Contra demo, the developer wrote analysis tools that extract assets from an actual ROM: sprite sheets become PNG files, audio becomes MP3, and code structure becomes high-level source. That source then compiles through `neo8` into the playable demo. The extraction step is one-time work. The resulting codebase is independent of the original ROM.
AI-Assisted Engine Development
The developer described the NES hardware capabilities to an AI agent — sprite limits, input registers, audio channels — and had the agent generate the initial engine structure. This included the entity system, the rendering loop, the input abstraction, and the sound scaffolding. The human then refined and extended it. The AI handled boilerplate; the human made architectural decisions.
What This Means for Homebrew Developers
For developers targeting retro aesthetics on modern platforms, `neo8` offers a different trade-off than existing options. Fantasy consoles like PICO-8 impose artificial constraints. Full engines like Unity or Godot carry massive overhead. Custom C++ engines require building everything from scratch. This engine sits in a narrow middle ground: it enforces NES-like constraints by design but runs natively everywhere without an emulator layer.
The zero-dependency binary output matters for distribution. Players download and run. No runtime install. No browser required. The engine itself is small enough to understand completely, which matters when debugging edge cases in gameplay logic.
The Difference Between Preservation and Creation
Emulators preserve. Ports translate. This engine creates. The distinction shapes every architectural choice. An emulator must replicate cycle-exact behavior. A port must match the original code's logic. A creation engine only needs to feel right — same jump physics, same enemy patterns, same screen transitions — while giving the developer modern tools to express new ideas.
The Contra demo proves the feel is achievable. Whether the engine sustains a full original game remains to be seen. The developer has not released the source. The Hacker News post includes a demo video with audible coughing and compressed audio, recorded for a friend and reposted on a whim. Sometimes the most useful tools start as private experiments.