-
Notifications
You must be signed in to change notification settings - Fork 3
Data Schema::Save File
Subject9x edited this page Oct 6, 2023
·
2 revisions
battleMETAL uses a custom save file format and pipeline compared to vanilla Quake. This was caused by Quake's save files not preserving entity links, which would screw up multi-part entities. The save format also would not have been able to save the player's mech list and equip list data either. Therefore a custom save file was decided on.
- Each save file is stored in /data/saves/
- they're numbered 0 - 6, each represents a save 'slot'.
- save files are plaintext files with the .sav extension.
- all values are strings, and converted during save file load.
- save = the saveslot number of the save file.
- mission = the mapname of the map the player is on.
- mechs = a list of all the UID's of the mechs the player has, see
- items = a list of all the UID's of the equipment the player has.
- points = unused and deprecated for now.
- newgame+ = determined by campaign file syntax, mostly leave alone.