MEGA MAN X ENGINE PROJECT
David Luky ↗PT
ProjectEnemies

CHOOSE AN ENTRY. HELP CLOSE A GAP.

Enemy catalog.

See the art, what already works, and what is missing. Open an entry, check its checklist, and find a concrete contribution.

16 of 16 entries in this selection

Verified partPartial / to validateNeeds measurement or integration

The ✓ applies to the described step. Every entry in this scope still has pending work; no character is marked as fully complete. First time here? Start with the guide →

Enemy · 0x0B

Axe Max

The log thrower

✓ Has verified steps

The body, axe, and contact with the stack have received fixes. The behavior still needs to be checked in every appearance.

  • Art: Verified part
  • Movement: Partial / to validate
  • Attacks: Partial / to validate
  • Collision: Verified part
  • Reference: Partial / to validate
  • Tests: Verified part
NEXT TASK

Check activation, disappearance, and return at Sting Chameleon's three current positions.

Checklist, tasks, and how to help

Checklist by area

  • Art · Verified part

    Body and axe composition aligned with the reference, with pose and ground-support tests.

  • Movement · Partial / to validate

    Stationary base and alert state measured; reactivation in Sting Chameleon's appearances still needs validation.

  • Attacks · Partial / to validate

    The launch of two logs and the release frame have been measured. Restocking the logs and the complete cycle still need review.

  • Collision · Verified part

    The stack is solid from above, from the sides, and from below in the test scene; this does not settle all enemy collision.

  • Reference · Partial / to validate

    Visual composition compared with the original. Contact and cycle limits still need documentation.

  • Tests · Verified part

    Body/axe, support, hit effect, and collision contracts cover the described fixes.

Where to find it

Chill Penguin · Sting Chameleon

Needed contributions

  • Programming — Check activation, disappearance, and return at Sting Chameleon's three current positions.
  • Research — Record how the logs are replenished and which object controls each one after launch.
  • Tests — Test the stack from all three sides, shoot from both sides, and leave/return to the screen.

How to verify the deliverable

Show the same appearance before and after leaving the screen, without duplicating logs or losing the stack state.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: axemax private materialsReferences and measurements private materialsRelated verification private materialsSupplementary verification private materialsGround support private materialsHit visual effect private materialsStack collision in the engine private materialsenemy.cpp ↗axemax_stack_collision.h ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Enemy · 0x27

Strider

The long-legged enemy

✓ Has verified steps

The per-step displacement has been measured. The animation still uses an incomplete sequence: two original frames are missing.

  • Art: Needs measurement or integration
  • Movement: Verified part
  • Attacks: Needs measurement or integration
  • Collision: Partial / to validate
  • Reference: Partial / to validate
  • Tests: Verified part
NEXT TASK

Capture the full character during one cycle and recover cells 0x06 and 0x07.

Checklist, tasks, and how to help

Checklist by area

  • Art · Needs measurement or integration

    Cells 0x06 and 0x07 are missing; they were cropped out of the available captures.

  • Movement · Verified part

    Steps and the duration of 12 frames per step compared by trajectory test.

  • Attacks · Needs measurement or integration

    No attack was observed in this entry's material; the repertoire needs confirmation.

  • Collision · Partial / to validate

    The drawn shape was measured; contact damage and physical limits are still provisional.

  • Reference · Partial / to validate

    There is a reference sequence, but two poses fell outside the image.

  • Tests · Verified part

    The trajectory test covers displacement; it does not prove the missing animation.

Where to find it

Intro Highway · Sigma 1 · Spark Mandrill · Storm Eagle

Needed contributions

  • Sprites — Capture the full character during one cycle and recover cells 0x06 and 0x07.
  • Programming — Integrate the recovered poses while preserving the movement's eight steps.
  • Tests — Compare the complete walk: six available poses must not shorten an eight-step cycle.

How to verify the deliverable

Deliver the two poses with palette, alignment, and frame number, plus a comparison of a complete cycle.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: se_strider private materialsReferences and measurements private materialsRelated verification private materialsSupplementary verification private materialsenemy.cpp ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Enemy · 0x49

Drone rotor

Air patrol

✓ Has verified steps

The horizontal patrol and its integration have dedicated tests. Contact and pose-change observations are still missing.

  • Art: Partial / to validate
  • Movement: Verified part
  • Attacks: Needs measurement or integration
  • Collision: Partial / to validate
  • Reference: Partial / to validate
  • Tests: Verified part
