Saving and loading a game is something that any game should have by default these days. But after all these years, we still don’t have a universal way of saving data and each game uses different methods for storing and loading their info. This is pretty much normal, since the way we store the data depends on the type of game you’re making and how you’re making it.
For us, Afterloop is all about zero loading times, and choosing a format like XML and JSON for saving was out of question due to their slow parsing speeds.
We started with binary serialization, but soon enough we had problems making saves backwards compatible, we needed SPEED and FLEXIBILITY. Flatbuffers had everything we needed.
In this post, I’ll explain how we used flatbuffers for saving and loading data in Unity.
Flatbuffers might seem scary and mysterious at first, but in reality it’s not that hard to use !
Obviously, this is not something that beginners should use but since I couldn’t find any examples of flatbuffers with Unity3D on the web, I had to make this post.
We’re proud to present PR8, our little hero of AfterLoop.
PR8 is an utility robot, 8th generation of Progress Ready series. This little fellow is stuck in an endlessly shifting maze, and has lost contact of outside world since 1960s.
The maze is like a loop, your goal will be to help PR8 explore this massive maze containing over hundreds of different puzzles, and get it out.
As you may know, we are currently working on ROTE Revolution, which is a 3D game with an Isometric camera and a top down view. In this new version we decided to add 3d elements and sceneries to our puzzle. That idea looked cool, but little did we know that we were running straight into a wall.
Here are some tips for you, in order to avoid having the same issues as we encountered, and also how to improve the look of your game!