You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(saves): tell the setup wizard a 404 is an answer, not an outage
get_save_setup_info collapsed every server-saves failure onto
recommended_action "server_unreachable", so a RomM database reset — which
drops this device's registration and makes the saves query 404 — told the
user their server was offline while it was answering fine.
Add a fourth arm, "not_found", peeled off with a sibling
except RommNotFoundError. It holds the wizard exactly as the unreachable
branch does: a 404 leaves the server's slot inventory just as unproven as an
outage, so auto-confirming the default slot could still clobber real server
saves on the first post-confirmation sync. The launch gate likewise still
aborts. Only the copy and the reachability verdict change.
The copy deliberately does not say the game has no saves. The 404 can come
from the device registration rather than the ROM, so that would swap one lie
for a more specific one; it states what RomM could not find instead.
SlotSetupWizard needed no change: it already tested for an explicit
server_unreachable, so a not_found result now correctly reports the server
reachable and leaves the reconnect gate disarmed.
This clears the last site flagged by check_404_not_unreachable.py.
0 commit comments