NEXT TASK

Repeat X's approach to identify when the drone opens its arms.

Checklist, tasks, and how to help

Checklist by area

  • Art · Partial / to validate

    Twelve original cells are available; the visual reference identification still needs to be finalized.

  • Movement · Verified part

    Horizontal patrol at 1.5 pixels per frame, with movement and integration contracts.

  • Attacks · Needs measurement or integration

    No attack was observed. What starts the two open-arm sequences still needs to be explained.

  • Collision · Partial / to validate

    A stop on the terrain appeared in one case; contact damage remains provisional.

  • Reference · Partial / to validate

    Poses and positions have been measured in captures; some transitions still need repetition.

  • Tests · Verified part

    Dedicated tests cover movement, integration, content, and engine rendering.

Where to find it

Flame Mammoth · Launch Octopus · Storm Eagle

Needed contributions

  • Research — Repeat X's approach to identify when the drone opens its arms.
  • Programming — Compare the stop on touching the terrain at more than one position.
  • Tests — Check contact without inferring damage from a video in which X was not hit.

How to verify the deliverable

Deliver two reproducible examples of the transition, with X's and the drone's positions and the first frame of the change.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: se_drone private materialsReferences and measurements private materialsRelated verification private materialsSupplementary verification private materialsDrone content private materialsEngine rendering private materialsenemy.cpp ↗gameplay_enemy_contact.h ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Boss · 0x0C

Flame Mammoth

Trunk and head receive X's shots

✓ Has verified steps

The Buster hitbox and the damage palette have been corrected. The complete fight still depends on attacks and transitions compared with the original.

  • Art: Verified part
  • Movement: Partial / to validate
  • Attacks: Needs measurement or integration
  • Collision: Verified part
  • Reference: Partial / to validate
  • Tests: Verified part
NEXT TASK

Record every attack and link the boss pose to the object it actually creates.

Checklist, tasks, and how to help

Checklist by area

  • Art · Verified part

    The normal and damage atlases have orientation and palette compared with the original; this does not settle the timing of each animation.

  • Movement · Partial / to validate

    The boss uses the engine's generic flow. The fight's specific rules have not yet been authenticated.

  • Attacks · Needs measurement or integration

    The attack list is declarative. Triggers, transitions, and the identity of attack objects still need measurement.

  • Collision · Verified part

    X's shots reach the trunk and head with the 38 × 58 hitbox. X's collision with the body is a separate question.

  • Reference · Partial / to validate

    Captures and hit, body, and palette data exist. Each attack and its objects still need to be explained.

  • Tests · Verified part

    Atlas and shot-hitbox contracts cover the fixes; they do not prove parity for the complete fight.

Where to find it

Flame Mammoth · boss fight

Needed contributions

  • Research — Record every attack and link the boss pose to the object it actually creates.
  • Programming — Specialize the attacks after confirming triggers, trajectory, and transitions.
  • Tests — Check shots to the head and middle of the body from both sides; test body contact separately.
  • Sprites — Measure the damage-flash timing without changing the pixels and palette already compared.
  • Audio — Link each effect to the start of the corresponding attack or impact.

How to verify the deliverable

Deliver one complete attack with state, pose, identified projectile, and sound events. Preserve the already verified hits on the upper body.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Buster hitbox and reference private materialsDamage palette private materialsFight definition and limits private materialsShot hitbox verification private materialsAtlas verification private materialsboss.cpp ↗gameplay_scene_boss.cpp ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Enemy · 0x51

Walker

Chases, stops, and shoots

↻ In development

The alternation between walking and stopping has been measured. The distance that enables firing and the bullet's vertical path still need precision.

  • Art: Partial / to validate
  • Movement: Partial / to validate
  • Attacks: Partial / to validate
  • Collision: Partial / to validate
  • Reference: Partial / to validate
  • Tests: Partial / to validate
NEXT TASK

Measure X's distance on the first frame of each shot and record the bullet's height.

Checklist, tasks, and how to help

