You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having a way to use tables for variables could be a good thing. Case example : a quest requires to use a wand on 20 squirrels. We can't be sure the player isn't using the wand on the same squirrel 20 times. We could use 19 variables to store GUIDs and check each previous variable, but that would be a mess. Being able to add to a table and check it cleanly could help.
This would probably need :
Effects to interact with a table : add, clear - remove, shuffle/sort ?
Access to the table elements : ${example.i} to access the i-th element of the "example" table would be consistent with access to event arguments.
Conditions on the table : is X in the table, how many elements in the table ?
The text was updated successfully, but these errors were encountered:
Having a way to use tables for variables could be a good thing. Case example : a quest requires to use a wand on 20 squirrels. We can't be sure the player isn't using the wand on the same squirrel 20 times. We could use 19 variables to store GUIDs and check each previous variable, but that would be a mess. Being able to add to a table and check it cleanly could help.
This would probably need :
The text was updated successfully, but these errors were encountered: