KNULLI Save States Not Working? Check RetroAchievements Hardcore Mode

Short Answer

If Quick Load will not restore a save state while RetroAchievements is active, check HARDCORE MODE before assuming the state system is broken.

On KNULLI, the documented path is:

START → Game Settings → RetroAchievement Settings → HARDCORE MODE

Hardcore consistently restricts loading states. Creating a state is less clear across the official sources: RetroAchievements says creation remains allowed, while KNULLI’s hotkey documentation describes save and load actions more broadly as disabled. Check Create and Load separately.

If you accept the achievement consequences, turn only HARDCORE MODE off, back out of the menu, and relaunch the same supported libretro game. Do not turn off the master RETROACHIEVEMENTS switch.

Symptoms

This guide applies when a game is already running through a supported RetroArch/libretro core and one of these happens:

  • Quick Load shows: “You must pause or disable Achievements Hardcore Mode to load states.”
  • Quick Load does nothing or does not return to the earlier scene.
  • RetroArch reports that Achievements Hardcore Mode is enabled.
  • Quick Save appears to work, but Quick Load does not.
  • Both Quick Save and Quick Load appear unavailable while Hardcore is on.

The first three strongly match an active-Hardcore restriction. The last two require separate Create and Load checks because official wording conflicts on creation.

Hardcore is a cause to confirm, not a default explanation for every save-state problem. If HARDCORE MODE is already off, the game is not recognized by RetroAchievements, or the controlled Casual test fails, stop at the bounded alternative-cause section below.

Scope and Evidence

Version and evidence scope

  • Audience: Anbernic RG CubeXX and KNULLI H700 users
  • Firefly 20241204: RetroArch 1.19.1
  • Gladiator II 20250813: RetroArch 1.20.0
  • Scarab 20260511: RetroArch 1.22.2
  • Evidence: Official documentation and tagged or release-pinned source; no owner hands-on testing
  • Proof boundary: One legally owned, RetroAchievements-recognized game using a supported libretro core

The three releases use the same KNULLI path and Hardcore setting. KNULLI passes that switch to RetroArch as cheevos_hardcore_mode_enable when it launches the game.

This is not a guide to battery-backed or ordinary in-game saves, state-file repair, changing emulators, standalone-emulator troubleshooting, or game-specific bugs.

Non-overlap audit

PASS — article #9 second-SD storage guide. This article changes no storage target and performs no file or card repair. Readers with a second-card selection problem should use the separate KNULLI storage-selection guide.

PASS — Quick Menu/M+B guide. This article assumes the game session is accessible. It does not open or repair RetroArch’s Quick Menu, remap M+B, or change per-core hotkeys. Verification uses KNULLI’s documented direct Quick Save and Quick Load shortcuts.

Confirm Libretro, RetroAchievements, and Hardcore Status

Confirm all three conditions before changing the setting.

1. Confirm a supported libretro core

The deterministic procedure in this guide applies to RetroArch/libretro. KNULLI also forwards achievement settings to some standalone emulator generators, but their state controls, messages, and exact behavior are emulator-specific.

If the selected emulator is standalone, stop. Do not assume RetroArch hotkeys or warnings apply to it.

2. Confirm that RetroAchievements recognizes the game

Use a game that the current RetroAchievements session identifies. A network connection or enabled master switch alone does not prove that the game is recognized or supported.

If the game is not recognized, do not use that launch to prove the Hardcore diagnosis.

3. Check the exact KNULLI switch

Return to EmulationStation, then:

  1. Press START to open the Main Menu.
  2. Open Game Settings.
  3. Open RetroAchievement Settings.
  4. Under OPTIONS, find HARDCORE MODE.

The English frontend description is:

Disable loading states, rewind and cheats for more points.

Language and theme presentation can vary. The relevant control is HARDCORE MODE, not the master RETROACHIEVEMENTS switch.