Checklist by area

  • Art · Partial / to validate

    Sheet and identity are available. The order of some walking poses still needs comparison.

  • Movement · Partial / to validate

    Measurements show 1.5 pixels per frame, 55 frames stopped, and 30 walking; the state variation still needs explanation.

  • Attacks · Partial / to validate

    Stationary firing and a speed of 2.25 pixels per frame have been measured; range and vertical deviation remain open.

  • Collision · Partial / to validate

    Contact damage measured; the hitbox uses the art's extent as an approximation.

  • Reference · Partial / to validate

    Identity linked to the stage captures, without a separate canonical visual reference.

  • Tests · Partial / to validate

    Stage-start and activation contracts cover shared parts, not the complete attack.

Where to find it

Chill Penguin

Needed contributions

  • Research — Measure X's distance on the first frame of each shot and record the bullet's height.
  • Programming — Resolve the range condition and the stopped-state variation from these measurements.
  • Sprites — Compare the pose order in both directions.

How to verify the deliverable

Reproduce two approach-and-shoot cycles with distance, duration, and trajectory identified.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: walker private materialsReferences and measurements private materialsRelated verification private materialsSupplementary verification private materialsenemy.cpp ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Enemy · 0x54

Snowball

Rolling and growth

✓ Has verified steps

The movement already has its own contract. What triggers growth still needs to be discovered, and collision for the larger form still needs to be applied.

  • Art: Partial / to validate
  • Movement: Verified part
  • Attacks: Needs measurement or integration
  • Collision: Needs measurement or integration
  • Reference: Partial / to validate
  • Tests: Verified part
NEXT TASK

Capture growth on another terrain profile to distinguish time, distance, and slope.

Checklist, tasks, and how to help

Checklist by area

  • Art · Partial / to validate

    Six cells and the larger appearance are available; visual identification is not yet complete.

  • Movement · Verified part

    Measured air and ground speed rules are covered by the movement contract.

  • Attacks · Needs measurement or integration

    No shot was observed; the size change still needs to be explained.

  • Collision · Needs measurement or integration

    The small hitbox exists. Collision for the grown 32 × 32 form is not yet integrated.

  • Reference · Partial / to validate

    The previous identification was reviewed; do not confuse it with the generic object called snowball.

  • Tests · Verified part

    The dedicated contract covers the accepted movement without settling growth.

Where to find it

Chill Penguin

Needed contributions

  • Research — Capture growth on another terrain profile to distinguish time, distance, and slope.
  • Programming — Integrate the larger collision after confirming the growth trigger.
  • Tests — Repeat contact before and after growth, from both sides.

How to verify the deliverable

Present two cycles on different terrain and a test that changes collision at the same moment as the visual form.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: cp_snowball private materialsReferences and measurements private materialsRelated verification private materialsSupplementary verification private materialsenemy.cpp ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Enemy · 0x04

Stretch Bird

Attack integrated; complete fidelity still open

↻ In development

The attack now uses behavior measured in the original game. Completion applies to the tested scope; audio, body contact and complete parity must be checked separately.

  • Art: Partial / to validate
  • Movement: Partial / to validate
  • Attacks: Partial / to validate
  • Collision: Partial / to validate
  • Reference: Partial / to validate
  • Tests: Partial / to validate
NEXT TASK

Compare uncovered situations, citing the capture and exact timestamp.

Checklist, tasks, and how to help

Checklist by area

  • Art · Partial / to validate

    Attack poses were compared against reference pixels.

  • Movement · Partial / to validate

    Base behavior and attack cycle integrated within the observed scope.

  • Attacks · Partial / to validate

    Launch, cadence and projectile integrated and tested; this does not close every gameplay situation.

  • Collision · Partial / to validate

    Attack contact has dedicated checks. Complete body and interaction parity remains open.

  • Reference · Partial / to validate

    Controlled captures and frame-by-frame states support the integration; the full campaign still needs comparison.

  • Tests · Partial / to validate

    Controller and in-game contracts pass; tests do not replace full-campaign acceptance.

Where to find it

Armored Armadillo · Chill Penguin · Sigma 2 · Spark Mandrill

Needed contributions

  • Research — Compare uncovered situations, citing the capture and exact timestamp.
  • Tests — Reproduce differences in audio, body contact or projectile interactions.

How to verify the deliverable

A reproducible difference with clear steps and limits, without rebuilding the already integrated attack.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: stretch_bird private materialsReferences and measurements private materialsRelated verification private materialsSupplementary verification private materialsenemy.cpp ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Enemy · 0x53

