Grant Gryczan


Example: ```ts Advancement('test', { criteria: { a: { trigger: 'minecraft:tick' }, b: { trigger: 'minecraft:tick' } }, requirements: ['a'] }); ``` This should be inferred as `Advancement`, not `Advancement`. Otherwise...


 Documentation: https://minecraft.fandom.com/wiki/Predicate#condition_value_check

The `player` property of any applicable advancement trigger's `conditions` should always accept an `EntityCriterion`, not only an array of predicates.  The `player` property also should not accept a single...

  

This only happens when inputting `MCFunctionInstance`s into `schedule.clear`, not `string`s. And this issue does not apply to `mcFunctionInstance.schedule.clear()` either.   This also happens with `schedule.function`, but only when called...

For example, `mcFunctionTag.values` does not include `MCFunctionInstance` in its element type, even though it works fine in JS runtime. 

Incorrect output with empty `execute` `run` callback

3

```ts MCFunction('test', () => { execute.as('@s').run('something', () => {}); say(1); say(2); say(3); }); ``` outputs ```mcfunction execute as @s run say 1 say 2 say 3 ``` This applies whether...