-
Bug
-
Resolution: Unresolved
-
None
-
1.15.2, 20w11a, 20w12a, 20w14a, 20w16a, 20w17a, 20w18a, 20w20b, 1.16 Pre-release 5, 1.16.1, 1.16.2 Pre-release 1, 1.16.2, 1.16.3, 1.16.4 Pre-release 1, 1.16.4, 20w45a, 20w46a, 20w48a, 20w49a, 20w51a, 21w03a, 1.16.5, 21w10a, 21w11a, 21w13a, 21w15a, 21w16a, 21w19a, 1.17 Pre-release 1, 1.17, 1.17.1, 21w37a, 1.18.1, 1.19, 1.19.1, 1.19.2, 1.19.3 Release Candidate 1, 1.19.3, 23w03a, 1.19.4, 23w18a, 1.20.2, 23w42a, 24w33a, 1.21.1, 25w03a
-
None
-
Confirmed
-
Commands
The bug
/gamerule rule <value> succeeds even though <value> equals the current value. This behavior is inconsistent with other commands: /bossbar, /team, and /data.
How to reproduce
/gamerule maxCommandChainLength 2
→
Gamerule maxCommandChainLength is now set to: 2/gamerule maxCommandChainLength 2
→
Gamerule maxCommandChainLength is now set to: 2