Mad Pecker

Attack integrated; complete fidelity still open

↻ In development

The attack now uses behavior measured in the original game. Completion applies to the tested scope; audio, body contact and complete parity must be checked separately.

  • Art: Partial / to validate
  • Movement: Partial / to validate
  • Attacks: Partial / to validate
  • Collision: Partial / to validate
  • Reference: Partial / to validate
  • Tests: Partial / to validate
NEXT TASK

Compare uncovered situations, citing the capture and exact timestamp.

Checklist, tasks, and how to help

Checklist by area

  • Art · Partial / to validate

    Attack poses were compared against reference pixels.

  • Movement · Partial / to validate

    Base behavior and attack cycle integrated within the observed scope.

  • Attacks · Partial / to validate

    Launch, cadence and projectile integrated and tested; this does not close every gameplay situation.

  • Collision · Partial / to validate

    Attack contact has dedicated checks. Complete body and interaction parity remains open.

  • Reference · Partial / to validate

    Controlled captures and frame-by-frame states support the integration; the full campaign still needs comparison.

  • Tests · Partial / to validate

    Controller and in-game contracts pass; tests do not replace full-campaign acceptance.

Where to find it

Chill Penguin

Needed contributions

  • Research — Compare uncovered situations, citing the capture and exact timestamp.
  • Tests — Reproduce differences in audio, body contact or projectile interactions.

How to verify the deliverable

A reproducible difference with clear steps and limits, without rebuilding the already integrated attack.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: mad_pecker private materialsReferences and measurements private materialsRelated verification private materialsSupplementary verification private materialsMad Pecker art and content private materialsenemy.cpp ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Enemy · 0x2E

Met from Storm Eagle

Hides and opens its helmet

↻ In development

Seven poses are available. The shot when opening the helmet is not yet integrated, and one moving appearance remains unexplained.

  • Art: Partial / to validate
  • Movement: Needs measurement or integration
  • Attacks: Needs measurement or integration
  • Collision: Partial / to validate
  • Reference: Partial / to validate
  • Tests: Partial / to validate
NEXT TASK

Record several waits with the helmet closed, varying X's distance.

Checklist, tasks, and how to help

Checklist by area

  • Art · Partial / to validate

    Seven cells recovered and sheet available in the engine.

  • Movement · Needs measurement or integration

    Four appearances stayed still; the fifth moved. This difference needs to be explained.

  • Attacks · Needs measurement or integration

    The attack on opening was observed, but the opening condition remains unknown and is not integrated.

  • Collision · Partial / to validate

    Hitbox and contact damage are provisional.

  • Reference · Partial / to validate

    Poses and appearance records exist; several waits with X at different distances still need measurement.

  • Tests · Partial / to validate

    The current tests verify content and distribution without settling the behavior.

Where to find it

Armored Armadillo · Sigma 1 · Storm Eagle

Needed contributions

  • Research — Record several waits with the helmet closed, varying X's distance.
  • Programming — Integrate the attack after settling the opening condition and moving state.
  • Tests — Check how shots interact with the open and closed helmet.

How to verify the deliverable

Explain the opening at more than one distance and reproduce the case in which the enemy walks.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: se_met private materialsReferences and measurements private materialsRelated verification private materialsSupplementary verification private materialsenemy.cpp ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Enemy · 0x29

Blue Highway robot

One entry for its appearances and research

↻ In development

Two body poses and the Highway shot already have references. The former “Corridor mech” entry is collected here to compare the material and avoid duplicate work.

  • Art: Partial / to validate
  • Movement: Partial / to validate
  • Attacks: Partial / to validate
  • Collision: Needs measurement or integration
  • Reference: Needs measurement or integration
  • Tests: Partial / to validate
NEXT TASK

Trace the tiles of records 0x29 and 0x41 in the Storm Eagle captures and prove their relationship.

Checklist, tasks, and how to help

Collected research

The original capture shows a single robot, and the old corridor thumbnail is its lower-body crop. Both internal records reuse parts of the same image. Which record generates each part still needs proof; measurements therefore keep their source, and we have not changed HP, attacks or collision in the game.

Technical records and limits

Highway robot · primary record

intro_robot · 0x29

Two 44 × 62 px poses. Body and projectile have original-game references. The Highway test covers shot emission; this does not complete the enemy’s fidelity.

