mojira.dev

Thomas Hall

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

Assigned

No issues.

Reported

MC-129440 Select chunks reset to world seed upon loading a world from a previous snapshot Duplicate MC-124187 Simultaneous movement key press not registering - Linux Duplicate MC-123835 Colored sidebar display slots are not visible Fixed MC-123440 Java error printing in console when particle not visible to players Duplicate MC-114314 Sweep attack doesn't affect entities on same team even with friendlyFire on Confirmed MC-96254 Player grace period missing for damage Fixed MC-91508 Visual Block Lag with clone commands Duplicate MC-86109 Translucent rendering of signs Cannot Reproduce MC-86104 /give creates broken splash potion Incomplete MC-70446 Severe Crash Caused by Custom Villager Trading Duplicate MC-68485 Unable to jump while holding sprint key at the same time Duplicate MC-66298 Crash when attempting to make a mob spawner spawn Items Duplicate MC-62103 Status effects misbehave with faster clocks Works As Intended

Comments

Affects 1.21.5

I've observed the same issue: Despite confirming that the internal server is running at 20 TPS, liquids will cease propagating for no evident reason. Applying block updates doesn't resolve the issue

[media]

. 

[media]

I can confirm this issue up to 1.16.5 (Linux Mint 20.1 Cinnamon), and while it's relatively unproblematic as the game resumes upon closing the external application, all buttons that open external applications including the "Open Pack Folder" buttons for resource and data packs cause the program interruption. In the 1.17 snapshots (21w03a) Minecraft cannot resume after closing the external program, and instead crashes.

Confirmed for me on 1.15 pre-6. The entity appears pure white from some angles, and glows with a white outline from others. Entities which are visible work as normal, and those on the same team as the player with seeFriendlyInvisibles set to true work properly as well, as depicted in the second screenshot.

[media][media]

WORKAROUND:
There's a fix coming down the pipeline for glfw potentially; in the corresponding issue in their tracker is this link https://github.com/glfw/glfw/pull/1472/files#diff-0f3106b1408d89cbecbe2f57a783331bR1265
it leads to a fix which describes what lines to change and how in order to resolve this bug as well as the issue that caused it in the first place. If you feel like compiling your own libraries to restore your ability to enjoy parkour and pvp, then that's the solution.

Confirmed for 1.13.2

I'll elaborate, since I'm working on this project with the reporter. We used to regularly experience MC-123363, but when it was marked resolved we could no longer trigger that one specifically.

This crash showed up after MC-123363 was resolved and the reporter has been unable to reliably replicate it.

In order to replicate the crash, we run a function which procedurally runs fill commands and loads a selection of structures. During the generation process players who are have the affected chunks loaded will sometimes have their games crash in a manner similar to MC-123363.

Affects 1.13 pre-6

Unable to replicate by breaking only one banner at a time. Using a fill command on a large cube of banners I was able to reliably crash the client. Looks like MC-123363.

Can confirm, it should be noted that this bug is most obvious while immersed in water and it can be hard to tell what is going on if your character is outside of it

Jumping on this bug before it gets marked as duplicate, there is currently no valid root bug for this particular issue. MC-123498, which currently has a large number of bugs marked as duplicates, is marked as invalid because "this is not a technical support forum".

The 'bug' appears to have shown up in 1.12 as well as the snapshots as a recent change, and all of the bug reports which include an environment list Windows 10. I can confirm that this bug appears in Windows 10 but not Linux Mint 18.3 while fullscreened in both 1.12.2 and the snapshots.

It seems likely that a change in Windows 10 has caused a problem with how Minecraft draws its window.

EDIT:

To clarify, the bug appears in fullscreened but not windowed mode.

cannot reproduce in 1.13 pre-3

[media]

Supposedly Mojang was going to recalculate all light levels in existing worlds when 1.13 came out to fix the change to how light passes through water. There's a reason that Mojang strongly recommends not playing full-time on the snapshots.

Confirmed for 1.13 pre-release 1.

Alright, I finally got around to testing in the latest snapshot. As of 1.13 pre-release 1 The problem persists only as long as the vanilla datapack isn't loaded. Loading it and then relogging fixes the issue.

That matches the symptoms of MC-129838

Bug extant in 1.13 pre-1. It functionally means you can't disable the vanilla datapack.

This bug is not fixed. Affects 18w21a as shown in attached screenshots.

 

[media][media]

Affects 18w21a on a world last opened in snapshots.

EDIT: Swimming in singleplayer first does not fix the problem as the reporter above claims.

No need for sarcasm. The bed breaks even with blocks below, or I wouldn't have mentioned it.

Bug appears to be fixed for Tallgrass and Doors as of 18w20a. Can anyone confirm? Beds load, but immediately break.