Variables: persistent per-player data
Player data is managed through Actions and Conditions. The reviewed Core does not expose a general resources/variables/ loader analogous to Items. Do not create a file there expecting a variable definition to load.
Basic: add points
Create plugins/Obsidrel/resources/actions/points.yml:
earn_point:
enabled: true
steps:
add:
type: VAR_ADD
variable: points
amount: 1
notice:
type: MESSAGE
message: '<green>Points: {var:points}</green>'
Invoke the Action through a Trigger or UI button.
Advanced: gate by amount
Create plugins/Obsidrel/resources/conditions/points.yml:
has_points:
enabled: true
type: VARIABLE
variable: points
operator: '>='
value: 10
message: '<red>10 points required.</red>
Attach conditions: [has_points] to a protected Action.
Other verified operations
- Actions:
VAR_SET,VAR_ADD,VAR_REMOVE,VAR_RESET,FLAG_SET,FLAG_TOGGLE,TIMER_START. - Conditions:
VARIABLE,FLAG,TIMER. - Text expressions:
{var:points},{flag:has_ruby_key},{timer:ruby_timer}. - Timer Actions accept
duration, e.g.30s.
Verify isolation between two players and persistence across reconnect/restart. Actions · Conditions.