chameleonic

PICO-8 game: you're a chameleon with rope physics

Go to file

Kistaro Windrider b6d1a21b7e Basic save/load system (#23 ) Save/load system. Not golfed. Saves the music flag, the last level the player played, and the furthest level reached. Loads music flag on launch. Title screen starts on most recent level played; when in "release configuration" the title screen will only let the player pick levels up to the maximum reached through gameplay, but right now this is replaced with the 31. Save file can be wiped by holding the down arrow at the title screen. block writes while reading Disabling writes during "wipe" and "first load" is not quite semantically what we want, it's writes during read we want to block. This happens because turning the music on or off tries to save the state, and it's easier to just ignore that persistence request than to rework the music code so it doesn't. "wipe" and "first load" are when we're actually reading (and enacting) state, but it's the act of reading rather than those two acts that should block writes. It is also unwilling to write until it's done its first read, which I think is a feature; it makes it harder to accidentally blank out the player's data. Reviewed-on: #23 Co-authored-by: Kistaro Windrider <kistaro@gmail.com> Co-committed-by: Kistaro Windrider <kistaro@gmail.com>	2023-01-02 23:08:03 +00:00
chameleonic.p8	Basic save/load system (#23 )	2023-01-02 23:08:03 +00:00
README.md	Initial commit	2022-12-17 12:16:18 -08:00

Kistaro Windrider b6d1a21b7e Basic save/load system (#23 )

Save/load system. Not golfed.

Saves the music flag, the last level the player played, and the furthest level reached. Loads music flag on launch. Title screen starts on most recent level played; when in "release configuration" the title screen will only let the player pick levels up to the maximum reached through gameplay, but right now this is replaced with the 31.

Save file can be wiped by holding the down arrow at the title screen.

block writes while reading

Disabling writes during "wipe" and "first load" is not quite semantically what we want, it's writes during read we want to block. This happens because turning the music on or off tries to save the state, and it's easier to just ignore that persistence request than to rework the music code so it doesn't. "wipe" and "first load" are when we're actually reading (and enacting) state, but it's the act of reading rather than those two acts that should block writes.

It is also unwilling to write until it's done its first read, which I think is a feature; it makes it harder to accidentally blank out the player's data.

Reviewed-on: #23
Co-authored-by: Kistaro Windrider <kistaro@gmail.com>
Co-committed-by: Kistaro Windrider <kistaro@gmail.com>

2023-01-02 23:08:03 +00:00

chameleonic.p8

Basic save/load system (#23 )

2023-01-02 23:08:03 +00:00

README.md

Initial commit

2022-12-17 12:16:18 -08:00

README.md

EAT BUGS, SPACE SCUM