Save System
Not implemented yet in GalaxyEggbertCNA; an open design question for CNA specifically.
Not implemented, and not fully decided
GalaxyEggbertCNA has no save/load code at all — there is no lives count, no world
progress, and nothing to persist yet since there's no real gameplay. Even for
GalaxyEggbertSimple3D (which does implement save/load), whether to reuse
mobile-eggbert's exact byte-level save format for cross-compatibility is documented in
CLAUDE.md as an open question, not a default — see easy3d.md §12 Q7.
What mobile-eggbert's Format Looks Like (reference only)
mobile-eggbert's save data (GameData.cpp) is a flat binary layout covering per-slot
lives, last-world-reached, and door-open flags across 3 gamer slots. It is listed in
CLAUDE.md's reuse table as reference only — reusing its exact byte
layout for save compatibility requires explicit user approval, it is not assumed.
Roadmap
Per plan.md's E3D-MIG-100…107 gameplay-porting tasks, save/load is sequenced after
core gameplay (pickups, hazards, enemy stomp, exit gate) is ported — with an explicit decision
point on save-format reuse before implementation begins.