mojira.dev

Fry

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

Assigned

MC-265656 Pumpkins can no longer be sheared Fixed MC-260409 Cherry Grove biome is not in the #is_overworld biome tag Fixed MC-260296 Pink petal block models are not optimized Fixed MC-260059 Pigs do not seem to spawn in Cherry Grove biome Fixed MC-257378 Villagers and piglins can't open or close doors Fixed MC-249831 Aquifers can cut themselves off at chunk borders Fixed MC-249405 chatScale option defaults to 0.0 instead of 1.0, causing chat to disappear Fixed MC-249392 Options have missing or untranslated names Fixed MC-249389 GUI Scale is a slider instead of a button Fixed MC-248636 The game output and server console are logged and spammed with "Creating a MIN function between two non-overlapping inputs" when joining or creating a world Fixed MC-241830 Windswept savannas in amplified worlds have the incorrect surface blocks Fixed MC-241409 Game crashes when terrain shaper data is missing Fixed MC-241245 Generated Deepslate overwrites ore veins (mainly Iron ore veins) Fixed MC-241194 Crash: java.lang.NullPointerException: Cannot invoke "ddm.a(cao, cps, java.util.Random, gh)" because the return value of "java.util.function.Supplier.get()" is null Fixed MC-241172 Rare Datafixer error occured in old world Fixed MC-240631 Extremely slow End terrain generation Fixed MC-240507 Mob Spawning in structures fails in pre-1.18 generated monuments/swamp huts/outposts Fixed MC-240503 Bedrock doesn`t generate in Badlands or Wooded Badlands Fixed MC-240495 Deepslate does not generate below Y=0 in Badlands or Wooded Badlands Biomes Fixed MC-240494 Duplicated mineshafts with new cave generation Fixed

Reported

MCPE-51211 Problem with the GUI and menus Cannot Reproduce

Comments

Is this still an issue in 1.18 Pre-release 2?

Please provide seed/coordinates for 1.18 Pre-release 1, if the issue is still happening

@unknown was the world created fresh in 1.18 Pre-release 1, or was it created earlier?

Is this still an issue in 1.18 pre-release 1?

Is this still an issue in 1.18 pre-release 1? fluid propagation was improved

Is this still an issue in 21w44a? Please try loading directly from 1.17.1 to 21w44a; for worlds loaded in 21w43a erasing the caches might solve the issue (Select world in the menu, press Edit, press Optimize World, check Erased cached data checkbox, proceed)

If you still have this issue in 21w44a, try erasing the cached data (Select world in the menu, press Edit, press Optimize World, check Erased cached data checkbox, proceed)

I can reproduce this in 21w43a, but not in 21w44a; is this still an issue in the latest snapshot?

Is this still an issue in the latest snapshot?

Hi! Could you please attach the full server log with the crash on the latest snapshot? It should contain more debugging information that should help us track down this issue

The glass block does not render it's faces when seen from the inside; is that the only issue you see, or is there something else?

Is this still an issue in the latest pre-release?

Please post the full game log if you experience this issue, in addition to the crash report.

Pack has version 4, which is the format used in 1.14; 1.15 will use version 5, and version 4 is partially updated to that when possible, but this pack has banner patterns in 1.15 format, which makes them break on load; you need to either roll them back to 1.14 format, or update the pack fully to 1.15 format

behaves a little weirdly

Can you be more specific? 🙂

No worries, better safe then sorry 😉

If this is still happening to you, and if you have a backup of the world right before you can trigger the issue, that might help; I managed to get one and consistently reproduce it, and fixed what was causing it, but there might be more to it; if you can reproduce it by

  1. Restoring the backup

  2. Choosing edit -> optimize -> erase cached data (before loading it)

  3. See the issue immediately after loading the world

Then it would be very helpful if you can share your world backup, along with what render distance you're using.

Thanks!

 

1.14 or 1.14.1-pre1? One of the fixed issues was for the server shutdown code.

Does this still happen in 1.14.1-pre1 with either a new world, or a world with an erased cache? Please keep in mind that it's possible to trigger it, close the game, but not see it until you load the world the next time.

This bug is taking so long because we have not found any way at all to trigger it on demand; I never manager to trigger it once on my machine, and there seems to be no action in particular that makes it more or less likely to happen; a few potential causes of this error were fixed in 1.14.1-pre1, but without being able to check there's no way to know for sure.