The header is part of the picture.

Before you start

Check region and cartridge revision, then the required iNES or NES 2.0 representation. NES 2.0 uses a 16-byte header and may include trainer data. A .nes extension alone is not enough.

Don’t strip an NES header using a SNES copier-header recipe, change mapper fields or add/remove trainer data without a verified release instruction. Famicom Disk System images need a separate guide; this is cartridge guidance.

The tested setup matters

Match the release’s emulator/core version, mapper support, region/timing and expansion-device settings.

Check, patch, then play

1. Keep an untouched backup. Work on a separate copy.
2. Compare the exact source and extracted patch SHA-256 values with the release page. Check files locally →
3. Open the patcher/version named by the release. Select the verified source and patch; choose a different output filename. Use only the documented settings and patch order.
4. If supplied, compare the output SHA-256 before launching it. Matching bytes do not prove a complete playthrough.
5. Use the tested emulator configuration from the same release guide. Real hardware, flash cartridges, old saves and save states require their own evidence.

No patcher or patch format is approved for these drafts yet. BPS support in a tool is not universal game or platform compatibility.

Something doesn’t match?

Wrong source checksum

Recheck platform, region, revision, size and required header/container form. A filename is not proof. Don’t edit bytes to make a checksum match.

Wrong patch checksum

Check that you hashed the extracted patch, not its archive. Download that version again from the release link. If it still differs, stop.

Patcher rejects the input

Confirm tool version, source form and patch version. Start from the untouched original; don’t patch an already patched file or force a source mismatch.

Output checksum differs

Keep it separate and don’t treat it as verified. Recheck inputs, options and patch order.

Correct files, but the game fails

Match the published emulator/core version, machine and region settings. Disable undocumented cheats or automatic patches. Use the documented boot sequence instead of an old save state.

Public reporting is closed for now. Keep error messages and non-sensitive setup details locally. Do not send ROMs, disk images, firmware or private logs.

Format reference · Reference documentation is not Patch Quest compatibility certification.