Sorry, I have another question. I’ve noticed that USavior3::WriteSlotToFile empties the content of the slot instance data (it calls e.g. SlotData->Complex.Empty()). So it seems I can’t hold a slot instance in memory after I’ve written it to a file, I’d have to re-load it using ReadSlotFromFile if I want to continue to add to it. This makes it a bit more difficult to build up a combined save state in memory - although the Copy node would allow me to copy it out I guess.
What’s the reason for WriteSlotToFile deleting all the data in the slot instance? I’d prefer to have the choice of keeping that instance in memory if I wanted, or destroying it if I wanted the memory back.
[Edit]This is complicated by the fact that some things automatically call WriteSlotToFile so I have to be careful about what order I try to update the slot instance, because rather unintuitively it’ll lose all its data after certain calls I think?