Game logic - Game logic storage – Ylands

From Bohemia Interactive Community
Jump to navigation Jump to search
No edit summary
m (Text replacement - "{{DEFAULTSORT:{{#sub:{{PAGENAME}}|19}}}}" to "{{DEFAULTSORT:{{#sub:{{PAGENAME}}|13}}}}")
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
=Description=
=Description=
Special game logic to store data specific to another game logic. When assigned trough instruction [[Ylands Tile - Add-Remove logic storage|'''Add logic storage''']], it will create a '''copy''' witch will be '''attached''' to selected game logic '''instance'''.
Special game logic to store data specific to another game logic. When assigned trough instruction [[Ylands:Tile - Add-Remove logic storage|'''Add logic storage''']], it will create a '''copy''' witch will be '''attached''' to selected game logic '''instance'''.


*Storage has to be attached to entity via '''Add Storage''' instruction, target becomes [[Ylands Tile - Storage owner literal|'''storage owner''']]
*Storage has to be attached to entity via '''Add Storage''' instruction, target becomes [[Ylands:Tile - Storage owner literal|'''storage owner''']]
*Any storage can have unlimited number of owners, each owner will have its unique copy of attached storage
*Any storage can have unlimited number of owners, each owner will have its unique copy of attached storage
*Game logic can have unlimited number of storages
*Game logic can have unlimited number of storages
Line 17: Line 17:
*In case of multiple instances of same composition, references in all compositions will be set to one storage
*In case of multiple instances of same composition, references in all compositions will be set to one storage


=Notes=
= Notes =
*In case a script will try to access non-existent storage this will stop the script. So it is crucial to do a storage check using [[Ylands Tile - Has logic storage|'''Has storage''']] instruction before accessing storage on unknown entity  (e.g Trigger object).
*In case a script will try to access non-existent storage this will stop the script. So it is crucial to do a storage check using [[Ylands:Tile - Has logic storage|'''Has storage''']] instruction before accessing storage on unknown entity  (e.g Trigger object).


=Related Instructions=
= Related Instructions =
*[[Ylands Tile - Add-Remove logic storage|Add / Remove Logic Storage]]
*[[Ylands:Tile - Add-Remove logic storage|Add / Remove Logic Storage]]
*[[Ylands Tile - Has logic storage|Has Logic Storage]]
*[[Ylands:Tile - Has logic storage|Has Logic Storage]]




----
----
{{Ylands scripting navbox}}
{{Navbox/Ylands}}
{{DEFAULTSORT:{{#sub:{{PAGENAME}}|19}}}}
{{DEFAULTSORT:{{#sub:{{PAGENAME}}|13}}}}


[[Category: Ylands 0.12]]
[[Category: Ylands 0.12]]
[[Category: Game Logic]]
[[Category: Game Logic]]

Latest revision as of 14:21, 24 November 2023

Description

Special game logic to store data specific to another game logic. When assigned trough instruction Add logic storage, it will create a copy witch will be attached to selected game logic instance.

  • Storage has to be attached to entity via Add Storage instruction, target becomes storage owner
  • Any storage can have unlimited number of owners, each owner will have its unique copy of attached storage
  • Game logic can have unlimited number of storages
  • Each owner will have unique values in each storage
  • Storage data (variables) can be found in Variables category
  • Storage instructions can be found in Instructions category

Custom instructions

  • Instructions in a storage are executed only within currently called storage instance and it will affect only variables of this instance.

Storages in compositions

  • When composition using any storage will get exported, it will save with a copy of that storage (even if not selected)
  • When such composition is placed in other scenario, it will make new independent copy of included storage under new name (e.g Entity storage (2))
  • In case of multiple instances of same composition, references in all compositions will be set to one storage

Notes

  • In case a script will try to access non-existent storage this will stop the script. So it is crucial to do a storage check using Has storage instruction before accessing storage on unknown entity (e.g Trigger object).

Related Instructions


Ylands - Editor
Editor

Animated objects, Custom UI, Entity welding, Game export, Game ID, Monetization, MIDI music, Optimizations, Common Problems, FAQ

Script

Introduction, Conventions, Client script, Text scripting, Custom controls, Custom controller, Storage Data, Game set, Leaderboards, Matchmaking, Map markers

Game logic

AI Behaviour, Ask Player, Controller, Custom Camera, Custom Controls, Custom HUD, Custom Window, Data Set, Dialogue, Entity Label, Entity Storage, Entity Template, Environment, Event Listener, Game Logic Label, Game Logic Storage, Game Logic Template, Global Storage, Group Template, Image Library, Impassable Barrier, Light, Melee Attack Effect, Particle Effect, Particle Template, Path, Play Area, Player Role, Player Team, Position Animator, Post Process, Reference Point, Resource, Rotation Animator, Script Module, Skill, Sound Effect, Spawn Point, Time Trigger, Transaction, Trigger Zone, Voice Chat Channel, Water Volume

Script tiles

Game, Entities, Game Logic, Logic, Loops, Instructions, Number, Vector, Color, String, Array

Misc

WIKI FAQ

Retrieved from "https://community.bistudio.com/wiki?title=Ylands:Game_logic_-_Game_logic_storage&oldid=350128"