Hello people,
I’ve written a tutorial dealing with the much-expected saving and loading functionality of any game. I’ve taken the .NET/Mono serialization approach which I’m using to build my RPG Fantasy game, and I think this could be useful to anybody looking for some guidelines.
I haven’t gotten much feedback on my previous article which I also posted here, dealing with cross-scene saving of objects and data, but I’m hoping I did a better job here 
Let me know what do you think!
Just took a quick overview, and it looks pretty decent. Going to do a more in dept read tomorrow. Cheers.
Finally someone has lifted the clouds on saving for me.
Everywhere else just mentions playerperfs all the time.
Thank you so much for this, will read through and follow this and your other tutorial later this week.
Will give you a heads up how I get on.
Thanks again
Thanks for the tutorial.
I found the first part very interesting as an approach for carrying things across scene barriers.
What I’m curious about is: How scaleable is the second part? Wouldn’t you need to hard code everything that is being saved? Couldn’t each scene need different things saved?
I could imagine a situation where you would want to place an object and mark it as “saveable”, and then have the system find it and save it.
That being said, it’s a good introduction into serialisation and saving data.
Thanks!