-
Bug
-
Resolution: Duplicate
-
None
-
Minecraft 1.6.2
-
OS: Windows 7 64-bit SP1; Java: Version 7 Update 25;
CPU: Intel Core i5; RAM installed: 4.00 GB
-
Unconfirmed
Overview: There's actually a series of bugs while using the /effect command in singleplayer (cheats-enabled) mode. According to Minecraft Wiki, the duration is counted in seconds and shall not exceed 1,000,000, but in practice the status effects will actually last for an unexpected length of time. It seems that for different effects, the timing is treated differently as well.
Problems:
- Using effects No. 1-22:
- Using effect No. 23 (Saturation):
- The number of seconds is inconsistent with your command for ANY durations set.
e.g. Saturation for 1639 seconds (=27m19s) returns as around 1m21s
e.g. Saturation for 100 seconds (=1m40s) returns as around 4 seconds
e.g. Saturation for 20000 seconds (=5h33m20s) returns as around 16m38s
- If the duration is set to at least 32767, the timer freezes as well.
e.g. Saturation for 32766 seconds (=9h6m6s) returns as around 27m17s
e.g. Saturation for 32767 seconds (=9h6m7s) returns as infinite duration.
- The number of seconds is inconsistent with your command for ANY durations set.
- duplicates
-
MC-19648 The "/effect" command sets time for instant effects to ticks and not to seconds
- Reopened