I know what you’re thinking, “There’s already guides to this!”, but this is different! I’m explaining how a save file works, because anytime someone wants to make a save code system, they can’t understand it half the time. This guide will be good to help newbies understand the concept of a save file. Now that I’ve said that, let’s get started!
What we call as the community of Gimkit, a “save code”, is not really a save code. To explain what I mean, let’s split this into two sections real quick!
Thank you! That’s a lot better! ‘under his breath’ Here’s your payment, now scram!
Anyways, in this first section, we’ll talk about the export. The export’s role in this is not to save the game, it’s to give the player the save code before they leave the game. When exporting, we use block code to turn data into digits, which then makes up the save code. Not that hard to understand, right? Let’s move on!
What the Import’s role in this is converting those same digits into data. We use block code to do this. Before the block code activates, the player has to put in a code by use of counters and buttons, or anything you can put digits in. The counters update the properties or items. When the player finishes entering in the save code, block code turns those digits back into data, by use of block code. It’s that simple!
In summary, we’re not technically saving the game, we’re just using a “save” code to bring back the progress the player wants so he can continue his journey on a game.
Again, before I end this topic, this is for newbies. How useful do you think this guide is?
- 5 Amazing! Really useful on the forums!
- 4 It’s pretty good!
- 3 It’s decent I guess.
- 2 It’s needs work.
- 1 This guide is the worst!