Current definition: Turret, HP 16. Integrated shot at 4 px/frame, damage 2 and three visual frames of 16 × 16 px. Body collision remains provisional.

Intro Highway · Sigma 1 · Spark Mandrill · Storm Eagle

Former “Corridor mech” · identity pending

se_mech · 0x41

One 42 × 43 px cell associated with record 0x41. Review of the original image and tiles confirms a lower-body crop of the robot. Extraction used proximity, which does not yet prove which object generated these pixels.

Current definition: Anchored. HP 2 in the predominant samples; one sample has HP 6. Attack unobserved, contact damage provisional. These values are not transferred to the Highway robot.

Storm Eagle

Checklist by area

  • Art · Partial / to validate

    OID 0x29: two body poses and three projectile frames recovered. The old corridor thumbnail is a smaller crop, associated with record 0x41 whose identity is still under investigation.

  • Movement · Partial / to validate

    Samples of both records remained stationary. The engine still uses separate definitions while their relationship is investigated.

  • Attacks · Partial / to validate

    The OID 0x29 shot has recovered art and engine integration, with an automated contract. No attack has been confirmed for record 0x41.

  • Collision · Needs measurement or integration

    Hitboxes and contact need their own validation. Values from record 0x41 cannot replace those of 0x29 without proving their relationship.

  • Reference · Needs measurement or integration

    Material from both entries is collected here. The priority is to identify which object owns the tiles of the 0x41 crop in the existing captures.

  • Tests · Partial / to validate

    The Highway contract checks the shot and its presentation. Corridor content tests do not prove identity or equivalent behavior.

Where to find it

Intro Highway · Sigma 1 · Spark Mandrill · Storm Eagle

Needed contributions

  • Research — Trace the tiles of records 0x29 and 0x41 in the Storm Eagle captures and prove their relationship.
  • Sprites — Check the corridor crop and recover only frames attributed to the correct object.
  • Programming — Reuse the definition and attack only if equivalence between the records is proven.
  • Tests — Compare firing, direction and contact in the stages where the robot appears, with X on both sides.

How to verify the deliverable

Associate each image and measurement with the correct object. If the records are equivalent, demonstrate the same combat rule before unifying the engine; if they are not, explain the difference within this entry.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: intro_robot private materialsReferences and measurements private materialsRelated verification private materialsReference for the three shot frames private materialsRecord 0x41: identity under investigation private materialsFormer mech content contract private materialsStage appearance checks private materialsenemy.cpp ↗intro_robot_scheduler.h ↗intro_robot_scheduler.cpp ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Enemy · 0x15

Spiked sphere

Leftward movement

↻ In development

The art and movement were recovered. Rotation timing, the contact hitbox, and positions in the other stages still need review.

  • Art: Partial / to validate
  • Movement: Partial / to validate
  • Attacks: Needs measurement or integration
  • Collision: Needs measurement or integration
  • Reference: Partial / to validate
  • Tests: Partial / to validate
NEXT TASK

Measure how long each rotation pose remains visible.

Checklist, tasks, and how to help

Checklist by area

  • Art · Partial / to validate

    Two-frame sheet recovered; rotation timing is still provisional.

  • Movement · Partial / to validate

    Leftward movement of 1.5 pixels per frame at constant height was measured.

  • Attacks · Needs measurement or integration

    No separate attack was observed. Behavior when destroyed still needs to be recorded.

  • Collision · Needs measurement or integration

    The contact hitbox was not captured in the original.

  • Reference · Partial / to validate

    Reference pixels and positions exist, but comparison between stages remains open.

  • Tests · Partial / to validate

    Definition and positioning contracts cover part of the data.

Where to find it

Armored Armadillo · Chill Penguin · Intro Highway · Sigma 1 · Sigma 2

Needed contributions

  • Sprites — Measure how long each rotation pose remains visible.
  • Research — Capture contact and destruction to measure the hitbox and what happens afterward.
  • Tests — Check each position in the listed stages before considering distribution complete.

How to verify the deliverable

Deliver a rotation cycle with timings and a reproducible contact, without using image size as proof of the hitbox.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: intro_spikeball private materialsReferences and measurements private materialsRelated verification private materialsSupplementary verification private materialsenemy.cpp ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Enemy · 0x2D

