v0.8.0

Changelog

3D Map Save Editor

• New object data/property UI
  • The tool is now a save game editor, the new UI can edit most values within objects.
  • The new property UI uses a tree view instead of nested tables. This improves viewing nested data structures a lot.
• Add full support for 1.0 save games
• Add support for class specific binary data (belts, vehicles, powerlines, ...)
• Support lightweight buildables
• Add window for save header
• Add window for camera settings

Save Game Libary

• Refactor save object structure
  • There is now a single non-polymorphic SaveObject class that holds the object header and the object instance data.
  • Objects use class names and a class hierarchy close to the original ones in the game.
  • Rename some structs and variables to better match original names.
  • Replace the file system like node iteration by a simple getObjectsByClass() / getObjectsByPath() interface.
  • This is a breaking change of the library interface.
• Add new 1.0 structs and types
• Support 1.0 blueprints
• Update and add Python examples
• Improve C++/Python interoperability by using shared_ptr as object holder instead of unique_ptr. This avoids data copies, and allows a more natural interaction with objects from the Python side.

Save Game Documentation

• Update for full 1.0 save format
• Add documentation of class specific binary data
• Add documentation of the blueprint file format

Internal

• Many internal code fixes, cleanups and improvements
• Update dependencies

Known Limitations

• The 3D Map editor only can edit existing values. Adding/Removing properties/objects will be added in a future version. (The Python library already supports adding/removing data.)
• Parsing of game files for a more detailed world representation and loading object models is not updated for 1.0/Unreal 5 yet.
• Support for modded save games is limited.