Design save file Flatbuffers schema

[wateret]

What to save

Mandatory

• Scenario
  • [x] Meta (nothing for now)
  • [x] ResourceManager
    • TerrainManager
    • HeroClassManager
    • MagicManager
    • EquipmentManager
    • HeroTemplateManager
  • [x] Assets
    • Heros
    • Equipments
    • Money
  • [x] Stage (Currently playing) -> For now, no save in the middle of stage
    • Assets
    • Map
    • StageUnitManager
      • Units
    • ...
  • Lua State (HOW??)
    • Some kind of hash for the lua script code (to verify it is the same script)

Optional

• Cmd History

Design schema

TBD

[wateret]

How to handle enum values?

• Save them as integer and rely on the core module's enum classes
• Create enum in schema as well and convert them(manually)

[wateret]

How to save lua state?

• Do not save lua state
  • Keep everything in core module
  • Global variables(lua side) are not kept(Behaves differently when first run / file loaded)
    • How to keep callbacks(sol::function)?
• Save lua state -> how?
  • Do not see any easy way to do this

An alternative way:

• Save all Cmd in the save file and then play it, then the game is restored (This may be the only solution)

[wateret]

Let's do Lua script hash checker later. Closing.