CyclopsMC / IntegratedScripting / 33627544083

50%

master-26-lts: 51%

Pull #70

github

Translate script values back to NBT when an operator expects NBT

Only compound tags keep their type when they are translated to a script:
all other tags become plain script values, and an absent NBT value becomes
null. Passing such a value to an operator again therefore failed, because
it was translated back to the value type it looked like. A list tag that
came out of an NBT path filter expression came back as a list, so
nbtAsTagList(idContext.ops.stringNbtPathMatchFirst(...)) failed with a
wrong type error instead of listing the matches, and null values did not
translate at all.

Operator arguments are now translated against the value type the operator
expects for them, so script values reaching an NBT input are converted to
NBT, and null becomes an absent NBT value.

Related to #67

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JCW1HmWhLT27jh57t9d7B6

302 of 852 branches covered (35.45%)

Branch coverage included in aggregate %.

1412 of 2582 relevant lines covered (54.69%)

19.92 hits per line