-
Bug
-
Resolution: Unresolved
-
None
-
1.16.1, 20w30a, 1.16.2 Pre-release 1, 1.16.2 Pre-release 2, 1.16.2 Pre-release 3, 1.16.2 Release Candidate 1, 1.16.2 Release Candidate 2, 1.16.2, 1.16.3 Release Candidate 1, 1.16.3, 1.16.4 Pre-release 1, 1.16.4 Pre-release 2, 1.16.4 Release Candidate 1, 1.16.4, 20w45a, 20w46a, 20w48a, 20w49a, 20w51a, 21w03a, 1.16.5 Release Candidate 1, 1.16.5, 21w05a, 21w05b, 21w06a, 21w07a, 21w08a, 21w08b, 21w10a, 21w11a, 21w13a, 21w14a, 21w15a, 21w16a, 21w17a, 21w18a, 21w19a, 21w20a, 1.17 Pre-release 1, 1.17 Pre-release 4, 1.17 Release Candidate 1, 1.17 Release Candidate 2, 1.17, 1.17.1 Pre-release 1, 1.17.1, 21w39a, 21w41a, 21w42a, 1.18.1, 22w05a, 1.18.2, 1.19 Pre-release 1, 1.19, 1.19.2, 1.19.3, 23w07a, 1.19.4, 23w14a, 1.20.1
-
Confirmed
-
Commands, Player, Save Data
-
Low
-
Platform
The bug
Although MC-179851 is fixed, the base of the generic.movement_speed attribute when set for players is reset to the default value after relogging the world.
How to reproduce
- Use the following command to give faster movement speed to the player:
/attribute @s minecraft:generic.movement_speed base set 0.2
- Observe the movement speed of the player after relogging the world
→
The base is reset to the default value
Workaround
A workaround for the bug would be to use attribute modifiers instead of setting the attribute base:
/attribute @s minecraft:generic.movement_speed modifier add 0-0-0-0-0 generic.movement_speed 1 multiply
