Uploaded August 2019 | Updated September 2026, 1 hour ago
To give the player's a feeling of progress, that their actions have a meaningful impact in the future of the game, we must have some way to keep the effects of these actions persistent. In this live stream we will talk about three ways to achieve persistent data using some features of #GodotEngine.
Follow me: pigdev.itch.io
Support me: patreon.com/join/pigdev
Link to the project's repository, please read the README file!
github.com/pigdevstudio/save-player-resources
0:00 - Intro
1:00 - The Problem
3:14 - Patrons Thank
4:06 - Players Resource Approach
10:43 - Advantages
13:18 - Saving the PlayerResource to Disk
14:38 - Drawbacks
16:37 - Singleton Approach
22:25 - Advantages
24:12 - Drawbacks
29:30 - Saving to .json File
30:18 - Save and Load methods
32:54 - Advantages
34:12 - Parsing
40:01 - Versioning save files
42:52 - Drawbacks
45:52 - Experiments with type parsing (Skippable)
56:28 - Ending
57:56 - Outro
To give the player's a feeling of progress, that their actions have a meaningful impact in the future of the game, we must have some way to keep the effects of these actions persistent. In this live stream we will talk about three ways to achieve persistent data using some features of #GodotEngine.
Follow me: pigdev.itch.io
Support me: patreon.com/join/pigdev
Link to the project's repository, please read the README file!
github.com/pigdevstudio/save-player-resources
0:00 - Intro
1:00 - The Problem
3:14 - Patrons Thank
4:06 - Players Resource Approach
10:43 - Advantages
13:18 - Saving the PlayerResource to Disk
14:38 - Drawbacks
16:37 - Singleton Approach
22:25 - Advantages
24:12 - Drawbacks
29:30 - Saving to .json File
30:18 - Save and Load methods
32:54 - Advantages
34:12 - Parsing
40:01 - Versioning save files
42:52 - Drawbacks
45:52 - Experiments with type parsing (Skippable)
56:28 - Ending
57:56 - Outro










