# Crash BASIC 1.36.1 Release Notes

*~written by Crash-tan~*

## THE "SOLO CAN SAVE AGAIN" FIX

Quick but important one. If your **single-player** game tried to write a file —
`OPEN`, `SAVETEXT`, `SAVEJSON` — it could get slapped with:

> File I/O is not allowed on the client side in multiplayer.

…which is nonsense, because *you weren't in multiplayer.* Solo games are allowed
to read and write files, full stop. 1.36.1 makes that true again.

---

## What happened

Since 1.29.0, every solo game quietly gets its own behind-the-scenes "room" so
that `WITH ROOM` / `SET ROOM` and friends behave the same whether you're playing
alone or on a server. That solo room is supposed to count as *authoritative* —
solo means you're both the server and the only client, so you're allowed to do
server-side things like write save files.

One authority check didn't get the memo. The file-I/O gate saw "there's a room
attached" plus "I'm not flagged as the server" and concluded *multiplayer
client* — so it blocked the write and pointed you at `EVENT HOST "Save"`. Wrong
call for a solo game.

This affected **single-player on every platform — native desktop *and* the
WASM / browser build** — not just the browser, even though that's usually where
it showed up first.

---

## The fix

The file-I/O gate now recognizes solo mode for what it is: authoritative. Solo
games read and write files freely again, exactly like they always should have.

Real multiplayer is untouched — a genuine client in a live session still can't
write files directly (persistent storage stays server-authoritative; that's the
whole point), and the host / player-servers still can. Only the solo case was
wrong, and only the solo case changed.

---

## Compatibility notes

- **Pure bug fix — no language changes.** No new or changed keywords, functions,
  or behavior. Programs run exactly as before; the ones doing solo file I/O just
  stop erroring.
- **Multiplayer file-I/O rules are unchanged.** Clients still route saves through
  the host / server; only single-player was misclassified.
- **Rebuild both targets.** The bug lived in shared, platform-independent code,
  so the fix ships in both the native desktop builds and the WASM build.

---

*You're the server, the client, and the player. Of course you can save.*

*— Crash-tan*
