Persistent Storage – Ylands
Jump to navigation
Jump to search
No edit summary |
Lou Montana (talk | contribs) m (Lou Montana moved page Ylands Persistent Storage to Ylands:Persistent Storage: Text replacement - "Ylands " to "Ylands:") |
||
(3 intermediate revisions by 2 users not shown) | |||
Line 27: | Line 27: | ||
Image:Ylands-Editor-game storage variables1.png|Storage variables | Image:Ylands-Editor-game storage variables1.png|Storage variables | ||
</gallery> | </gallery> | ||
---- | ---- | ||
{{Ylands | {{Navbox/Ylands}} | ||
{{DEFAULTSORT:{{#sub:{{PAGENAME}}|7}}}} | |||
[[Category: How | [[Category: Script: How To]] |
Latest revision as of 16:28, 16 November 2022
Overview
It is possible to store custom data for any player across different instances of one custom game. This means, that when payers will disconnect from one game instance (i.e server) and will reconnect to another one, it is possible to store and retrieve data between those game sessions. For example, creator can store record of achievements gained by the player while playing the game.
- Storage data are always unique to a specific player (similar as entity storage)
- Storage data can be updated only if owning player is online
Add new variable to storage
- Navigate editor menu -> game settings and open Game storage
- Use "Add new variable" button to add new variable to storage
- Set variable name, type and default value
- Important
- Pay attention to variable type setting, this cannot be changed later!
- New variable is committed to Game storage right after variable settings are confirmed
- Once committed, storage variables cannot be deleted, only marked as "obsolete" (to assure continuous game compatibility)
Using storage variables
- Once declared, storage variables will become available in Visual scripting under Variables -> Game category
- Game storage variables can be used in same way as entity storage variables, but in this case the owner always have to be a player