OPEN REQUESTS NOW

What still needs to be recorded in Mega Man X.

Today there are 2 open requests. For each one, this page says what to do, where, what to have first, what counts as done and how long to keep recording.

Utuboros, the sea serpent 2 open requests · 2 of 6 parts already seen by the project

This page changes over time. When recordings arrive, the project checks them. What it has already seen gets a ✓ mark and a request that was answered leaves the list.

Status checked on 2026-10-16.

The full list, with all three games and what is already done, is at Requested recordings.

Go to the requests ↓

How to record

A recording is not a video: Mesen saves only the buttons you press, in a small file (.mmo). Use the project recording pack.

Download the recording pack ↓

Set up the pack Unzip the pack into a folder. Unzip Mesen 2.1.1 so that Mesen.exe sits inside the pack's Mesen folder, without deleting settings.json. Put your ROM in 1-PUT-YOUR-ROM-HERE and run 2-CHECK-THE-ROM.bat: it must show OK in green. Open Mesen with 3-PLAY-AND-RECORD.bat, set up your controller in Settings > Input and open the ROM with File > Open.
Reach the starting point without recording Go to the boss door, or just before the enemy, and save a save state there. Before you start recording, loading a save state is fine, as often as you like.
Record your attempt Menu Tools > Movies > Record. Save the file in the pack's recordings folder, with the name the list gives. Under Record from, choose Current state. Use Power on only when the list asks for it.
Stop and check Menu Tools > Movies > Stop. Check that the .mmo file is in the folder. Did it not go as planned? Load the save state and record again with the same name plus -b at the end (then -c, -d). Do not delete the earlier ones: a failed attempt is useful too.

All the steps, the list of what you need and the golden rules are in Play and record →

How to send

Zip the recordings folder and email it to davidluky@davidluky.com, the website's contact. You can send them a little at a time, after each session. Do not send the ROM.

Name of each recording: the file name is the request name, exactly: X1-S3-vile.mmo. If you split it into parts: X1-S3-vile-b.mmo, X1-S3-vile-c.mmo. In the movie description (the text box when recording), write the same name.

Each request below shows the file name it uses. You can put several requests of the same fight in one recording.

The open requests 2 open requests

Utuboros, the sea serpent Launch Octopus stage

2 open requests · 2 of 6 parts already seen by the project

Utuboros: charged Fire Wave
What to do
Hit the serpent's head, body and tail with a fully charged Fire Wave shot. On the body the shot bounces off and the serpent loses no life: that is expected, and the hit counts anyway.
Where
In the Launch Octopus stage, in the fight against the sea serpent Utuboros.
What to have first
Have Fire Wave and the arm part. You can use the game's password to arrive with everything.
What counts as done
A fully charged Fire Wave shot hitting each part of the serpent marked with ○ just below. On the body the shot bounces off and the serpent loses no life: the hit counts anyway.
- Head: still to be seen.
- Body: still to be seen.
- Tail: still to be seen.
Parts the project has already seen: 0 of 3.
How long to keep recording
Keep recording for a few seconds after each hit on the head, the body or the tail. Only then stop.
Why it helps
A recording of this fight already arrived and the project checked it: this hit is not in it. Without it, the damage of this weapon on the serpent cannot be checked.
File name: X1-S1-utuboros
Technical details
Parts: boss.utuboros.damage 23:weapon:9, 24:weapon:9 and 25:weapon:9 (each boss object, 0x23, 0x24 and 0x25, counts separately). B15 stop b15-utuboros-23-4-charged: needs a recording of this fight with the weapon and the arm part (boss_step_sweep_2026-10-04_b45.json). Source: build/R130/volunteer.json, class H.
Checked on 2026-10-11 (S23, build/S23/check.md): recording_events.py, the H25 scan of the 156 movies without a capture and the r109 intake show this part in no recording. The two verified recordings of this fight (vol-b5-utuboros-1 and vol-b5-utuboros-death-1, intake r109 of 2026-10-09) hold no charged special-weapon shot while Utuboros is active, and object 0x24 loses no life in either. No light-intake movie shows this fight. This item is part of request X1-S1-utuboros, which stays open.
Update of 2026-10-12 (task H30, knowledge_base/mmx1/rom/boss_hunts_2026-10-12_h30.json): the automatic hunts with charged weapons (42, over the 21 parts, from two verified recordings of this fight) reached only 2 parts, 24:weapon:7 and 25:weapon:15; the other 40 stopped at the 2400-frame input limit. This weapon still has all three parts open.
Utuboros: charged Storm Tornado
What to do
Hit the serpent's head, body and tail with a fully charged Storm Tornado shot. On the body the shot bounces off and the serpent loses no life: that is expected, and the hit counts anyway.
Where
In the Launch Octopus stage, in the fight against the sea serpent Utuboros.
What to have first
Have Storm Tornado and the arm part. You can use the game's password to arrive with everything.
What counts as done
A fully charged Storm Tornado shot hitting each part of the serpent marked with ○ just below. On the body the shot bounces off and the serpent loses no life: the hit counts anyway.
- Head: already seen by the project (volunteer recording, 10/15/2026).
- Body: still to be seen.
- Tail: already seen by the project (volunteer recording, 10/15/2026).
Parts the project has already seen: 2 of 3.
How long to keep recording
Keep recording for a few seconds after each hit on the head, the body or the tail. Only then stop.
Why it helps
A recording of this fight already arrived and the project checked it: this hit is not in it. Without it, the damage of this weapon on the serpent cannot be checked.
File name: X1-S1-utuboros
Technical details
Parts: boss.utuboros.damage 23:weapon:11, 24:weapon:11 and 25:weapon:11 (each boss object, 0x23, 0x24 and 0x25, counts separately). B15 stop b15-utuboros-23-5-charged: needs a recording of this fight with the weapon and the arm part (boss_step_sweep_2026-10-04_b45.json). Source: build/R130/volunteer.json, class H.
Checked on 2026-10-11 (S23, build/S23/check.md): recording_events.py, the H25 scan of the 156 movies without a capture and the r109 intake show this part in no recording. The two verified recordings of this fight (vol-b5-utuboros-1 and vol-b5-utuboros-death-1, intake r109 of 2026-10-09) hold no charged special-weapon shot while Utuboros is active, and object 0x24 loses no life in either. No light-intake movie shows this fight. This item is part of request X1-S1-utuboros, which stays open.
Update of 2026-10-12 (task H30, knowledge_base/mmx1/rom/boss_hunts_2026-10-12_h30.json): the automatic hunts with charged weapons (42, over the 21 parts, from two verified recordings of this fight) reached only 2 parts, 24:weapon:7 and 25:weapon:15; the other 40 stopped at the 2400-frame input limit. This weapon still has all three parts open.