-
Bug
-
Resolution: Incomplete
-
None
-
1.16.201 Hotfix
-
None
-
Unconfirmed
-
Windows
For example, use the following animation_controller.
The interval before "/say on_exit" is too long.
There is no "animations" in "test_state" and the transition is "1" already, but the state still exits too late.
If "on_entry" is "/setblock ~ ~ ~ grass" and "on_exit" is "/setblock ~ ~ ~ air", which means grass will disappear immediately, but the player is moving, the position where the second command be executed could be wrong.
Don't tell me
"on_entry": ["/setblock ~ ~ ~ grass", "/setblock ~ ~ ~ air"]
because it doesn't work in my case! That's another bug I'm about to report. MCPE-116447
{
"format_version": "1.10.0",
"animation_controllers": {
"controller.animation.player.__example__": {
"initial_state": "default",
"states": {
"default": {
"transitions": [
{
"test_state": "query.is_sneaking"
}
]
},
"test_state": {
"on_entry": [
"/say on_entry"
],
"on_exit": [
"/say on_exit"
],
"transitions": [
{
"default": "1"
}
]
}
}
}
}
}