Chill Penguin bat

Waits, releases, and flies

✓ Has verified steps

The wait and distribution of flight directions have their own test. Visual identification and contact still need more examples.

  • Art: Partial / to validate
  • Movement: Verified part
  • Attacks: Needs measurement or integration
  • Collision: Partial / to validate
  • Reference: Needs measurement or integration
  • Tests: Verified part
NEXT TASK

Obtain a second controlled contact and an image that identifies the pose unambiguously.

Checklist, tasks, and how to help

Checklist by area

  • Art · Partial / to validate

    Visual family and sheet are available, but the canonical reference has not yet been confirmed.

  • Movement · Verified part

    A wait of 30–35 frames and flight at 1 pixel per frame, with trajectory and distribution tests.

  • Attacks · Needs measurement or integration

    No shot was observed in the available material.

  • Collision · Partial / to validate

    There is one damage-1 observation; it is not enough to settle the hitbox and contact.

  • Reference · Needs measurement or integration

    Family resemblance is not enough to conclude the identification of each pose.

  • Tests · Verified part

    The dedicated contract checks the flight law and its direction distribution.

Where to find it

Armored Armadillo · Chill Penguin · Sigma 2 · Sigma 3

Needed contributions

  • Research — Obtain a second controlled contact and an image that identifies the pose unambiguously.
  • Sprites — Check the waiting and release poses against the identified reference.
  • Tests — Validate the appearances in the four stages without replacing this ID with a generic bat.

How to verify the deliverable

Associate pose, identity, and contact in the same capture and preserve the already verified flight distribution.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: cp_bat private materialsReferences and measurements private materialsRelated verification private materialsSupplementary verification private materialsenemy.cpp ↗enemy_bat_drift_law.h ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Enemy · 0x19

Mine-dropping bat

Patrol at fixed height

↻ In development

The patrol, two mine releases, and damage have been measured. Visual matching and contact geometry still need to be settled.

  • Art: Partial / to validate
  • Movement: Partial / to validate
  • Attacks: Partial / to validate
  • Collision: Partial / to validate
  • Reference: Needs measurement or integration
  • Tests: Partial / to validate
NEXT TASK

Link each sheet pose to an identified capture of the original.

Checklist, tasks, and how to help

Checklist by area

  • Art · Partial / to validate

    Sheet available; identity linked to campaign captures, without a final visual reference.

  • Movement · Partial / to validate

    A patrol at 1.25 pixels per frame and a wait at fixed height were measured.

  • Attacks · Partial / to validate

    Two releases, trajectory, and mine persistence were measured; the cycle needs review as a whole.

  • Collision · Partial / to validate

    Body damage 2 and mine damage 1 observed; contact geometry is still approximate.

  • Reference · Needs measurement or integration

    Comparison of the sheet and visual identity in the highway appearances still needs to be finalized.

  • Tests · Partial / to validate

    Shared damage contracts cover contact; this entry has no dedicated flight comparison.

Where to find it

Chill Penguin · Intro Highway

Needed contributions

  • Sprites — Link each sheet pose to an identified capture of the original.
  • Research — Check the highway appearances and separate the body from the mines in the records.
  • Audio — Identify the release or impact effect and record its moment; do not infer sound from movement.

How to verify the deliverable

A short sequence should identify the body, mine, and sound event separately, with the source of each reference.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: bat private materialsReferences and measurements private materialsRelated verification private materialsSupplementary verification private materialsenemy.cpp ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Enemy · 0x50

Armored turret

Attack integrated; complete fidelity still open

↻ In development

The attack now uses behavior measured in the original game. Completion applies to the tested scope; audio, body contact and complete parity must be checked separately.

  • Art: Partial / to validate
  • Movement: Partial / to validate
  • Attacks: Partial / to validate
  • Collision: Partial / to validate
  • Reference: Partial / to validate
  • Tests: Partial / to validate
NEXT TASK

Compare uncovered situations, citing the capture and exact timestamp.

Checklist, tasks, and how to help

Checklist by area

  • Art · Partial / to validate

    Attack poses were compared against reference pixels.

  • Movement · Partial / to validate

    Base behavior and attack cycle integrated within the observed scope.

  • Attacks · Partial / to validate

    Launch, cadence and projectile integrated and tested; this does not close every gameplay situation.

  • Collision · Partial / to validate

    Attack contact has dedicated checks. Complete body and interaction parity remains open.

  • Reference · Partial / to validate

    Controlled captures and frame-by-frame states support the integration; the full campaign still needs comparison.

  • Tests · Partial / to validate

    Controller and in-game contracts pass; tests do not replace full-campaign acceptance.

Where to find it

Storm Eagle

Needed contributions

  • Research — Compare uncovered situations, citing the capture and exact timestamp.
  • Tests — Reproduce differences in audio, body contact or projectile interactions.

How to verify the deliverable

A reproducible difference with clear steps and limits, without rebuilding the already integrated attack.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: se_turret private materialsReferences and measurements private materialsRelated verification private materialsenemy.cpp ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Created by the boss · 0x56

Storm Eagle chick

Spawns during the boss fight

↻ In development

The release of four chicks and their initial speeds have been measured. The pursuit after release is not yet integrated.

  • Art: Partial / to validate
  • Movement: Partial / to validate
  • Attacks: Needs measurement or integration
  • Collision: Needs measurement or integration
  • Reference: Partial / to validate
  • Tests: Partial / to validate
NEXT TASK

Capture a chick that completes the dive and reaches X.

Checklist, tasks, and how to help

Checklist by area

  • Art · Partial / to validate

    Egg-release cells and sheet available.

  • Movement · Partial / to validate

    Four diagonal releases and their initial speeds have been measured.

  • Attacks · Needs measurement or integration

    The subsequent dive toward X is documented but not integrated.

  • Collision · Needs measurement or integration

    HP, hitbox, and contact are provisional because the capture did not show a hit on X.

  • Reference · Partial / to validate

    The reference belongs to the boss attack; it is not a fixed map appearance.

  • Tests · Partial / to validate

    The egg-attack contract covers chick generation, not the complete dive.

Where to find it

Storm Eagle · boss fight

Needed contributions

  • Research — Capture a chick that completes the dive and reaches X.
  • Programming — Integrate the pursuit after the diagonal release, using the measured target and duration.
  • Tests — Check the creation, contact, and disappearance of every chick in the fight.

How to verify the deliverable

Demonstrate the transition from diagonal release to dive and one real contact, without adding chicks to the stage's fixed population.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: se_eaglet private materialsReferences and measurements private materialsRelated verification private materialsenemy.cpp ↗boss_se_egg_drop.h ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides

Enemy · 0x0F

Highway object 0x0F

Identity under investigation

? Identity to confirm

The current content calls it a helicopter; another reference points to a crusher. The thumbnail shows the current file, with this uncertainty made explicit.

  • Art: Needs measurement or integration
  • Movement: Needs measurement or integration
  • Attacks: Needs measurement or integration
  • Collision: Needs measurement or integration
  • Reference: Needs measurement or integration
  • Tests: Partial / to validate
NEXT TASK

Link ID 0x0F to its image and sprite data in a single capture of the original.

Checklist, tasks, and how to help

Checklist by area

  • Art · Needs measurement or integration

    An image exists in the project, but its visual identity is disputed. Provisional thumbnail.

  • Movement · Needs measurement or integration

    The current hovering is an approximation and does not prove the original behavior.

  • Attacks · Needs measurement or integration

    The bomb branch that destroys terrain is not yet implemented.

  • Collision · Needs measurement or integration

    Health, contact, and geometry are provisional until the identity is resolved.

  • Reference · Needs measurement or integration

    ID 0x0F, the on-screen image, and the recorded object must be linked in the same capture.

  • Tests · Partial / to validate

    The highway contract does not resolve this identity conflict.

Where to find it

Intro Highway

Needed contributions

  • Research — Link ID 0x0F to its image and sprite data in a single capture of the original.
  • Sprites — Confirm the silhouette before renaming or replacing the sheet.
  • Programming — After identification, measure the bomb and terrain change before integrating the attack.

How to verify the deliverable

A reproducible reference should explain which object is 0x0F, how it attacks, and which art represents that state.

Files and evidence

Code links open public files. References that are not distributed are marked as private materials.

Definition: intro_helicopter private materialsReferences and measurements private materialsRelated verification private materialsenemy.cpp ↗destructible_terrain.h ↗
I want to help with this entry ↗

Browse AI tasks →

Direct link to this entry · View all guides