android studio tutorial save information in states

Similarly loading can take a moment to finish, and triggers On load complete when done. Once saving has completed, the System trigger On save complete triggers. Saving can take a moment to complete, and the game keeps running in the mean time. Appropriate use of the No Save behavior can also help make savegames smaller (see below). Offering a limited number of save slots is a good way to ensure you never hit the limit. This is unlikely to be a problem for most games, but if you have a huge number of separate save slots you might hit the storage limit. Note that most browsers have a limit on how much data a web page can save to disk.

You could offer the player a set of slots to save to, or allow them to enter their own savegame names.

Each slot is like a separate file that stores a different save. It's often useful to allow players to have multiple savegames. Savegames don't go there (luckily), they are stored in either WebStorage or IndexedDB, which are permanent storages and are not affected by the user clearing their cache. The browser cache is a very much temporary storage that is used to save things like images on web pages without having to re-download them every time, and it's regularly cleared. For example, Firefox and Chrome will store savegames separately if a player saves a game while using Chrome, then switches to Firefox, they will not be able to load that savegame. Note however savegames are associated with the specific browser. This means players can switch off their computer or device, come back the next day, and the savegame can still be successfully loaded.

Savegames are stored on disk by the browser. For mobile games you'll obviously need to make a touchable button somewhere instead, but to keep things simple we'll focus on a desktop game.

Android studio tutorial save information in states