MissLauralot

Hoping this blatant inconsistency can be addressed in the future. Obviously it will require adding a setting to allow players now used to the backwards controls to keep them as it is. That’s why I was keen to get it fixed at the time as that extra work and confusion wouldn’t have been necessary.

Please prioritise bugfixing over releasing new features. Quality over quantity, as they say.

With all these missing features that are apparently out of Mojang’s control, I guess we were using the better old system for the last few years. What a downgrade. Embarrassing for Atlassian.

Still an issue in 25w46a.

Issue remains in 25w46a.

Ah woops, I missed that. Unfortunately, the ‘Issue Links Panel’ doesn’t load for me. An empty white box comes up with an endlessly loading circle. I see now that there is a message about “users experiencing issues loading the list of bugs” so I guess that is a temporary problem.

Still an issue November 2025.

Still an issue in 25w45a.

Still an issue in b3.5.17. The minimum is 1604x940 (Windows 10). In 2.1.17784, the minimum size is/was 1000x631. It was also much quicker to load had a better layout. Please stop making the launcher worse.

Can confirm in 1.21.4

Seed: -6533926018995126751

XYZ:  -896 83 -1348

XYZ:  171 68 869 

Windows 10 LTSC 1809. The launcher is "legacy" one, version b3.3.13-2.1.3.

Obviously you have a much clearer view of the internal workings and the changes from version to version so I'm not trying to say anyone is wrong. All I, as a player, see is the symptom (> 3x the load time). Is there a way I can gather more information for a new ticket? I attached a launcher log to the one I made but I don't know what to look for in it.

Affects 1.21.3

@davidsiegel

Since MCL-24706 was closed as a duplicate and the issue still persists, this ticket should be reopened.

Affects 3.3.13 (Legacy Win).

Hi @unknown. Did you see my comment with table which clarifies the inconsistency? Surely that cannot be intended as the Bundle is not even consistent with itself.

Other feedback also takes note of it – post 1, post 2.

Interesting, but rather than speculate on how the error came about what was intended at what point, I'll instead illustrate how clear the error/inconsistency is.

I made a comparison of various stone and greyscale blocks.

Screenshot of blocks -

Screenshot of map -

Blocks and map colours side-by-side -

Deepslate's map colour is actually darker than Stone/Andesite's - it's just a visual illusion. Tuff's map colour should probably be the same as Stone (112, 112, 112), the same as Deepslate (100, 100, 100), or something in between. Interestingly, the colours of the Tuff blocks are similar to Light Gray Concrete (slightly yellow/brown), though Light Gray Concrete's map color (153, 153, 153) is unsuitable due to being brighter than Stone and doesn't have the yellowy tinge anyway.

Time from when window first appears to when 'Play' button appears:

2.1.17784 - 4 seconds

2.27.19 - 15 seconds

2.27.11 - still takes ~25 seconds to load for me - double what it takes to load 2.1.17784, which itself used to be quicker. Windows 10 i5-7200U.

There should be probably be more thorough testing done but there's a definite issue with declining performance so unless there is a better ticket with more information provided then this one should be reopened.

Affects 2.25.4 (Legacy Win)

Confirmed in 1.21-pre3.

It looks straightforward to fix unless I am misunderstanding jigsaw blocks. Only two small changes to one file seem necessary.

The relevant file is 

1.21-pre3.jar\data\minecraft\structure\village\plains\town_centers\plains_meeting_point_1.nbt

1) Change the jigsaw with orientation:down_south (7th in palette) to orientation:down_north. This will then match the jigsaw in well_bottom.nbt, which is orientation:down_north.

2) Change its data (the one with state:6) from joint:rollable to joint:aligned to remove the randomness.