When attempting to use experimental queries such as;
query.biome_has_any_tag('tag_name')
query.scoreboard('scoreboard_name')
or any other query that is experimental in the Molang documentation, they break the file they are in.
Update:
When looking at the content log, the following error occurs when using the biome query:
... q.biome_has_any_tag('plains') | unrecognized token: q.biome_has_any_tag('plains')
Expected Behavior:
Experimental queries work as intended and don't break the files they are in
Actual Behavior:
Use of experimental queries breaks files
Steps to Reproduce:
Setup an animation controller or variable that uses an experimental query
Attempt to do something with that query (switch states in a anim_controller, run an animation in a resource file, etc.)
It won't work
Switch the experimental query to something like query.is_sneaking
The files will no longer be broken and will work
Comments 15
query.scoreboard only works in rp only if the scoreboard you're querying is on the sidebar, i believe. (not sure about bp)
I've tried using query.scoreboard in both rp and bp, both return unrecognised token errors, even with the scoreboards on the sidebar. Not to mention that if they were only to work while on the sidebar that would be a bug itself.
I've tried using query.scoreboard in both rp and bp, both return unrecognised token errors, even with the scoreboards on the sidebar. Not to mention that if they were only to work while on the sidebar that would be a bug itself.
This also happened to me too. I have been getting the same error by testing the biome the player is in.
[media]
Here is the Behavior Pack I encountered the error in. Extract it as zip then go to animation_controllers, temperaturetest.json and see the queries.
(Version: v1.16.201)
This also happened to me too. I have been getting the same error by testing the biome the player is in.
[media]
Here is the Behavior Pack I encountered the error in. Extract it as zip then go to animation_controllers, temperaturetest.json and see the queries.
(Version: v1.16.201)
Nevermind. I found out that you only need to enable "Additional modding capabilities" in the world settings. I hope that helps anyone else that has this same issue.
Added error from content log output