FLYGAME / PLAYER & ENGINEERING REFERENCE

FlyGame Wiki — Game & Systems

FLYGAME WIKI / CANONICAL EDITORIAL INDEX · Last reviewed November 15, 2026

This page replaces the imported September 2026 standalone reference with a smaller, source-graded index. It preserves its game topics without implying that every implementation has passed ordinary-play validation. Sections will expand into full articles as current source and emulator evidence support them.

Start here

Game mechanics

World streaming and movement

SOURCE-IMPLEMENTED. The tools and generated data use 16×16 tile chunks for streamed regions. A directional collision routine candidate cleared a private fixed-ROM layout check, but current-source player movement still needs live verification. See Engineering Bench.

Characters, progression, combat

SOURCE-IMPLEMENTED / HISTORICAL LIVE TESTS. Banked skill and combat progression systems, actor definitions and tests exist in the project. An earlier ROM had Mesen-backed actor and skill observations; these do not automatically certify today's candidate ROM or the entire RPG journey.

Inventory, equipment and chests

SOURCE-IMPLEMENTED / PARTIALLY VERIFIED. Item, equipment and chest runtime components exist. The caller-memory chest result-channel fix has static regression coverage. A separate F-024 stack concern and full chest Save/Continue validation remain unresolved.

Quests, NPCs and world props

SOURCE-IMPLEMENTED. Project tooling and runtime scaffolding support NPC identities, interaction routes, props, triggers, signs and flags. Authored/catalog presence alone does not guarantee a particular quest or NPC occurs in the verified playable slice.

Weather and the Tideheart

SOURCE-IMPLEMENTED / PLAYTEST NEEDED. Weather and Tideheart-related logic have documented source and static validation. The planned ordinary sequence from receiving the Tideheart through saving, continuing and weather use remains to be observed in a properly isolated ROM session.


World & progression

  • Plains / Waypost: an early quest and traversal area in the game's authored content; route not yet accepted end to end.
  • Great Temple: floors 1, 2 and 3 are first-slice progression checkpoints; walkthrough sequencing awaits proof.
  • Tideheart: a central named milestone in the first-slice plan, including weather interaction tests.

The world guide explains these places without inventing dialogue, maps, item stats or enemy placement.

The developer's bench

  • GBDK 2020 / banked ROM: code and data must respect fixed-ROM and switchable-bank constraints.
  • Working RAM and call depth: small object-frame savings are not proof of whole-game stack safety.
  • World authoring: editors, generated background tiles, sprites and site assets feed the build.
  • 3D camera experiments: separate tooling demos remain TOOLING-DEMONSTRATED until a production ROM integrates and verifies them.

See Engineering Bench for readable technical stories.

Reading and evidence standards

  • PLAYTESTED: source-matched ROM, identified emulator state, ordinary player controls and relevant saved-game isolation.
  • SOURCE-IMPLEMENTED: code or authored content present, runtime outcome not fully established.
  • TOOLING-DEMONSTRATED: an editor or lab demo, not necessarily a cartridge feature.
  • PLANNED: a target or design; not a release promise.
  • HISTORICAL: valid for an earlier dated snapshot, may have changed.

For the latest development story use Development Journal. For the complete story and source policy see About FlyGame.


Historical preservation note: The original FlyGame DMG Project Site v2 package (September 17, 2026) remains in the owner's supplied backup. This page supersedes it as the maintained editorial wiki; no original game files were edited.

Explore the detailed guides

Our first expanded articles turn the source catalog into a growing player reference. Each page carries its own evidence grade and review date.

New: playable systems & source-backed field guides

Go deeper into controls, the people of Waypost, regional roads, equipment and weather. Each chapter distinguishes authored content from a verified current-ROM walkthrough.