Item Serialization

Memories

Memories are simply serializable representations of Vault Item components that you want to persist.

Anything that is expected to change about your item on a per-instance basis should be saved to a memory using the provided SaveToMemory function in Vault Items. That same data should be pulled from the memory using LoadFromMemory.

This is done this way instead of using the SaveGame specifier because the SaveGame specifier saves a sequence of bytes without any context, thus if you change something about your item (like add or remove a property) your previous saves will no longer work. With the memory structs approach shown here, as long as you refactor your functions acording to the changes made old saves will still work.

Note: If you feel like this approach is too cumbersome you can side step this feature and implement serialization in whatever way works best for you. Also feel free to let me know as I'm always keen to learn about different approaches.

Saving & Loading Items

Below is an example of how to override the SaveToMemory and LoadFromMemory functions to use the serialization system that comes with VaultLogic.

For the basic example of a key those functions would look like this:

Notice the usage of the KeyMemory struct, you can create structs to save the data you need in c++ or blueprints.