ENUM

SaveManagementStrategy

Strategies used to manage save data.

  • enum SaveManagementStrategy {
  • # No strategy is used to manage saves. In other words, no saves are persisted.
  • NONE
  • # Only one copy of the initial save is kept, which is replaced by new saves.
  • # Best for extremely large and irregular (random) save files, but loses the
  • # ability to restore a previous save.
  • REPLACE
  • # A full copy of the save contents are kept on the creation of each new save.
  • # Best for small save files that don't take up a lot of space.
  • COPY
  • # A diff is created from the initial save of the ISaveProfile.
  • # If no initial save exists, then the behaviour for the initial save only is
  • # the same as Copy.
  • #
  • # Best for fixed-size, larger save files that are still reasonable in size to
  • # calculate
  • # a diff based on the initial save for. Calculating the diff will incur a
  • # CPU time cost.
  • DIFF
  • }