Post by spiceboy on Dec 31, 2021 1:01:37 GMT
I've been working on a save system for a few weeks now, and I've figured out a lot of the infrastructure necessary. The use of the Unity package "Easy Save 3" has made a lot of this work rather straightforward, and I've gotten to a spot where I can save "most" Unit data, as well as "Scenarios", a data type I've introduced which basically bundles together some cutscenes/conversations with a map, spawn positions, a player controlled party, and enemies.
One aspect I'm struggling with right now is how to handle notifications. I want to be able to save and load in the middle of a battle, which means keeping track of notifications regarding stats, status afflictions, etc.,
I initially thought of just persisting the entire table of notifications, but I believe this is not even possible. While Easy Save 3 has great support for Unity types and quite a few System types as well, it doesn't have support for some of the architecture used like System.Action. I thought of perhaps serializing the Notification Center by reference, but this would involve significantly changing the architecture designed so that it lives within the Scene itself, instead of as a static reference.
I also thought of simply initializing common notifications I know will be in use whenever a load happens, such as the listeners for Stats. However, that doesn't take into account context dependent cases such as status afflictions.
Anyone have any experience building persistence into this framework?
One aspect I'm struggling with right now is how to handle notifications. I want to be able to save and load in the middle of a battle, which means keeping track of notifications regarding stats, status afflictions, etc.,
I initially thought of just persisting the entire table of notifications, but I believe this is not even possible. While Easy Save 3 has great support for Unity types and quite a few System types as well, it doesn't have support for some of the architecture used like System.Action. I thought of perhaps serializing the Notification Center by reference, but this would involve significantly changing the architecture designed so that it lives within the Scene itself, instead of as a static reference.
I also thought of simply initializing common notifications I know will be in use whenever a load happens, such as the listeners for Stats. However, that doesn't take into account context dependent cases such as status afflictions.
Anyone have any experience building persistence into this framework?
