Suggestion Closed · Implemented

Variable Conditions (VariableIsSet, VariableEquals, VariableinRange, etc) do not correctly parse nested placeholders

#4800 opened by Unknown 2 years ago

Unknownreported this suggestion

Sorry about the previous issue - messed up that test case when debugging pretty badly. But this was the main issue I was attempting to debug.

test-conditions-cast:
  Skills:
  - skill{s=test-conditions-exec;id=tester} @self

test-conditions-exec:
  Skills:
  - setvariable{var=caster.<skill.id>;value="hello";type=STRING} @self
  - skill{s=test-conditions-eval} @self
  
test-conditions-eval:
  Conditions:
  - varisset{name=caster.<skill.id>} orelsecast test-conditions-notset
 # - varisset{name=caster.tester} orelsecast test-conditions-notset
  Skills:
  - message{m="Variable set, <caster.var.<skill.id>>"}

test-conditions-notset:
  Skills:
  - message{m="Variable not set, <caster.var.<skill.id>>"}

This will return Variable not set, even though caster.<skill.id> is set. However if instead I check for

  - varisset{name=caster.tester}

which should be equal to

  - varisset{name=caster.<skill.id>} 

I get Variable set.

This is also the case for the other variable placeholders I've tested so far.

Sign in to join the discussion.