minecraft:movement no longer works correctly on the player
Partner Rank:
2
Partner Team Reporting:
Gamemode One
Verification builds and Platforms:
v1.12.0, v1.13.0.1; Windows 10
Regression builds:
Correction: After further investigation, it turns out that v1.12.0 also has the bug in it. In fact, the component works perfectly fine if it's applied every tick (by a loop like the environment sensor) but not if it's only added once. That lead to an incorrect regression build on this report.
Summary:
minecraft:movement no longer works correctly on the player. Upon adding a component group with this component, the player does not receive the modified speed permanently. It seems like the speed gets modified for only a few ticks as the FOV changes for the split of a second.
Impact:
Affects upcoming content
Repro Steps:
- Download the attached BP and apply it to a world
- Join the world and type "/tag @s add show_bug"
- Observe the result
Observed Results:
The player's health permanently changes but the movement speed is not correctly increased.
Expected Results:
The new movement value gets applied correctly and therefor behaves like all other components.