namsic
- namsic
- JIRAUSER472700
- Europe/Stockholm
- Yes
- No
MCPE-72795
This query has been fixed
When the Runtime Identifier is set to a projection such as minecraft:arrow or minecraft:snowball, rotating the model on the add-on to the y-axis (using tp command) does not rotate normally.
However, when set to minecraft:armor_stand, it rotates normally on the y-axis.
Expected Behavior:
- The rendered model's y-axis rotation follows real y-axis rotation
Actual Behavior:
- The rendered model's y-axis rotation does not change
Steps to reproduce:
- Add an entity whose runtime identifier is minecraft:arrow
- Register an animation controller with a command for the entity to rotate on the y-axis
- Summon the entity
Test Files
- Video: https://drive.google.com/file/d/1aba6nBQiR0-2n9g81aV3NcOzAgfcdWc1/view?usp=sharing
- Addon: https://drive.google.com/file/d/1XgGW4uk9m8MyXrXwFR9oMpznjhDkIK41/view?usp=sharing
How To Test
- Make a world with this test addon
- /function init
- Type "/function test/start" while turning your head
- Keep an eye on the summoned entity.
Suppose you have three files
File 1 only exports variables
In File 2 and File 3, you can change the values of the variables and print them out respectivelyIf you change the value of a variable in file 2, the output of file 2 is normal, but file 3 still does not change the value of that variable
Conversely, if you change the value of a variable in file 3, the output of file 3 is normal, but file 2 still has the value you changed previouslyExpected Behavior:
- Exported variables share values
Actual Behavior:
- Exported variables are not shared
How to Test:
1. Apply pack and create world
2. Follow the steps below to chat (ignore the instructions in parentheses)
- 1 (Set the value of variable 1 to 1 in file 2)
- print (Print the values of the variables in file 2)
- print2 (Prints values of variables from file 3)
- 13 (Set the value of variable 1 to 3 in file 3)
- print (same as described above)
- print2 (same as described above)
3. If you checked the bug in the chat above, change the number and check other kinds of variablesTest File:
Suppose you have three files
File 1 only exports variables
In File 2 and File 3, you can change the values of the variables and print them out respectivelyIf you change the value of a variable in file 2, the output of file 2 is normal, but file 3 still does not change the value of that variable
Conversely, if you change the value of a variable in file 3, the output of file 3 is normal, but file 2 still has the value you changed previouslyExpected Behavior:
- Exported variables share values
Actual Behavior:
- Exported variables are not shared
How to Test:
1. Apply pack and create world
2. Follow the steps below to chat (ignore the instructions in parentheses)
- 1 (Set the value of variable 1 to 1 in file 2)
- print (Print the values of the variables in file 2)
- print2 (Prints values of variables from file 3)
- 13 (Set the value of variable 1 to 3 in file 3)
- print (same as described above)
- print2 (same as described above)
3. If you checked the bug in the chat above, change the number and check other kinds of variables
Test File:
Minecraft Script:
Other JS Test Site:
Steps to reproduce
- Just console.warn(NaN === 1);*
Minecraft Script:
Other JS Test Site:
Steps to reproduce
Just console.warn(NaN === 1);*
Minecraft Script:
Other JS Test Site:
Steps to reproduce
Just console.warn(NaN === 1);
*Minecraft Script:
Other JS Test Site:
Steps to reproduce
Just console.warn(NaN === 1); // Not only 1 but all numbers are possible
query.health is a useful query, but with these bugs it would be difficult to use fluidly.
I uploaded test files (I tested it in Minecraft Preview, but release version also makes this bug)
This bug has a huge impact on creating content. It's a bug that existed since a long time ago, but I thought it should be fixed now, so I posted it like this
When will it be fixed...
And I always check this bug in the beta version and add it to the affected version
I tested number, string, object, list, map, array
All this variables didn't change
So this is bug
setVelocity function does not apply to custom entity either