Training Livestream - Saving and Loading - June 6 - Live from Epic HQ

[DizzyWes]

@Raildex_;720620

I was very disappointed by the Stream

In the Stream Wes used a variable “Door Unlocked” and accessed it within a Door Blueprint.
Guess what? If you place another door in the level, it won’t work anymore or to be more precise: Both doors would be loaded the way first door was saved.
Not to mention that the door accesses the game mode. I find this a bad design.
The GameMode or the GameInstace should decide what properties should be loaded and access the actors in the world. not the other way round. (This is my opinion. I find it weird to access GameInstance/Mode in every Blueprint I want to save)
It won’t work with a different map either. Wes answered my question “How to save dynamically spawned actors” with “Save the array in the GameMode”.
But this won’t work either since the Actors may be of a different Type. You would need to save the type-specific data and the actor-data separately.
Having two separate arrays is not a good practice.

Sorry you didn’t find this stream useful, we can do a more advanced version next time. This was meant as an intro to Saving and Loading and the examples I cited were one off examples meant to be used as a place to start. The way I would approach saving/loading content would vary based on the project and type of data I’m working with. I might expand the usage of my struct to include all the things I want to save (object type references, numerical values, transform information, etc) or might work with data tables instead if I’m working with large quantities of information.