Una, the moon minus two
the full text for the options, in case your instance hasn't been updated to 3.0 yet (like mine)
offer a converter to a simpler format
allow running a "database server" to modify the save
throw this format away, you need something simpler
just let them fend for themselves
Una, the moon minus two
Sawdust saves are a proper database format, and are not easily read/written without the official library for them, which is only available for Java
what is the best approach for allowing third-party devs to edit save files?
[ ] offer a converter to a simpler format
[ ] allow running a "database server" to modify the save
[ ] throw this format away, you need something simpler
[ ] just let them fend for themselves
Una, the moon minus two
bbcode (baby code)
Una, the moon minus two
Una, the moon minus two
@zoe WMV and WMA are the Timeout Zone
Una, the moon minus two
@zoe bad container for bad codecs
Una, the moon minus two
@sc pff
Una, the moon minus two
@zoe also not too thrilled by it being closed source
Una, the moon minus two
@zoe Oh Boy My Favorite
Una, the moon minus two
you press a button by accident or click in the wrong place and it clears your selection without recourse
EXTREMELY frustrating when you're trying to do nearly-sample-accurate selections
Una, the moon minus two
I hate Audacity
Una, the moon minus two
@zoe https://breakbeatheartbeat.bandcamp.com/track/flashback
https://breakbeatheartbeat.bandcamp.com/track/shakes
Una, the moon minus two
@zoe flashback/shakes
they play in the main menu on next launch if a crash was detected
Una, the moon minus two
I think I'm going to trim the crash music to a minute long because it's rarely heard
Una, the moon minus two
just changed the music playing logic so it'll avoid playing the same track over and over if at all possible
Una, the moon minus two
@monorail @zoe also, that wouldn't detect e.g. kill -9, power failure, etc
Una, the moon minus two
@monorail @zoe crash handlers have to do the bare minimum and assume nothing, and I don't yet have one
Una, the moon minus two
@zoe I mean, what you're really checking for is "exit code did not run"
so the best way to do that is to add a flag that says "exit succeeded" when you exit and clear it when you start
Una, the moon minus two
I detect an abrupt shutdown by adding an "abruptShutdown: true" line to the config on game start and changing it to false when the game exits
Una, the moon minus two
nope. still a little crunchy
Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.
All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.