You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, save data is enough to do just about anything, but very barebones, and requires large amounts of boilerplate to achieve basic functionality. If the game provided a few automatically serialized tables for various conditions, the problem of managing save data could be averted almost entirely.
Such tables could include:
Global save data that is never reset
Run save data that is reset upon starting a new run, but kept through continues
Level save data that is reset upon entering a new stage
Room save data that is reset upon entering a new room
Entity save data that is tied to individual persistent entities, like the player, pickups, and slot machines
Serialization should cover:
Numbers, bools, strings, nil, and tables of various depths containing those values
Vectors
Colors (if this is possible given Colorize?)
Error detection if a value is included that cannot be serialized
It could make sense to just use json for serialization like mods do currently, for ease of serializing basic values, with special handling for vectors and similar.
The text was updated successfully, but these errors were encountered:
Currently, save data is enough to do just about anything, but very barebones, and requires large amounts of boilerplate to achieve basic functionality. If the game provided a few automatically serialized tables for various conditions, the problem of managing save data could be averted almost entirely.
Such tables could include:
Serialization should cover:
It could make sense to just use json for serialization like mods do currently, for ease of serializing basic values, with special handling for vectors and similar.
The text was updated successfully, but these errors were encountered: