mojira.dev

Panda4994

More than one avatar was detected! There might be multiple accounts sharing this same name.

Assigned

MC-298605 When creating a Water World superflat world, the player spawns at the bottom of the sea Fixed MC-297614 Area effect clouds with duration greater than or equal to 2147483628 disappear after a tick Fixed MC-297275 Players can desync from their mounts when jumping on a happy ghast Fixed MC-279417 Luring mobs onto blocks at Y=-64 will instead make them pathfind to the highest elevation Fixed MC-279301 Player dies by falling from 22.00001 blocks instead of 23 blocks Fixed MC-279281 Fall damage occurs from jumping from 2 blocks up Fixed MC-277754 Chunks on the corner of the rendering distance are not synchronized between client and server for the terrain Fixed MC-277548 Invisible block entities and items disappearing Fixed MC-277275 Crash upon loading chunks when teleporting Fixed MC-276979 Lock field on containers and minecraft:lock data component do not get datafixed correctly when a \ is present Fixed MC-275774 Observers no longer detect redstone dust powering/unpowering Fixed MC-275397 Redstone dust doesn't update properly Fixed MC-275332 The rotation of a wall/ceiling lever and button does not affect the update order of wire in Redstone Experiment Fixed MC-273288 Dropping a stack of items while in the creative mode inventory deletes them Fixed MC-272843 Stepping up blocks while falling on the side of them can sometimes allow players to climb to normally unreachable heights Fixed MC-272553 Naturally generated End Stone drops in cases where the Obsidian platform generates inside the island Fixed MC-272424 Chunks occasionally have large dark areas in the sky Fixed MC-272329 Riding an entity into portals may cause the game to softlock Fixed MC-272322 When you are riding an entity through portals, you and the entity may teleport to the wrong place Fixed MC-272198 Shulkers' models sometimes appear offset upon end city generation Fixed

Reported

MC-143979 The order in which tile entities get processed changes after reloading Confirmed MC-142768 Mobs can suffocate below blocks, if the eye height isn't inside the collision box Fixed MC-141485 Spawn chunks changed size from 16/17 to 23 side length Invalid MC-141484 Entities stay on the global list even when the chunk unloaded Fixed MC-141483 Changing the render distance can cause chunks to stay loaded Fixed MC-141482 /forceload loads an area one chunk larger than specified Works As Intended MC-141480 /forceload query can not be run from functions or command blocks Invalid MC-140985 Scheduled ticks get lost when leaving chunks (Redstone components get stuck) Fixed MC-140853 Being close to the end island causes out of memory and file descriptor exhaustion Fixed MC-130942 Errors, warnings and 10 second freeze on loading list of singleplayer worlds Fixed MC-125044 Signing-GUI of Book and Quill does not interpret TextComponent of the Author Duplicate MC-123217 Moving blocks don't inherit behaviors of the block they hold Confirmed MC-120596 Hopper don't pick up items under certain conditions Confirmed MC-119808 Minecarts drop their items offset in the positive direction Fixed MC-119807 Breaking inventories next to walls can cause items to glitch away Fixed MC-110455 Crash while using a lot of pistons/slime blocks (java.lang.IllegalArgumentException: Cannot get property) Duplicate MC-110247 Moving blocks can move entities into other moving blocks (also when they move in a different direction) Fixed MC-110244 Moving blocks use 0,0,0 as surrounding to calculate their bounding box Fixed MC-110094 Entities can fall through moving fences Fixed MC-109604 Removing a powered observer does not cause all needed updates Duplicate

Comments

Hello, Dispensers work fine in odd and even ticks. It’s sheep eating grass that now only occurs every second tick for optimization reasons. While it is not ideal that those tick alignments are visible in farms like yours, they should still work fine. The second set of dispensers should start taking over once the first one runs out.
We consider this issue a Won't fix which means there is no specific plans to track or fix this issue by itself, but it might get addressed by future system reworks eventually.

Hello,

Inside your .minecraft folder there should be a folder debug containing reports about the misplaced chunks. Could you attach those?
Also did you use any mods or external programs on this world (e.g. world edit)?

Also the logs from the time you got the errors might be helpful, if you can find them in the .minecraft/logs folder.

Hello, you marked 1.21.8 Release Candidate 1 as affected version, but the attached screenshot shows 1.21.7.

We fixed the reported issue in 1.21.8 Release Candidate 1.

I will close this report as duplicate. If the issues actually still occur on 1.21.8 Release Candidate 1 for you, please make sure to create another report with an up to date screenshot.

Thank you!

Hello, could you please attach a screenshot with the debug screen open?
You can open it in game by pressing F3.

Please make sure to be in the lastest version while doing so (1.21.8 Release Candidate 1)

The report is unclear in what this would add. Could you please explain?

This issue is invalid, but may I indroduce you to https://piston-meta.mojang.com/mc/game/version_manifest_v2.json 🙂

Hello,

Yes, JVM version is essentially the Java version. JVM stands for Java Virtual Machine.

