mojira.dev
MC-76044

randomTickSpeed, spawnRadius, maxEntityCramming and maxCommandChainLength accept non-integer value

Resolved
Fixed
4

The bug

You can set any value for gamerules like randomTickSpeed, spawnRadius or maxEntityCramming which store numbers, but the command feedback is always "Game rule [GAME_RULE_NAME] has been updated to [VALUE]", even if the provided value is not a number. The expected behavior is that an error message appears just like it is for the gamerules which store boolean values when trying to set a non-boolean value.

How to reproduce

Use the following command

/gamerule randomTickSpeed text

→ The feedback "Game rule randomTickSpeed has been updated to text" appears

Comments 9

Confirmed.

Isn't it just bad lag? The graphics seem ok, but the game is actually lagging.

Nvm thinking of different issue

Confirmed for

  • 1.8.3 /gamerule randomTickSpeed accepts any value, while it should only accept values equal or greater than 0

Confirmed for 15w31a snapshot.

I did /gamerule randomTickSpeed over 9000 then /gamerule randomTickSpeed

[media]

Confirmed for

  • 16w05b

The enviroment is supposed to contain pc details.

Also for spawnRadius and maxEntityCramming

A fix for this might fit nicely with the change to tab-completion of functions in the gameLoopFunction gamerule

yuval gat

(Unassigned)

Confirmed

/gamerule, command, gamerule, integer, maxCommandChainLength, maxEntityCramming, number, randomTickSpeed, spawnRadius

Minecraft 1.8.2-pre1, Minecraft 1.8.3, Minecraft 1.8.9, Minecraft 16w05b, Minecraft 1.10.2, ..., Minecraft 1.11.2, Minecraft 17w06a, Minecraft 1.12 Pre-Release 6, Minecraft 1.12.1, Minecraft 1.12.2

Minecraft 17w46a

Retrieved