caf4d5e558
mrpci_request_save / mrpci_save_out / mrpci_save_in carry a SaveData across the wasm boundary, so the browser build can save and restore even though Command::SaveGame's std::fs call goes nowhere there. The moment being stored is exactly the one the native build writes to saves/<slot>.json — the same GameState::save_data — so a slot means the same thing in both places. F5 now asks the page instead of the filesystem; F7 points at the SAVES menu, because restoring needs to know *which* slot and a function key can't say. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| build.sh | ||
| index.html | ||
| mq_js_bundle.js | ||