Colin Block
- NegativeZ_
- negativez_
- Europe/Stockholm
- Yes
- No
Just 2 bugs that I noticed:
*After every push a hopper sends 2 items at a time
*Redstone locked hoppers still accept incoming items from other hoppers
Just
2bugs that I noticed:*After every push a hopper sends 2 items at a time
*Redstone locked hoppers still accept incoming items from other hoppersJust a bugs that I noticed:
*After every push a hopper sends 2 items at a time:
The hopper will release items in a stack 2 at a time in quick succession despite delay between each item.
Sorry, first time on Bug Tracker. Not too familiar with how it all works, would you like me to remove the post?
Just a bug
sthat I noticed:*After every push a hopper sends 2 items at a time:
The hopper will release items in a stack 2 at a time in quick succession despite delay between each item.
Hoppersbroke againHoppers push 2 items at a time
Hoppers push/pull 2 items at a time
Frozen blocks rarely don't generatingon population loadingFrozen blocks rarely don't generate on population loading
The Bug
Frozen blocks, such as snow layers and ice rarely don't generate in a strip of chunks.What I expected
Snow.What happened
Snow did not generate and ice did not freeze in a pond.Background
I created the world in 18w10a I believe and setup a home, then I continuously updated until 18w16a.However, the chunks shown in the photos provided are well over 500 blocks from previously generated chunks.More Information
The effected strips are only effected on the -X half of the chunk. The tree in the creative screenshots is just due to chunk loading (Generated the chunk without the tree and then the chunk with the tree thus populating said chunk and crossing the boundary). I tried recreating the glitch in different scenarios:
- Recreating the world and flying to the coordinates.
- Creating a Buffet world with just snow and ice, flew around generating terrain but did not find any replicates of the bug.
Theories
- This bug could be similar to another bug (Unfortunately I could not remember the bug nor could I find it in Bug Tracker).
- While I was exploring I was previously West (-X) of the glitched chunks, then retraced my steps and did a loop to go back to that spot. My guess is that those chunks were loaded, populated, but listed as populated, and then reloaded as populated chunks.
- Or I just have no idea what I'm saying.
The Bug
Frozen blocks, such as snow layers and ice rarely don't generate in a strip of chunks.What I expected
Snow.What happened
Snow did not generate and ice did not freeze in a pond.Background
I created the world in 18w10a I believe and setup a home, then I continuously updated until 18w16a. However, the chunks shown in the photos provided are well over 500 blocks from previously generated chunks.More Information
The effected strips are only effected on the -X half of the chunk. The tree in the creative screenshots is just due to chunk loading (Generated the chunk without the tree (Above the line) and then the chunk with the tree (below the line) thus populating said chunk and crossing the boundary), this screenshot shows the same recreated world at the same coordinates. I tried recreating the glitch in different scenarios:
- Recreating the world and flying to the coordinates.
- Creating a Buffet world with just snow and ice, flew around generating terrain but did not find any replicates of the bug.
Theories
- This bug could be similar to another bug (Unfortunately I could not remember the bug nor could I find it in Bug Tracker).
- While I was exploring I was previously West (-X) of the glitched chunks, then retraced my steps and did a loop to go back to that spot. My guess is that those chunks were loaded, populated, but listed as populated, and then reloaded as populated chunks.
- Or I just have no idea what I'm saying.
The Bug
Frozen blocks, such as snow layers and ice rarely don't generate in a strip of chunks.What I expected
Snow.What happened
Snow did not generate and ice did not freeze in a pond.Background
I created the world in 18w10a I believe and setup a home, then I continuously updated until 18w16a. However, the chunks shown in the photos provided are well over 500 blocks from previously generated chunks.More Information
The effected strips are only effected on the -X half of the chunk. The tree in the creative screenshots is just due to chunk loading (Generated the chunk without the tree (Above the line) and then the chunk with the tree (below the line) thus populating said chunk and crossing the boundary), this screenshot shows the same recreated world at the same coordinates. I tried recreating the glitch in different scenarios:
- Recreating the world and flying to the coordinates.
- Creating a Buffet world with just snow and ice, flew around generating terrain but did not find any replicates of the bug.
Theories
- This bug could be similar to another bug (Unfortunately I could not remember the bug nor could I find it in Bug Tracker).
- While I was exploring I was previously West (-X) of the glitched chunks, then retraced my steps and did a loop to go back to that spot. My guess is that those chunks were loaded, populated, but
listed as populated, and then reloaded as populated chunks.- Or I just have no idea what I'm saying.
The Bug
Frozen blocks, such as snow layers and ice rarely don't generate in a strip of chunks.What I expected
Snow.What happened
Snow did not generate and ice did not freeze in a pond.Background
I created the world in 18w10a I believe and setup a home, then I continuously updated until 18w16a. However, the chunks shown in the photos provided are well over 500 blocks from previously generated chunks.More Information
The effected strips are only effected on the -X half of the chunk. The tree in the creative screenshots is just due to chunk loading (Generated the chunk without the tree (Above the line) and then the chunk with the tree (below the line) thus populating said chunk and crossing the boundary), this screenshot shows the same recreated world at the same coordinates. I tried recreating the glitch in different scenarios:
- Recreating the world and flying to the coordinates.
- Creating a Buffet world with just snow and ice, flew around generating terrain but did not find any replicates of the bug.
Theories
- This bug could be similar to another bug (Unfortunately I could not remember the bug nor could I find it in Bug Tracker).
- While I was exploring I was previously West (-X) of the glitched chunks, then retraced my steps and did a loop to go back to that spot. My guess is that those chunks were loaded, not populated, but listed as populated, and then reloaded as populated chunks.
- Or I just have no idea what I'm saying.
Sethbling describes what I'm talking about very well:
Oneway DoorsThe yellow box as described in the video activates while in the air of a jump and clips the bottom edge of a block sometimes and the player looses momentum.
Steps to reproduce
Dig out a 4 block tall tunnel of any length.
Now place random blocks on the 4th layer.
Sprint and jump down the length of the tunnel.
Occasionally the player will clip the bottom of the block and loose momentum.
This glitch can be recreated with the debug stick.
One chest is rendered as a double chest but still labeled as single, and the one next to is just a single.

















Also, change the keybind for Discord aswell.
Very anoying for trying to write relative coordinates in command blocks.
Same happened with me, only it was random based. Thanks for the fix.
I don't believe this is a bug. I just checked the wiki and here is a caption from the Behavior section:
Note that even with commands, effects cannot be made to last forever. If an effect is set to an excessively large amount of time, such as 182 hours [655200 seconds], it will display as "*:*", but will still continue ticking down and eventually expire.
I believe this is implemented just to show that the timer is very high and may never be reached.
Odd, some clients crash because of clicking on the language settings. The resulting error is because the client couldn't find K (I believe it's Russian). Not too sure if they are the same bug.