AlexIIL
- AlexIIL
- alexiil
- Europe/London
- Yes
- No
Minecraft launcher 1.6.84-j, (Unknown Java version, I assume it's the one that's shipped with the launcher).
Minecraft launcher 1.6.84-j
In 1.11.2 the enchantment GUI's book animation opened and closed smoothly, at the the same framerate as the game was running. In 1.12.2 (and in snapshot 17w45a) the animation jumps between positions, staying in a single one for a few frames.
From the equivalent forge code (1.12.2, MCP data version "snapshot_20170629") it appears that minecraft calls GuiScreen.drawScreen with a parameter for "partialTicks" with "Minecraft.getTickLength()" rather than "Minecraft.getRenderPartialTicks()". (The former is the amount of time, in ticks, from when the last frame was rendered, the latter is the amount of time, in ticks, since the last tick). Note that this
issueis reproducible without forge, so it is not caused by a broken forge patch,it is just muchmore obvious in modded GUI's that have larger animated elements than the enchanting table.In 1.11.2 the enchantment GUI's book animation opened and closed smoothly, at the the same framerate as the game was running. In 1.12.2 (and in snapshot 17w45a) the animation jumps between positions, staying in a single one for a few frames.
From the equivalent forge code (1.12.2, MCP data version "snapshot_20170629") it appears that minecraft calls GuiScreen.drawScreen with a parameter for "partialTicks" with "Minecraft.getTickLength()" rather than "Minecraft.getRenderPartialTicks()". (The former is the amount of time, in ticks, from when the last frame was rendered, the latter is the amount of time, in ticks, since the last tick). Note that this is reproducible without forge, so it is not caused by a broken forge patch, but it is more obvious in modded GUI's that have larger animated elements than the enchanting table.
Description
While a campfire is burning items (for example it's both lit and there's 1-4 raw beef placed on it) minecraft attempts to save the chunks it's in every tick - however this is noticeable as an increase to tick times. Placing multiple campfires in the same chunk doesn't increase tick times at all.
Reproduction
- Create a new "superflat" world
- Ensure no mobs are present by running the commands: "/gamerule doMobSpawning false" once, and "/kill @e[type=!player]" twice
- Open the "Profiling debug screen" with "Alt+F3". It should show average tick times (bottom right corner) of about 1ms.
- Locate chunk boundries with "F3+G"
- Place 4 campfires down at the corner (see screenshot 01)
- Add 1 Raw Beef to each campfire
- Tick times should have increased appreciably. (Alternatively using a tool like "iotop" should show increased IO)
Modder Information
This bug was reproduced without mods. However looking at decompiled code shows that, every tick, minecraft now attempts to save up to 20 chunks that have been modified by almost anything (block modifications, block entity "setChanged" calls (which includes inventory modification like hoppers and brewing stand recipe completion))
Description
While a campfire is burning items (for example it's both lit and there's 1-4 raw beef placed on it) minecraft attempts to save the chunks it's in every tick - however this is noticeable as an increase to tick times. Placing multiple campfires in the same chunk doesn't increase tick times at all.
Reproduction
- Create a new "superflat" world
- Ensure no mobs are present by running the commands: "/gamerule doMobSpawning false" once, and "/kill @e[type=!player]" twice
- Open the "Profiling debug screen" with "Alt+F3". It should show average tick times (bottom right corner) of about 1ms.
- Locate chunk boundries with "F3+G"
- Place 4 campfires down at the corner (see screenshot 01)
- Add 1 Raw Beef to each campfire
- Tick times should have increased appreciably. (Alternatively using a tool like "iotop" should show increased IO)
Modder Information
This bug was reproduced without mods - in an unmodified client, launched by the official launcher. However looking at decompiled code shows that, every tick, minecraft now attempts to save up to 20 chunks that have been modified by almost anything (block modifications, block entity "setChanged" calls (which includes inventory modification like hoppers and brewing stand recipe completion))
Description
While a campfire is burning items (for example it's both lit and there's 1-4 raw beef placed on it) minecraft attempts to save the chunks it's in every tick - however this is noticeable as an increase to tick times. Placing multiple campfires in the same chunk doesn't increase tick times at all.
Reproduction
- Create a new "superflat" world
- Ensure no mobs are present by running the commands: "/gamerule doMobSpawning false" once, and "/kill @e[type=!player]" twice
- Open the "Profiling debug screen" with "Alt+F3". It should show average tick times (bottom right corner) of about 1ms.
- Locate chunk boundries with "F3+G"
- Place 4 campfires down at the corner (see screenshot 01)
- Add 1 Raw Beef to each campfire
- Tick times should have increased appreciably. (Alternatively using a tool like "iotop" should show increased IO)
Modder Information
This bug was reproduced without mods - in an unmodified client, launched by the official launcher. However looking at decompiled code shows that, every tick, minecraft now attempts to save up to 20 chunks that have been modified by almost anything (block modifications, block entity "setChanged" calls (which includes inventory modification like hoppers and brewing stand recipe completion))Description
While a campfire is burning items (for example it's both lit and there's 1-4 raw beef placed on it) minecraft attempts to save the chunks it's in every tick (which causes constant disk writing) - however this is noticeable as an increase to tick times. Placing multiple campfires in the same chunk doesn't increase tick times at all.
Reproduction
- Create a new "superflat" world
- Ensure no mobs are present by running the commands: "/gamerule doMobSpawning false" once, and "/kill @e[type=!player]" twice
- Open the "Profiling debug screen" with "Alt+F3". It should show average tick times (bottom right corner) of about 1ms.
- Locate chunk boundries with "F3+G"
- Place 4 campfires down at the corner (see screenshot 01)
- Add 1 Raw Beef to each campfire
- Tick times should have increased appreciably. (Alternatively using a tool like "iotop" should show increased IO)
Modder Information
This bug was reproduced without mods - in an unmodified client, launched by the official launcher. However looking at decompiled code shows that, every tick, minecraft now attempts to save up to 20 chunks that have been modified by almost anything (block modifications, block entity "setChanged" calls (which includes inventory modification like hoppers and brewing stand recipe completion))
Description
While a campfire is burning items (for example it's both lit and there's 1-4 raw beef placed on it) minecraft attempts to save the chunks it's in every tick (which causes constant disk writing) - however this is noticeable as an increase to tick times. Placing multiple campfires in the same chunk doesn't increase tick times at all.
Reproduction
- Create a new "superflat" world
- Ensure no mobs are present by running the commands: "/gamerule doMobSpawning false" once, and "/kill @e[type=!player]" twice
- Open the "Profiling debug screen" with "Alt+F3". It should show average tick times (bottom right corner) of about 1ms.
- Locate chunk boundries with "F3+G"
- Place 4 campfires down at the corner (see screenshot 01)
- Add 1 Raw Beef to each campfire
- Tick times should have increased appreciably. (Alternatively using a tool like "iotop" should show increased IO)
- Placing additional campfires in other chunks and adding raw beef to them should also increase tick times. (see screenshot 03)
- Waiting a minute for all campfires to finish cooking should result in tick times (and disk writes) returning to the previous values (1ms ticks, no disk activity)
Modder Information
This bug was reproduced without mods - in an unmodified client, launched by the official launcher. However looking at decompiled code shows that, every tick, minecraft now attempts to save up to 20 chunks that have been modified by almost anything (block modifications, block entity "setChanged" calls (which includes inventory modification like hoppers and brewing stand recipe completion))
Description
While a campfire is burning items (for example it's both lit and there's 1-4 raw beef placed on it) minecraft attempts to save the chunks it's in every tick (which causes constant disk writing) - however this is noticeable as an increase to tick times. Placing multiple campfires in the same chunk doesn't increase tick times at all.
Reproduction
- Create a new "superflat" world
- Ensure no mobs are present by running the commands: "/gamerule doMobSpawning false" once, and "/kill @e[type=!player]" twice
- Open the "Profiling debug screen" with "Alt+F3". It should show average tick times (bottom right corner) of about 1ms.
- Locate chunk boundries with "F3+G"
- Place 4 campfires down at the corner (see screenshot 01)
- Add 1 Raw Beef to each campfire
- Tick times should have increased appreciably. (Alternatively using a tool like "iotop" should show increased IO)
- Placing additional campfires in other chunks and adding raw beef to them should also increase tick times. (see screenshot 03)
- Waiting a minute for all campfires to finish cooking should result in tick times (and disk writes) returning to the previous values (1ms ticks, no disk activity)
Modder Information
This bug was reproduced without mods - in an unmodified client, launched by the official launcher. However looking at decompiled code shows that, every tick, minecraft now attempts to save up to 20 chunks that have been modified by almost anything (block modifications, block entity "setChanged" calls (which includes inventory modification like hoppers and brewing stand recipe completion))