If HARDCORE MODE is off, this article’s diagnosis does not pass. Do not toggle it repeatedly or begin unrelated repairs.

What Hardcore Restricts—and Why Create Is a Separate Question

All authoritative sources agree on the important part: loading a save state is restricted while Hardcore remains active.

RetroArch 1.19.1, 1.20.0, and 1.22.2 include this warning:

You must pause or disable Achievements Hardcore Mode to load states.

The conflict concerns state creation:

  • RetroAchievements says Hardcore restricts loading states and explicitly says creating them is still allowed.
  • KNULLI’s Hardcore setting description names loading states, not creation.
  • KNULLI’s hotkey page broadly says save/load, fast-forward, and rewind actions are disabled in Hardcore.
  • RetroArch has precise “loading save states” wording but also a broader status message saying save state and rewind were disabled.
  • RetroArch’s changelog records support for creating an automatic save state in Hardcore.

The safe conclusion is narrow:

  • Expect Load to be blocked when Hardcore is active.
  • Do not promise that Create will always be available on every screen or binding.
  • Do not claim both actions must always fail.
  • A state that appears to be created does not prove Hardcore is off.

Choose: Keep Hardcore or Switch to Casual

Make the choice before changing the toggle.

Keep Hardcore enabled

Leave HARDCORE MODE on if Hardcore credit matters more than loading states. Loading an earlier state will remain restricted.

Do not try to bypass the restriction or use states to obtain Hardcore credit.

Turn Hardcore off

With Hardcore off, achievements can still unlock in Casual mode. They are not Hardcore unlocks.

New play in that Casual session:

  • does not count toward Hardcore completion;
  • cannot award a game Mastery, gold border, or recent-master listing;
  • does not place the player on the main Hardcore leaderboard;
  • cannot submit game-specific leaderboard scores, times, or challenges that require Hardcore;
  • usually does not qualify for events that require Hardcore.

Turning Hardcore off changes how new play is credited. It does not erase or downgrade previously earned Hardcore achievements. Do not assume eligibility remains unchanged after the switch.

Turn Hardcore Off and Relaunch the Game

If Casual mode is acceptable:

  1. Quit the game normally to EmulationStation.
  2. Open START → Game Settings → RetroAchievement Settings.
  3. Leave RETROACHIEVEMENTS enabled.
  4. Turn HARDCORE MODE off.
  5. Back out of the menu so KNULLI saves the setting.
  6. Launch the same game again through the same supported libretro core.

KNULLI reads the setting and writes RetroArch’s Hardcore option during game launch. A full device restart is not required for this GUI change.

Do not edit configuration files, use shell access, change the core, reset KNULLI, or update or downgrade the system for this procedure.

Test One Supported Game with a Fresh Slot

For a controlled check, use:

  • a legally owned, RetroAchievements-recognized copy of Super Mario Bros. (NES);
  • the FCEUmm libretro core, identified by RetroAchievements as its most-recommended NES libretro core;
  • default KNULLI hotkeys;
  • one visibly unused, nonvaluable state slot.

Slot 9 is only an example. Use it only if the on-screen slot indication shows that it is unused and nonvaluable. Never overwrite a state you care about.

Default KNULLI controls for this check are:

  • Function + D-pad Up: next state slot
  • Function + D-pad Down: previous state slot
  • Function + west/left face button (Y): Quick Save
  • Function + north/top face button (X): Quick Load

User customization can change these defaults. This article does not repair or remap customized bindings.

Verify Create and Load Separately

Create check

  1. Start World 1-1.
  2. Stay near the opening position where Mario, the first Goomba, and the first pipe make the scene easy to identify.
  3. Use Function + D-pad Up/Down to select the fresh test slot.
  4. Confirm from the slot notification that it is the intended unused slot.
  5. Press Function + west/left face button (Y) once.

Create PASS: A save-state-created notification or thumbnail appears for that slot.

Create FAIL: No state is created. Stop. This guide does not establish whether the remaining cause is a binding, core, or another state-system issue.

