Variables accessible by Lua scripts, serialized as part of game state

[NoraCodes]

I think that the best way to handle keeping track of in-game state, things like "player has completed this quest", is to have, in game state and saved off with the rest of the game state's information, a way to store values by name. The syntax/semantics might be something like this:

To set an info by name:

set_info("completed castle quest", true)

Then, for example in an on_interact:

if get_info("completed castle quest") then
    say "Good job completing that quest!"
else
    say "You'd better get busy with that castle quest!"
end

[NoraCodes]

To clarify, variables created in the normal way wouldn't get saved as part of game state.

[arces]

From my understanding it will be "hard stored" (Written somewhere on disk, or flagged to be written on disk when the save event comes) and recoverable when the player calls set_info or create_info (or whatever the creation of the event will be)

[NoraCodes]

I was envisioning the game state being written to disk all at once, when
the game is saved through the menu. That way, retrieval is fast and the
entire game state can be passed around to different functions as needed.

On Thu, Jul 7, 2016, 10:42 PM Dan Janes notifications@github.com wrote:

From my understanding it will be "hard stored" (Written somewhere on disk,
or flagged to be written on disk when the save event comes) and recoverable
when the player calls set_info or create_info (or whatever the creation of
the event will be)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#7 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ADI0_erliI14iFnoIMG0mmj8h6bKLDbdks5qTeNCgaJpZM4JHuxY
.