mojira.dev

Fenhl (Max Dominik Weber)

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

Assigned

No issues.

Reported

MC-297340 Unifont CSUR missing Invalid MC-118627 Hitting a wall ignores totem of undying Fixed MC-110999 Unloading chunks with many tile entities causes client-side lag spike Duplicate MC-106303 3 carpets are not enough to smelt one item Fixed MC-106117 Clouds flicker between different positions when spectating minecart Fixed MC-106002 Shift + double click no longer moves all stacks Fixed MC-99556 Camera looking in the wrong direction when spectating minecart Duplicate MC-95594 Beacons lose their effects Duplicate MC-93708 Iron golem attacking players on peaceful difficulty, but attack does not hurt player Duplicate MC-91538 Beacon effect indicator does not blink when moving out of range Won't Fix MC-90605 Constant teleporting between Nether and Overworld Fixed MC-89593 The Void required for Adventuring Time Fixed MC-87961 Client hangs when reconnecting to a server Fixed MC-86620 Cursor moved to center of screen when game gets automatically paused Confirmed MC-85728 Hoppers try to pull items from solid blocks Awaiting Response MC-85662 Snapshot client causes system lag Duplicate MC-85366 Empty lines on old signs show null Duplicate MC-84069 Beacon effects constantly blinking even while in range of the beacon Fixed MC-83930 End City spawns even without Generate Structures Fixed MC-67338 Item in hoppers in the Nether disappears Awaiting Response

Comments

It does, thank you.

Please reopen, this is still an issue in 1.16-pre5. To reproduce:

  1. In a save-mode structure block, either manually set the size to something like 36×36×36, or use a corner-mode structure block to do so

  2. Click save or done

  3. The outline is reduced to 32×32×32, and loading the structure also only loads that part

@@unknown: 1.13 is already marked as affected. Please check the affected versions before confirming an issue.

Sounds like you fixed MC-102403 instead of this issue, so this ticket should be reopened.

I do not have access to macOS 10.13 “High Sierra”, but on 10.12 “Sierra” and 18w07c, this is now a crash bug:

  1. Activate native fullscreen.

  2. Activate F11 fullscreen.

  3. Switch to a different fullscreen app or desktop. This causes Minecraft to minimize into the Dock.

  4. Reactivate Minecraft by clicking the app icon in the Dock.

  5. Deactivate F11 fullscreen. Minecraft is now in a window within its fullscreen app slot. At this point, it is no longer possible to restore correct fullscreen functionality.

  6. Restore to windowed mode by dragging Minecraft down in Mission Control.

  7. Activate native fullscreen.

  8. Press F11. This causes Minecraft to crash.

Unfortunately, setting a 0.003 second delay is not a sufficient workaround to stop our hourly world backup script from occasionally crashing the server.

Fixed in 17w43b, as tested with books, signs, and command blocks.

Is there a ticket for the crash? I have not found one so far.

It is not native fullscreen but F11 fullscreen that crashes Minecraft.

Fixed in 17w43b.

This appears to be fixed in 17w43b, at least for my custom keylayout.

Same here. This appears to be fixed in 17w43a.

Just to clarify, given the MC-121279 link: Is this the right ticket for vanilla Minecraft (no resource packs) not playing any sound or music whatsoever?

@@unknown: 1.12 is already marked as affected. Please check the affected versions before confirming an issue.

I generated some new terrain in the same End and received the advancement upon entering a newly generated End city.

I can confirm this bug on a multiplayer server. The End city in question is correctly saved in the data/EndCity.dat file, and I am standing in it but not receiving the advancement.

@@unknown: Please stop constantly editing your posts. 6 people are receiving an email each time you do. The preview feature exists for a reason.

@@unknown: 1.11 is already markes as affected. Please check the affected versions before confirming an issue.

@@unknown: 1.11 is already markes as affected. Please check the affected versions before confirming an issue.

@@unknown: 1.10.2 is already marked as affected. Please check the affected versions before confirming an issue.