Browser play guide
Magma Dragoon Mod Updates and Save Backups
By RetroHours · Updated
RaylerProductions · Game by Cat Yard Games
On this page
Before updating Magma Dragoon Mod for Mega Man X: Viral Nightmare, keep two things: the game package you are currently playing and an exported copy of your save. That gives you a clear starting point if you need to compare releases or return to your existing setup.
The creator’s download link is updated with batch patches, so it also helps to record when you downloaded the files. Here is a short routine you can use for each update.
Check the release post before replacing files
Start with RaylerProductions’ V1.1 video and description, which links the MMXVNDRAGOON1.1.zip download. Follow any newer release information from the creator and read the instructions supplied with the package.
Keep three details together:
- The version or batch named by the creator
- The date you downloaded the package
- Any instructions about the required base game or saves
A link that receives patches can stay the same while its contents change. Keeping your download date is a simple way to distinguish copies without having to guess later.
Export your current save
If you play in RetroHours, use the game’s normal save feature and stop the session with the player’s controls. Open Saves, select the relevant game if asked, and choose Download current saves before changing files. You can also use Download beside a completed backup.
Give the backup a name you will recognize, such as “Magma Dragoon V1.1, before update, October 11.” Keep the original downloaded backup intact. If you later need a working copy, duplicate it rather than replacing the only backup you have.
Store mod saves separately from unmodified Viral Nightmare saves and files from other batches. A small folder with the original ZIP, save backup, and a text note of the version is enough. You do not need a complicated archive system.
Local browser saves depend on the browser and device you use. Exporting a file also protects you when clearing site data, changing browser profiles, or moving to another computer.
Follow the creator’s advice when returning to other batches
In the V1 release description, the creator recommends making a New Game file if you want to go back to other batches.
Plan that return around a fresh file and retain your mod progress separately. The advice is specifically useful for moving between batches; it is not a published compatibility chart for every possible update.
To bring progress into a newer release, open Saves for the new release. If the earlier release is still on your shelf, select it and choose Copy saves; otherwise choose Import backup and select the file you exported. Then choose Restore beside the copied files. Check the release instructions first: the game decides whether it accepts saves from another release, and the saves you replace stay in the list.
Test the update before a long session
Keep the previous package while you try the new one. Once the new release launches, make a short check:
- Confirm you opened the intended version using the package details and any version information shown in the game.
- Test movement, attacks, menus, and sound.
- Check the feature or fix mentioned in the release notes, if you can reach it.
- Save normally, end the session, and launch the same release again.
- Confirm that your new progress loads, then export a fresh backup.
If the release instructions recommend starting a new game, use that path for the test. Keep the older backup until you are satisfied with the new setup.
Make a bug report easy to reproduce
A useful report tells the creator how to reach the problem. Include:
- Mod version, batch information, and download date
- Where the problem happened and which character, parts, or equipment you used
- The steps just before it happened and whether it happens again
- Whether you started a new file or used an existing save
- Your play method, device, and browser if relevant
- The exact error text, or a screenshot or short clip showing the problem
Use the creator’s linked Discord reporting route for mod issues. For a browser import or player error, use RetroHours help. You do not need to know the cause before reporting; describing what you saw is more useful than guessing.
Check screenshots and filenames for personal information before sharing them. Keep an untouched save backup, and provide a copy only if it is needed to reproduce the issue.
If you are setting up the mod for the first time, the Mac browser guide covers the initial import. For later updates, the essential habit is the same: keep the old package, export the save, and test the new release before settling in.
The mod overview explains the currently playable encounter and the planned full stage.
Creator credit and sources
Magma Dragoon Mod is a community project associated with RaylerProductions. Mega Man X: Viral Nightmare is by Cat Yard Games. Mega Man and its characters belong to Capcom. RetroHours is independent and is not affiliated with or endorsed by these creators or Capcom.