I am currently developing a save system where, upon creating and launching a save, the system loads a specific location (or map). In this location, certain information needs to be saved, such as:
- Structures: Whether they are intact or destroyed.
- Player Data: Ongoing tasks and completed tasks.
When the player re-enters the save, I would like the system to restore the state of both the structures and the player data. This is similar to how it works in games like Pokémon, where you save, quit, and resume exactly where you left off.
However, I’m concerned that saving an entire map might not be optimal in terms of performance or storage efficiency. The same applies to saving individual structures. I’m currently researching how games like Pokémon handle this to implement a more efficient solution.
If you have any insights or suggestions on how to optimize this kind of save system, I would greatly appreciate your feedback. In the meantime, I will continue exploring potential solutions.
Best regards,
Lazxr