Creation passing does not, by itself, prove that Hardcore was off because RetroAchievements says creation is allowed in Hardcore and the official presentation conflicts.

Load check

  1. Keep the same slot selected.
  2. Make the scene visibly different by moving Mario beyond the first pipe.
  3. Press Function + north/top face button (X) once.

Load PASS: Gameplay returns to the exact earlier opening position. This demonstrates that the fresh state was created and loaded in this Casual RetroArch session.

Load FAIL: The changed scene remains or a load error appears. Stop. Hardcore is not established as the sole remaining cause.

This result applies only to this game, core, slot, and session. It does not prove old-state compatibility, support in other games/cores, long-term persistence, or Hardcore eligibility.

Release Differences

Firefly 20241204

  • Official RG CubeXX/H700 release image
  • Bundled RetroArch 1.19.1
  • Path: START → Game Settings → RetroAchievement Settings → HARDCORE MODE
  • KNULLI writes cheevos_hardcore_mode_enable at launch
  • RetroArch includes the Hardcore Load State warning

Gladiator II 20250813

  • Official RG CubeXX/H700 release assets
  • Bundled RetroArch 1.20.0
  • Same KNULLI path and switch description
  • Same generated RetroArch option and Load State warning

Scarab 20260511

  • Official RG CubeXX/H700 release asset
  • Bundled RetroArch 1.22.2
  • Same path and setting behavior
  • Pinned frontend source confirms RETROACHIEVEMENT SETTINGS, OPTIONS, HARDCORE MODE, and the “Disable loading states…” description

The standalone-emulator generator inventory differs by release. That does not broaden this article’s proof: the controlled procedure remains limited to a supported libretro core.

If It Still Fails

Stop after one confirmed Casual relaunch and one fresh-slot Create/Load test.

  • HARDCORE MODE was already off: This diagnosis does not fit.
  • The game is not recognized by RetroAchievements: This launch cannot verify the expected Hardcore restriction.
  • The emulator is standalone: RetroArch proof does not transfer automatically.
  • Create fails in confirmed Casual mode: Another cause exists outside this guide.
  • Create passes but Load fails in confirmed Casual mode: Hardcore is not the sole remaining cause.

Possible alternative categories include an unsupported state function, an incompatible state, a customized binding, a changed core, or a game/core-specific issue. They are deliberately out of scope here.

Do not delete states, repair storage or configuration, switch cores, reset or reflash KNULLI, or update or downgrade as part of this article.

FAQ

Does Hardcore Mode block loading save states?

Yes. Official sources consistently restrict loading while Hardcore is active.

Does Hardcore Mode always block creating a state?

Do not state that as a universal fact. RetroAchievements says creation is allowed, while KNULLI’s hotkey documentation uses broader save/load wording. KNULLI’s setting description and RetroArch’s warning specifically name loading. Test Create and Load separately.

Should I disable RetroAchievements completely?

No. Leave the master RETROACHIEVEMENTS switch on. This procedure changes only HARDCORE MODE.

Do I need to reboot the RG CubeXX?

No device reboot is required for this GUI toggle. Back out of the settings and relaunch the game so KNULLI generates the new RetroArch setting.

Will Casual mode still unlock achievements?

Yes, but they are Casual unlocks. They do not count toward Hardcore completion, Mastery, the main Hardcore leaderboard, game-specific leaderboards requiring Hardcore, or most Hardcore-required events.

Will turning Hardcore off erase earlier achievements?

Official sources do not support that claim. Turning it off changes how new play is credited; it does not erase or downgrade previously earned Hardcore achievements.

Does this procedure apply to standalone emulators?

Not as a guaranteed fix. Their controls, warnings, and state behavior are emulator-specific. The deterministic test in this guide is for FCEUmm running through RetroArch/libretro.

Sources

KNULLI

RetroAchievements and Libretro

RetroArch