Latest Article
Minimal engine file formats of Conspiracy intros
by BoyC / Conspiracy
The final executable for a 64k intro is nothing more than the engine packaged together with a datafile and its loader. The loader parses the datafile and builds up the structures and resources required by the engine to run the release the same way it does in the tool. Separating the code and data this way is **one of the key insights** in creating a modern 64k intro - the compressibility gains are insane. This article is a summary of our experiences with minimal file formats as we've been through a couple iterations.
## Problem Definition
Like any data driven piece of code, a 64k engine works by having certain data structures and resources in memory that it evaluates during execution. While working in the tool these structures usually have some additional metadata that helps the editing process, but isn't actually needed for demo playback (think of things like names, graph node location, organizational folders, etc.).