FLYGAME / PLAYER & ENGINEERING REFERENCE

Combat & Controls — The Six-Button Field Guide

FLYGAME WIKI / PLAYER MECHANICS · Source inspection November 15, 2026 · SOURCE-IMPLEMENTED; full current-ROM gameplay UNVERIFIED

One small controller, several kinds of action

FlyGame is designed around the original Game Boy's D-pad, A, B, Start and Select buttons. The challenge is making travel, interaction, combat and learned skills share that modest input surface without forcing every action into the same button.

InputSource-defined behavior
D-padMove the character and establish facing.
AContextual interaction for authored NPC, chest, sign, switch and trigger events; exact availability depends on the loaded scene.
B (tap)Basic melee attack in the direction the character is facing, subject to attack recovery.
Double-tap directionInnate dodge/lunge with a short invulnerability window, as described by the combat slice and runtime bank.
Hold Select + press directionSelect one of four assigned skill slots and attempt to cast.
Select + BCycle the authored player actor.
StartToggle the start/pause menu.

A subtle but important facing rule

In the currently inspected flygame_play_bank.c, Select + direction chooses a skill slot. It does not turn the player toward that direction. The cast uses the character's current facing established by movement beforehand. That detail is more precise than older playtest plans that described a skill as being aimed by the slot-direction press.

Move to face a threat first; then hold Select and press the slot direction to cast the skill equipped there.

This is a source-based control explanation, not proof that each input performs correctly on the newest cartridge build.

Basic attack and contact

A B tap invokes the banked basic attack routine. The source constructs a forward-reach hitbox and applies recovery rather than letting continuous held B produce unlimited swings. The enemy collision model compares combat rectangles—not simply visible sprite silhouettes. A character can appear close to an enemy while the engine's active collision anchors tell a slightly different story.

The July 28 Combat Runtime Truth Map documented several historical playtest lessons: moving and facing matter; a scripted attack that lands beside a sprite can still miss the actual hit rectangle; enemy contact uses a separate hurtbox. These observations explain engine behavior but should not be mistaken for live validation of every encounter in the current November candidate.

Skills, actors and effects

The player-skill test roster includes two authored player identities—PLAYER_CHAR_BOY and PLAYER_CHAR_GIRL—and four representative VFX/behavior skills: Arc Slash, Ring Pulse, Needle Bolt and Starburst. Later catalog design describes sixteen named skills sharing four common combat-animation and hitbox archetypes. Casts are gated by resources, cooldown and recovery, so selecting a slot does not guarantee a successful cast.

How a hit is calculated

The player’s resolved primary attributes feed a compact combat profile, with physical, arcane or spirit power, accuracy, evasion, penetration, critical/tempo and action-scoped elemental tags. Enemy type, power band, guard and position influence a hit. This system is intentionally table-assisted so expensive scaling is prepared by tooling rather than recalculated every time a Game Boy sprite moves.

Evidence and next checks

Current evidence: source-level controls and combat paths exist; older tests caught real input/facing/geometry behavior. Not accepted: an end-to-end playthrough of ordinary exploration, repeated enemy exchanges, a dungeon reward and Save/Continue in one source-matched November ROM.

Sources read: src/banked/flygame_play_bank.c lines 855–900 and 964–984; docs/COMBAT_SLICE_V1.md; docs/COMBAT_RUNTIME_TRUTH_MAP.md; docs/PLAYER_SKILL_PLAYTEST_PLAN.md; docs/COMBAT_INTERACTION_MODEL.md.


Equipment & Shops · Saving & Continuing · Playable Slice Tracker · FAQ