Teemu
- UserTeemu
- userteemu
- Europe/Helsinki
- Yes
- No
MC-154809
Bug has been tested on Ubuntu 18.04 LTS with
- Intel Core i5-8500 @ 3 GHz x 6
- 64 GB of RAM (8 GB allocated to Minecraft)
- x64-based PC
- Java Version: 11.0.3, Oracle CorporationJava Version: 11.0.3, Oracle Corporation
- Java VM Version: OpenJDK 64-Bit Server VM (mixed mode, sharing), Oracle Corporation
And a Windows 10 machine
- Intel Core i7-8700K @ 3.70 GHz x 6
'- 16 GB of RAM (4 GB allocated to Minecraft)
- x64-based PC
- Java Version: 1.8.0_51, Oracle Corporation
- Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Crash log for Ubuntu is crash-2019-06-18_20.34.25-server.txt.
Crash crash-2019-06-18_22.08.18-server.txt for Windows 10.
NOTE: this seems to be a duplicate of MC-150680, but in vanilla Minecraft.
Minecraft world crashes if a infected chunk gets loaded.
Error: java.lang.NullPointerException: Exception generating new chunk
Chunks have previously worked just fine. But now suddenly there is a chunk in the end that can crash the game (look crash report attachments). Apparently there are other chunks like this as well in the world, but I have been unable to locate them. Please take a look at the world inside unzip me.zip to see the bug in action in the end dimension. (Also a quick tip: open the world to LAN so you will not be stuck in a infinite loop forever if you are planning to open the world more than once. It will revert you back to the overworld if there is a crash.)
Also some info:
- Bug appears at -1558 94 -6219 in the End.
- Bug does not persist in a newly generated world.
- World is generated in 1.14(.0) with normal generation (not amplified etc.) and updated to 1.14.1, 1.14.2. and all 1.14.3 pre-releases from 1 to 3.
- There are chunks that don't affect the bug removed from the world files to save space.
NOTE: this seems to be a duplicate of
MC-150680, but in vanilla Minecraft.
EDIT: The bug COULD be due to
MC-154499. Sho
Minecraft world crashes if a infected chunk gets loaded.
Error: java.lang.NullPointerException: Exception generating new chunk
Chunks have previously worked just fine. But now suddenly there is a chunk in the end that can crash the game (look crash report attachments). Apparently there are other chunks like this as well in the world, but I have been unable to locate them. Please take a look at the world inside unzip me.zip to see the bug in action in the end dimension. (Also a quick tip: open the world to LAN so you will not be stuck in a infinite loop forever if you are planning to open the world more than once. It will revert you back to the overworld if there is a crash.)
Also some info:
- Bug appears at -1558 94 -6219 in the End.
- Bug does not persist in a newly generated world.
- World is generated in 1.14(.0) with normal generation (not amplified etc.) and updated to 1.14.1, 1.14.2. and all 1.14.3 pre-releases from 1 to 3.
- There are chunks that don't affect the bug removed from the world files to save space.
NOTE: this seems to be a duplicate of
MC-150680, but in vanilla Minecraft.
EDIT: The bug COULD be due to
MC-154499. Sho
Minecraft world crashes if a infected chunk gets loaded.
Error: java.lang.NullPointerException: Exception generating new chunk
Chunks have previously worked just fine. But now suddenly there is a chunk in the end that can crash the game (look crash report attachments). Apparently there are other chunks like this as well in the world, but I have been unable to locate them. Please take a look at the world inside unzip me.zip to see the bug in action in the end dimension. (Also a quick tip: open the world to LAN so you will not be stuck in a infinite loop forever if you are planning to open the world more than once. It will revert you back to the overworld if there is a crash.)
Also some info:
- Bug appears at -1558 94 -6219 in the End.
- Bug does not persist in a newly generated world.
- World is generated in 1.14(.0) with normal generation (not amplified etc.) and updated to 1.14.1, 1.14.2. and all 1.14.3 pre-releases from 1 to 3.
- There are chunks that don't affect the bug removed from the world files to save space.
NOTE: this seems to be a duplicate of
MC-150680, but in vanilla Minecraft.
EDIT: The bug COULD be due to
MC-154499. There is a End city within 200 blocks with a item frame. Probably that causes the issue.
Minecraft world crashes if a infected chunk gets loaded.
Error: java.lang.NullPointerException: Exception generating new chunk
Chunks have previously worked just fine. But now suddenly there is a chunk in the end that can crash the game (look crash report attachments). Apparently there are other chunks like this as well in the world, but I have been unable to locate them. Please take a look at the world inside unzip me.zip to see the bug in action in the end dimension. (Also a quick tip: open the world to LAN so you will not be stuck in a infinite loop forever if you are planning to open the world more than once. It will revert you back to the overworld if there is a crash.)
Also some info:
- Bug appears at -1558 94 -6219 in the End.
- Bug does not persist in a newly generated world.
- World is generated in 1.14(.0) with normal generation (not amplified etc.) and updated to 1.14.1, 1.14.2. and all 1.14.3 pre-releases from 1 to 3.
- There are chunks that don't affect the bug removed from the world files to save space.
Now that I actually read the patch notes...
"If you stand on a honey block that is pushed by a piston, you come along for the ride"
Shouldn't you just be dragged with it, but not be able to actually go inside it?
So have the datapack do /datapack disable <it's name>?
What did you mean? Can you provide the datapack?
Optifine is a mod. Mojang does not officially support it.
Therefore I think this is a Optifine / OpenGL bug report instead of a Minecraft bug report.
@Dxad I don't think that is so. The crash happens with a delay. Within that delay, I was unable to see anything except Endermen, End Stone and chorus.
Good idea though! I'll test it when pre 4 comes out.
In my opinion this should be a feature. Gliding while in water with a Riptide 3 trident, is really useful. Without gliding before taking off, it is a lot harder.
I think this is a useful bug/feature.
Duplicate of
MC-154499Duplicate of
MC-154809@Dxad Actually, seems like it is caused by item frames. So the bug is due to
MC-154499. There is a End city within 200 blocks with a item frame. Probably that causes the issue. Not 100% sure, but that is likely.As far as I have understood, this is a feature, not a bug.
Edit: and I mean like facing hoppers on Y 0 facing down.
Not something like having a issue with blockstates (like dispenser being powered all the time)
In the picture, you can kind of see the angry particle, along with the heart particles. Both do give the heart particles first, but then go angry, once they realize that they don't have enough beds, which they actually do.
Can confirm for 19w38b.
Can confirm for 19w38b.
Duplicate of
MC-163001Now that I actually read the patch notes...
"If you stand on a honey block that is pushed by a piston, you come along for the ride"
Shouldn't you just be dragged with it, but not be able to actually go inside it?
Maybe at least change the visually indicated block outline / hitbox to be a bit smaller then?
So do slime blocks. Isn't it supposed to be transparent?
Well... As far as there are no honeyed pistons, I think this should be a thing. Even if there were ones.
I think it completely made sense, and should not have been fixed, since I think it's not a bug (It's a feature!).
I found this earlier than this report, but I thought it wasn't a bug, since it completely made sense. It was perfect for launching traps when combined with an observer.
Why would you "fix" this feature?
Sounds more like a feature but could be a bug.
Confirmed for 1.16.3
I think this issue is related to near clipping in rendering. At least in third person, it seems like this issue can be prevented if all block faces are rendered more than 0.05 blocks (the near clipping plane value) away from the camera.
I tested my theory about near clipping with a mod that changes the near clipping value to 0.03 from the original value (0.05). And yes, lowering that value decreased the area on screen, where you can see through blocks. That happened with all perspectives.
However lowering the value shouldn't be the fix, since it can break a lot of other things.
It seems this issue is caused by the fact that collision checks are only made during the initial state ("FLYING").
Once the bobber enters a block that has water in it (it seems it doesn't even need to touch the water, just be on the same block), it changes to the "BOBBING" stage. Once that has happened, there seems to be no branch in the code to change the state ever again. That means that it just is in BOBBING state forever. Thus, the collsiion check is never reached, causing it not to attach to an entity.