You can find out which version you are running by pressing F3 in the game and looking at the top right of the screen.
But also, if you crash again, the crash report mentions the exact version at the very end of the file.

We recently changed the JVM version the game runs with to a newer version, so the suspicion is that this might already resolve the issue.
But if you still encounter the crash attaching a new report would be very helpful.

The Nvidia GPU Driver update is an interesting piece of context, thank you!

Best regards!

We do not have enough information to find the cause of this issue.

Please attach the affected (zipped) world file. If the file size is too large, please upload it somewhere else and then link to it here.

This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.

Hello!
I wasn’t able to reproduce the crash, but given that it happened three times in a row for you, this is an interesting crash to investigate.
Would it be possible for you to attach the crash reports? They should be in the folder %APPDATA%/.minecraft/crash-reports (assuming you are on windows) and have the date/time of the time of the crash in the title.
If there is no crash reports a video/screenshots of what it shows after the crash would be helpful as well.

I will set the report to Awaiting Response. It should reopen automatically once you provide additional information.

Best regards!

Hello,
this was an issue in the snapshots, but has been fixed in 1.21.6 Pre-Release 1.
The attached crashreport is from 25w21a. We closed this issue as Invalid as it’s not reproduceable on the claimed version.

Best regards!

While we are not looking to fix this, we think there is ways to work around this.

  • Use item_modelcomponent instead of custom data

  • Use custom_model_data and select instead

Does this issue still occur in 1.21.5 Pre-Release 1?

Was there a resource pack enabled when the errors showed up?
Also could you please screenshot the F3-screen? Thanks!

TLDR:
Various bugs causing MC-2025 have been fixed over the years. The remaining ones listed here are no longer reproducible.
If you are still encountering issues please follow the steps to create a new report for them.
 
Happy 2025!

 

The long version:

Hello everyone!
 
MC-2025 is the most up-voted bug report on the bug tracker. It has been open for over 12 ⚠️ years with so many contributions and reproductions from so many people.
That the issue is still open after 12 years is not down to a lack of trying to fix it. But the reality is, that there have been a lot of different contributing factors in the code, resulting in many different issues manifesting in a similar way.
As specific causes got fixed, the details on this report have been updated to match the remaining ones.
At this point a lot of them - in fact all that we are aware of - have been fixed!
 
It's not easy to get a full list of the underlying problems that caused MC-2025 and related issues, since many of them were never separately tracked as an own bug report.
 
But here is a list of a couple we were able to find:

  • Collision boxes having floating point rounding issues at high coordinates
    Fixed in 1.5

  • Collision boxes being globally changed from several threads
    Fixed in 15w38a (1.9)

  • Collions issues on chunk loading
    Fixed in 17w47a (1.13)

  • Baby mobs growing up next to blocks (MC-9568)
    Fixed in 21w05a (1.17)

  • Chickens spawned from eggs being in blocks
    Fixed in 21w05a (1.17)

  • Frogs growing up next to blocks (MC-253791)
    Fixed in 24w19a (1.21)

  • Baby mobs growing up next to blocks below blocks (MC-252846)
    Fixed in 24w19a (1.21)

But there is no doubt there was more!
 
 
So, what about the possible reasons that are still listed in the description of this report?

  • Floating point inaccuracies
    We got no working reproduction steps and nothing that would suggest this is still an issue.

  • Mobs moving in unloaded chunks
    It's questionable this ever was an actual issue. If it was, it has been fixed long ago.

  • Baby mobs growing up
    Fixed as per MC-9568, MC-253791 and MC-252846

With all this said, at this point we see no value keeping MC-2025 open.
It looks like the issue described by the title "when loading chunks" has been fixed by larger collision refactors in 17w47a (1.13), so we will be setting this as the fixed version.
The issues of mobs growing up next to blocks getting out was likely the reason MC-2025 got reopened the last time it did, but this has been fixed since.
 
If you are still encountering issues of this kind, please don't ask for this report to be reopened, but instead follow the steps to create a new report.
 
Thank you for all the contribution on this and other issues over the years!
 
Happy 2025 and hpp new er!

Is anyone still experiencing this issue in the current version?

Is this still an issue?

Is this still happening? If so, could we get some repo steps or further information added?

Link in the description appears to no work anymore.

This appears to no longer happen.

Hello, do I understand correctly that this does not go away when you restart the game?
If so, could you attach a copy of the affected world?

This report collected a lot of dust over the years.
The core of the issue has been fixed a while back, but it got reopened with changed repo steps.
So this time it was fixed according to the repo steps. Chickens did suffocate when spawned from eggs, because they would end up slightly in blocks. That's fixed, spawning chickens from eggs no longer does that.
Addionally MC-253791 (the frogs) and MC-252846 are fixed. Both were issues that were hidden in the duplicates of this issue and MC-2025.
Which brings me to the reason for my little rant: If there is new repos for suffocating mobs showing up, please make sure this issue is not reopened, but they are reported as new issues. Otherwise easy to fix issues can get lost behind lots of outdated information of old reports. Thank you! (and thank you for testing if the fix worked!) 🙂