MrKinau

Correct server download can be found here: https://piston-data.mojang.com/v1/objects/5f2e44493daf3cd4ab757e59921313c9c8d95151/server.jar

From piston meta: https://piston-meta.mojang.com/v1/packages/f8ce00355c7535323ad546f1f702e3aaaa48a99a/26.2-snapshot-3.json

Can confirm, maybe duplicate as this was intended to be fixed as MC-307286 is marked as resolved.

It is definitely better, it’s not happening all the time, but it is still happening on the first launch with a clean installation, I tested a bit around it seems to happen every time the onboarding screen is shown.

Steps to Reproduce

1. Modify the file options.txt: set onboardAccessibility:true or use a clean installation without any previous options.txt

2. Start the game

3. Click Continue in the onboarding screen.

4. Click Quit Game and see the process still running

Observed Beahvior

The process never ends, unless terminated manually using a signal.

Expected Behavior

The process ends after quitting the game.

Video

Another issue I’ve noticed, which seemingly is caused by the same unknown root cause is that chunk loading is pretty slow. Initial spawn chunk loading is fine, but after reloading chunks only the chunks directly around the player load properly and every other chunk takes very long to load or will only load after I looked around or moved. This feels pretty much the same as with the blocks not disappearing as they usually disappear when moving the mouse again, and this issue got introduced in 26.1-snapshot-7 as well.

I can confirm the Vulkan behavior in fullscreen is quite different from the behavior of OpenGL, I don’t have the same issues, but I do have significantly lower FPS when in fullscreen with Vulkan (except when something else like a desktop notification renders on top of the fullscreen window), regardless if it is exclusive fullscreen or not. I can’t see any difference between window manager fullscreen mode and just pressing F11.
Dunno if this is just a hidden KWin/KDE/Wayland/whatever feature or an actual bug.

Side note: Monitor only has 60Hz

boolean chatDisabledOrBlocked = minecraft.player.chatAbilities().canReceivePlayerMessages() || socialManager.isBlocked(id);

should be obvious whats wrong here 😅

Just tested on my Laptop with Ubuntu 25.10 and Mesa with Intel UHD Graphics 630, bug occurs, but looks like it’s happening less often.

Can confirm for 26.1-pre-1

same on X11

Can confirm (conditionally).

I was not able to reproduce this without using insanely high Luck of The Sea or luck effect values, but using such high values it is possible to get no loot when fishing in a “non open water spot”.

For reproduction you can use either a high luck of the sea value:

/give @s minecraft:fishing_rod[minecraft:enchantments={lure:3,luck_of_the_sea:3},minecraft:unbreakable={}]

or a high luck effect value:

/effect give @s minecraft:luck infinite 100

Some additional information to help fixing this:

• like clamlol said, setting mipmap levels to off and restarting the game prevents the issue from happening.

• Furthermore: setting Antisotropic Filtering to x4 or x8 fixes the issue as well (no restart needed), setting it back to x2 or off wont cause it to be blurry until restarted. (it was set to x2 by default for me)

• My blocks atlas looks let’s say “interesting”:

  [media: minecraft_textures_atlas_blocks.png_0.png]

• Attached my client log: https://mclo.gs/F8zS2C7

• And an intended crash for system details:

from crash report:
Operating System: Linux (amd64) version 6.8.0-45-generic
Processor Name: Intel(R) Core(TM) i7-14700KF
Graphics card #0 name: GP104 [GeForce GTX 1080]

^ ironically: removing the glowstone actually makes the game look brighter

1.21.8 (Brightness: Bright):

1.21.9 (Brightness: Bright):

ig it’s the same issue. Is this really WAI? It’s quite a big change to the looks of the night vision effect which is not mentioned in the changelog

On a local server with much power the issue is barely visible, to reproduce it for a longer period of time I’ve spun up a testing server with limited CPU power using

cpulimit --limit 100 -- java -jar server.jar nogui

Can confirm for 1.21.6-pre2: Additionally this does not only apply to the hotbar, it applies to many more UI elements (Scoreboard, Bossbar, Chat, Titles).

This also applies to switching “subservers” that are located behind a proxy.

Can confirm this. It additionally not only applies to centered or rotating text displays, it also affects bold static title text (depending on the gui scale the gaps appear at different positions)

/title @s title {"text":"vmVM","bold":true}

1.21.3:

1.21.4: