MEGA MAN X ENGINE PROJECT
David Luky ↗PT

YOUR AI. A REAL TASK.

Contributing just got easier.

Choose a small improvement. Give your AI the context. Submit something we can review together.

01 · Download the kit02 · Choose a task03 · Paste the prompt

Any area: code, documentation, translation or testing. The draw prepares a concrete request and shows the required material. Use your own AI; this site needs no API key.

Build your first request.

Extract the ZIP into its own folder and open that folder in Codex. Paste the prompt below.

Make the Axe Max entry clearer

Find up to three hard-to-understand sentences. Propose clearer wording while preserving verified facts and open work.

Text review. It does not verify new behavior, collisions or original-game fidelity.

Your prompt is ready
Help me contribute to Mega Man X. Task: docs-axe-max — Make the Axe Max entry clearer. Kit: 2026-09-10.4.

Read INSTRUCTIONS.md, tasks.json and the inputs listed for this task (or the equivalent sections of AI-CONTEXT.en.md). Use only the public kit and the listed public inputs.

Objective: Find up to three hard-to-understand sentences. Propose clearer wording while preserving verified facts and open work.
Acceptance: For each suggestion: current wording, replacement and reason. Cite the entry field. A verified step must not become a completed enemy.
Limits: Text review. It does not verify new behavior, collisions or original-game fidelity.

Work on this task now. Cite the exact fields, paths or timestamps you used. Do not invent findings or test results. Save output/report.json using templates/report.json; add report.md if helpful. Run tools/check_submission.py --report output/report.json only if you can execute Python locally; otherwise mark it not_run and return the report text. A structural PASS is not proof of gameplay correctness. Return the reviewed report or a small scoped patch for human review; do not send, push or publish automatically.

Read the response before submitting. The kit organizes the work; AI can still make mistakes.

SMALL STARTS, USEFUL CONTRIBUTIONS

What you can work on.

Three tasks work with the kit alone. One uses public video. Four use the public GitHub source.

Included public materialMake the Axe Max entry clearer

Find up to three hard-to-understand sentences. Propose clearer wording while preserving verified facts and open work.

Acceptance

For each suggestion: current wording, replacement and reason. Cite the entry field. A verified step must not become a completed enemy.

Text review. It does not verify new behavior, collisions or original-game fidelity.

Required inputs

  • context/enemies.pt-BR.json
  • context/enemies.en.json
Included public materialReview the Chill Penguin bat translation

Compare the PT and EN cp_bat entry. Check clarity, terminology, units and completion limits.

Acceptance

Submit a table with PT text, current EN, proposed EN and rationale. Preserve values and units; distinguish OIDs from provisional names.

A better translation does not prove art, attacks or contact. If wording is already correct, report that with examples.

Required inputs

  • context/enemies.pt-BR.json
  • context/enemies.en.json
Included public materialCheck catalogue consistency

Compare Axe Max, CP bat and Rotor drone in the included material. Check that summaries, six facets and next tasks agree.

Acceptance

List each entry, field and verifiable observation. Separate real contradictions from unclear terms. A report finding no defects is valid.

The catalogue is partial. Do not infer spawn counts, identity or collision from a thumbnail.

Required inputs

  • context/enemies.pt-BR.json
  • context/enemies.en.json
Requires viewing the videoDescribe a visible problem in the clips

Watch one gallery clip. Describe the first unusual behavior, when it appears and what you expected to see.

Acceptance

Provide clip name, URL, time in seconds, observation and expectation. Separate observation from hypothesis; record any inability to view the clip.

Requires viewing the public video or a supplied file. Text and a poster cannot establish that the animation was examined.

Required inputs

  • context/media.json
  • https://megaman.davidluky.com/galeria/
Uses public source codeMap the public snowball logic

Read the SnowballRoll implementation. Separate code rules, loaded data and inputs missing to reproduce a case. Propose one small next step.

Acceptance

Report the commit, functions, conditions and dependencies. Propose a patch only for a reproducible case using public inputs. A well-supported dependency map is a valid contribution.

Uses the public repository. Game definitions and captures are not included. Do not invent parameters or treat core contracts as proof of this enemy’s fidelity.

Required inputs

  • src/entities/enemy.cpp
  • src/entities/enemy.h
  • docs/reference-data.md
Uses public source codeMap the public Rotor drone update

Trace how the drone selects its direction and updates movement. Identify where state passes to physics and which inputs an independent test would require.

Acceptance

Submit paths, functions and update order, separating code observations from hypotheses. Do not claim gameplay tests or original-game comparisons without their required inputs.

Uses the public repository. Game definitions and captures are not included. Do not invent parameters or treat core contracts as proof of this enemy’s fidelity.

Required inputs

  • src/entities/enemy.cpp
  • src/entities/enemy.h
  • docs/reference-data.md
Uses public source codeTest JSON read results

Read json_io and existing coverage. If a direct contract is absent, add a temporary-file test for open failure, malformed JSON, schema rejection and a valid read.

Acceptance

Register one small contract in the public CMake configuration. Show the expected ReadError codes and CTest results. Preserve existing tests and do not load assets.

Do not duplicate a test. Use a unique temporary directory and clean up only files owned by that test.

Required inputs

  • src/data/json_io.h
  • src/data/json_io.cpp
  • cmake/PublicTests.cmake
  • CONTRIBUTING.md
Uses public source codeTest screen coordinate transforms

Inspect screen_transform and existing coverage. Propose a direct contract for invalid dimensions, letterboxing and points outside the internal viewport.

Acceptance

Test deterministic mathematics only, without opening a window. Register the CMake target and describe cases and CTest results.

Read existing contracts before adding another. Do not change scaling, camera or gameplay coordinates to accommodate the test.

Required inputs

  • src/app/screen_transform.h
  • cmake/PublicTests.cmake
  • CONTRIBUTING.md

Selecting a task does not reserve it. Check the issues and contribute from your fork. Original code is public under MIT; ROMs and assets are not included.

FROM RESPONSE TO CONTRIBUTION

Finished? Share the result.

  1. Review with your AI. Ask for sources, reproduction steps and what was not checked.
  2. Prepare the report. Use the included template. The checker validates format, not truth.
  3. Submit for review. Text and research by email or issue; code through a pull request to the public repository. Review your contribution before submitting.
Contact David ↗GitHub repository ↗