Confirmed — and you've put your finger on two separate gaps.

First: the options are only written to disk when you CLOSE the System Option window. Everything in there applies live as you click it, so it's very easy to change a setting, watch it take effect, and then have the page reload (the preview does that a lot) before anything was ever saved. It comes back on the old value and looks like it never saved at all.

Second, and this is the one you're really asking for: even when they do save, they save into this browser's local storage — not onto your character. Your key bindings ARE stored with the character, so they follow you; the system options aren't, so a different browser, a cleared cache, or a fresh preview session starts you back at the defaults.

The fix is both halves: write the settings the moment any of them changes rather than waiting for the window to close, and add them to the character save blob next to the key config so they ride along with you like your keys do. On load, the saved-with-the-character values are applied over the local ones.

Half of this is now fixed, and it's the half that was making it look completely broken. Everything in the System Option window takes effect the moment you click it, but the values were only ever written to disk when you CLOSED the window — so if the page reloaded first (and the preview reloads a lot) nothing had been saved and you got the old value back. Settings are now written every half second while the window is open, so mute, the FPS limiter, the sliders and the radio buttons all survive a reload or a relog even on a guest account. The second half of what you asked for — storing them ON your character the way your key bindings are, so they follow you to another browser or a fresh session — is a bigger change that touches the character save blob and the save edge-function, and it is not in this patch. I've kept that on the list.

The second half of this is now done, and it's saved in the database.

Settings are stored ON your character, in the same save blob as your key bindings — so they follow you to another browser, another machine, or a fresh session, instead of living only in this browser's local storage. Written whenever you close the System Option window (which now also pushes the save straight away rather than waiting for the next autosave tick), and applied back over your local values on load.

Two details worth knowing:

Older saves that predate this simply keep whatever your browser had. The merge fills in missing fields rather than replacing them, so a save written before a given option existed can't blank it.

Viewing mode (window vs full screen) is remembered but deliberately NOT re-applied at login. Browsers only allow fullscreen from a real click, so forcing it on load would just be ignored — it takes effect the next time you toggle it. Everything else (mute, volumes, the FPS limiter, picture quality, HP/MP alerts, screen shake) restores on login.

Status stays FIXED.