Test saving before relying on it
Use a disposable session to identify the game's own saving and the console's menu save function. Record which slot you selected and the point it contains. Then quit normally, reopen the game and test loading. Keep an important checkpoint separate from experimental slots so a mistaken save or load does not replace the only known good state.
The original Evercade manual documents its game-menu save and load controls. Super Pocket's official support likewise describes choosing a numbered slot from the game menu. Treat those as procedures for the named devices, and read the current manual when using a different model. Cross-device save behavior should be tested with expendable progress rather than assumed from a shared cartridge format.
Preserve a useful save inventory
- Console model and firmware, cartridge collection and game title.
- Slot number, approximate checkpoint and date last verified.
- Whether the progress uses an in-game save, a menu state or both.
- Any backup tool and release used, with the destination of the exported files.
EverSD's dated releases describe save backup and restoration features for supported patched setups, with fixes affecting particular formats over time. Read the relevant release notes before selecting a method. Current software and supported-device listings matter more than a video made for an older patcher. Keep an untouched export and test restoration on an unimportant save.
A microSD used by a third-party loader is not automatically a backup of every retail cartridge or internal built-in game. Inventory what the tool actually exported. Preserve filenames and metadata and keep a second copy on separate storage. Do not overwrite the source cartridge merely to check that a backup file exists.
Controller troubleshooting
For VS or VS-R input, begin with a documented controller connected directly. Blaze's VS-R controller manual names supported platforms and warns that controls differ between systems. Record whether the menu responds, which port is used and which player the game assigns. Add hubs, adapters or other controllers only after that baseline works.
If input fails only in one game, read its controls and compare another title. A missing shoulder-button action, an arcade coin input and a disconnected controller are separate issues. Keep a short table of each button's result when reporting a mapping problem. Avoid opening a controller before testing another cable route or supported port.
Care and charging checks
Use the power specification and cable instructions for the exact model. Inspect ports without inserting metal tools or forcing a connector. Compare a known working cable and suitable power source when charging is intermittent. The EXP-R quick-start guide identifies low battery indications and says to leave rear vents clear.
Store cartridges in their cases with labels readable and contacts protected. Keep liquids away from consoles and controllers, and disconnect power before external cleaning. A unit with battery swelling, abnormal heat or damaged charging hardware needs assessment before further use. Retain photographs and the circumstances of the fault for support.
See maintenance and recovery planning before resetting a device, and the compatibility record before treating one model's result as applicable to the whole family.
Sources and review
Reviewed October 11, 2026. The linked manufacturer and project documentation establishes supported behavior. The diagnosis checklists and preservation suggestions are original editorial guidance. Menus, services and project support can change; verify the linked instructions before an irreversible change.
- Blaze original Evercade quick-start manual, preserved reproduction
- Blaze Evercade EXP-R quick-start manual, preserved reproduction
- Blaze VS-R controller manual, preserved reproduction
- Official Super Pocket controls, save and update support
- EverSD current EveryPatcher and EverLoader3 downloads and device listing
- EverSD dated release history and feature changes