Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 81
    • Issues 81
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • dulst
  • core
  • Wiki
  • Save

Last edited by Kaoru Aoi Jan 18, 2019
Page history

Save

You can save long-term data to a player's library through the save action in the effect builder. It is great for creating game modes where the player's progress carries on through multiple matches. Example modes: singleplayer Rogue-like modes, multiplayer arena or battle royale modes.

To save arbitrary data to the player's library, first set the player's save property to the data that you want to save. Running the save action will then save it to the library.

To easily set the data into the save property, use the set data to player action that comes with most templates, it makes the process trivial.

Accessing save data

The saved data is accessible on every subsequent match by selecting the player through the effect builder. It is in the data property of the player. You can access it by using the dot syntax. Check it out in console with dulst.view('player1')

Clone repository
  • Analytics Events
  • Animations
  • Basic Effect Building
  • Change Log v13
  • Change Log v14
  • Change Log v15
  • Change Log v16.1
  • Change Log v16.2
  • Change Log v16.3
  • Change Log v16.4
  • Change Log v16.5
  • Change Log v16.6
  • Change Log v16.7
  • Change Log v16.8
  • Change Log v16
View All Pages