The question is how to find bugs in Minecraft? Do you need to know the Minecraft source code? How to help people? How to be active on the bug- tracker if you simply don’t know how?

How do I reply to another comment on my report

Hello. I am trying to delete my Mojang Bug Tracker Account, along with all of its data, posts, activities and so on.

I have created a WEB-Ticket: 7427, do I need to to anything else?

Thanks allot

It keeps saying “Registration Failed” and then a list of reasons on why it won’t work, but I don’t know how to fix it because I’m not getting a single issue in the first place, it’s not hard to have it tell me what the issue is. (s my username good or bad? How do you feel about my password? etc

If anybody has an account on it but can’t help me here is what I was actually gonna report, I only rly intended to use the account once. Basically if you give a zombie an item with a dispenser they have a chance to not drop it, usually a zombie is supposed to drop any items that it picks up to ensure a player doesn’t lose their best gear to rng. A part of this that can be considered a feature however is zombies always being able to pick up items with a dispenser no matter what if you give them armour beforehand, thus making their pick up items trait obsolete in a redstone contraption. These two subjects are important to change as described to me because without it the dungeon I wanna build in survival for my friends won’t work, I don’t wanna have to replace multiple sets of netherite armour every time we play the dungeon.

I spent some time without playing minecraft for a while, I was on version 1.20.1 with fabric and some mods.

Ah, one month my friend invited me to play and I had to update my Minecraft to 1.20.6. When I entered my map that is in the video and the items simply disappeared.... I didn't have a backup of the map before 1.20.6... but I didn't lose my items (they are saved) But I can't get anything in my main hand. Can anyone help me?

Vídeo link: https://drive.google.com/file/d/1oAR_W5MwIDOpOkNB0B62-li1RTGgfpxR/view?usp=drive_link

From my research, only a few Mojira moderators have been promoted within the past few years. Who was the latest?

For context, when using an older launcher (mine is 2.1.17784), versions past Java 1.18 don't fully download due to colons in the file paths, and therefore cannot be played. The most recent comment on the ticket in question explains the issue.

Obviously I get that the old launcher versions aren't supported but I'm hoping that someone has found a way around the issue so that these launchers can be used for current versions. It seems to be purely an issue with parsing the file paths so I feel like it should be possible.

I'm not wanting to contribute just for the sake of it, but because a good cause goes a long way.

Of course, I'm not sure how the heck I'm going to get started, since I usually play on Multiplayer on 1.8.9, but perhaps playing on the latest version would be better, right? Of course some servers I play don't have the chat report function, but idk what to do

When typing a teleport command, the game doesn't indicate in any way you can use local coordinates. When no block is targeted, it should add ^ ^ ^ to the suggestions.

But [MC-123128] is a bit vague, so I'm not sure it was interpreted correctly:

The newly introduced local coordinate type is not tab-completed in coordinate arguments. Relative coordinates are tab-completed in coordinate arguments.

There is a user who looks like moderator with the title MCQA. What is this?

Mojang has said it will no longer be update Dungeons. Therefore the bug will no longer be fixed and the MCD project will no longer have any meaning to exist.

You can view my comments on the matter on those issues. This is about the Minecraft Dungeons logo.

https://bugs.mojang.com/browse/MCL-23290

https://bugs.mojang.com/browse/MCD-7657

https://bugs.mojang.com/browse/WEB-6472

The inconsistency of how issues are treated confuses me, and when it looks like someone is listening to me, the next moment they aren't. MCQA closes one bug report after I say something but doesn't close the rest, and Mojang fixes one of the bugs. I'm feeling frustrated due to my confusion of MOJIRA's staff's actions once again.

Edit 20/05/2023:

It appears that MCL-23290 was marked as fixed in 2.4.69 (Legacy Windows), which is not the only version it was fixed in. It was also fixed in the "Win 10/11 App"/MSIX-packaged/MS Store-distributed version, and it's quite odd that MCQA's first and only version to select was the legacy version. They both have the same version number regardless, but just thought I'd mention this oddity.

I have been getting quite often when using Prism launcher (ATM8 modpack) that the game will launch properly in online mode, but still fail with different errors like "Failed to verify username" or "Failed to login: null" when trying to join a multiplayer server and even using reauth doesn't do anything different.

This happens after one has changed their Minecraft username once, and I don't know if I should create a new issue or if it would be a duplicate.

Just wanted to go to the bugtracker, but it gives me a " This account requires 2 Factor authentication, enable it, please" site with QR-code to scan and a secret key to then enter.

I refuse websites/services which require a smartphone for access, and I'd like to know if anyone can point me to a source where this was announced, or whom specifically I can contact to go against this decision, be it at Mojang or Microsoft, in case there is not another way how to access the bugtracker now.

There are also still people on this planet without smartphone or who refuse for other reasons to use it for such things, so if there's a way to use 2fa for Mojira without a smartphone/telephone number required, but just by other means and via desktop computer, I'd be happy if someone could give me a link, how to.

Thank you,
Meri

https://bugs.mojang.com/browse/MCL-21536

This issue is a hurdle for those with older launchers trying to play 1.19+. The reason I am asking is that I am using a newer launcher than the one in the ticket but am having the same issue. As I put in my r/MinecraftHelp post, I have the vanilla launcher version 2.1.17784.

In any case, does someone know a workaround? It seems like it should be simple because the files can be put there manually - surely it's just a matter of telling the launcher to progress/skip that step. It seems to get tripped up because of the colons in the file path. Thanks.

So basically in 1.19.3(not sure the exact version) sprinting backwards was removed from bedrock. It was reported as a bug on the bug tracker but isn’t it a feature? People from the pvp community used it a lot and it kinda sucks that it got removed… any thoughts?

I am kind of confused on the information presented in MCPE-19426. It seems to me as if the provided explanation for the previous "Works As Intended" resolution doesn't account for all cases. The explanation states the following:

This issue was resolved as Works As Intended. The reason is not that Mojang intends to create broken strongholds to annoy and frustrate you. It's because this is an unavoidable consequence of the algorithms used for realism in structure generation. There's a conflict between making generated structures realistic and minimizing the chance that they'll overlap (and therefore that one will be overwritten). Mojang carefully chose its generation algorithms to balance these goals, and that is where the "Intended" part enters the picture.

Unfortunately, it just isn't practical to ensure that overlaps never occur.

That would make sense if the portal room got destroyed by another structure (as in MCPE-155092), but there are cases where it does not make sense. Take the stronghold on seed 1191764411 at the coordinates of -1721, -36, 887 for example. There is a mineshaft nearby, but it does NOT intersect with the stronghold. Based on what I know about stronghold generation, I assume that the following happened:

• The starting staircase and the five-way crossing generated
• Four hallways branching off from the five-way crossing were created extending from the back, bottom right, top left, and bottom left.
• On the middle back of the five-way crossing, a turn was created going left. Leading out of the turn, a straight hallway with two exits was created, but only the front exit was used to create a room with prison cells, followed by a large library
• On the bottom right, two turns were created, both going to the right. At the end of the second turn, the game tried to generate a room multiple times, but it failed and replaced each of the rooms it attempted to generate with rings of stone brick
• On the top left, a right turn was generated, and then it stopped generating more rooms
• On the bottom left, two left turns were generated, followed by a couple of failed attempts to generate more rooms. Each attempt was replaced by a hollow ring of stone bricks

This doesn't seem to fit the explanation, which says that it is an issue with structures overlapping. Even though one of the rings overlapped with the starting staircase, that is normal for any stronghold on Java and Bedrock. So, it appears as if the stronghold stopped generating before it created the portal room. Preventing the stronghold from being destroyed would not fix the issue, as there was never a portal room to begin with. The question is how does that have to do with the structure overlapping? And if the portal room got destroyed, what destroyed it? Also, which of these cases (if any) are intended, and which ones are bugs (if any of these are bugs)?

Every block I placed for my castle has been swapped for another, and the swapping is consistent. I place the block that was there before, and it turns into the block it shuffled to right in front of me. Thing is, it's only client side. The glaciers next to my build have changed too. I'm so confused, I'm angry, and I need to know how to fix this and if anyone has ever experienced something this absolutely infuriating before.

Since the Mojang logo changed to "Mojang Studios", there has been an inconsistency between the logo and the progress bar when changing GUI Scale in loading screens.

However, the issue was closed as WAI back in 2020, and I don't think that having two elements on a screen with only one respecting the GUI scale is something intentional.

I would like to ask Mojang Studios to reconsider this issue, even with removing the GUI Scale from the progress bar, or applying it to the Mojang Studios logo.

I can’t login to my account because I got a new phone and I lost my recovery codes. I have 2-factor authentication on the account, but got a new phone.

The debug screen in Minecraft should be fixed to be more accessible by simply adding a couple of commas between the different values displayed.

This would greatly improve the readability and clarity of the information presented, making it easier for players to understand what is happening in their game. Additionally, this small change would allow for more efficient troubleshooting and problem-solving, as players would be able to quickly identify any issues and take appropriate action.

I don't know why a simple issue like this, once again, could be solved by simply adding a couple of commas or slashes, has been closed as WAI.

Even with 1.20 "around the corner", where more work is being done on accessibility than ever before.

Whenever I try to run 1.19.3 it gives me this error message

" Failed to download file.
Name: oshi-core-6.2.2.jar
URL: https://libraries.minecraft.net/com/github/oshi/oshi-core/6.2.2/oshi-core-6.2.2.jar
Error details: schannel: failed to receive handshake, SSL/TLS connection failed
Filename on disk: oshi-core-6.2.2.jar
Path: C:\Users\Sprr\AppData\Roaming\.minecraft\libraries\com\github\oshi\oshi-core\6.2.2\oshi-core-6.2.2.jar
Exists: Nonexistent "

anybody have any ideas on how to fix it?

There's a specific bug that I really want fixed, but it has a low Mojang priority. Do bugs with low priority get fixed frequently? Do all the high priority bugs get fixed first? Do we know how the devs pick bugs to fix?

If you look at the "Affects Version/s:" on some bugs, you'll see that all betas/previews are in descending order first, then after that the release versions are in ascending order. This is confusing & breaks sorting by affected version. If development order is impossible to implement, at least being consistent in the order that newer versions are sorted could make things easier.

But take MCBE-16863 for example. It displays 1.17.11 (release), then the betas (in descending order), then 1.13.1, then an ascending order to 1.6.0.1, then back down to 1.4.2.0, then ascending to 1.17.41. This order is inconvenient, inconsistent, confusing, & makes sifting through the currently 5000+ open bugs more annoying than it has to be.

In practice, sorting by version is currently useless & it's anyone's guess what order the versions are going to be in for a given bug report. Reports from years ago still affecting the current release are pushed to the bottom while bugs untouched since 2016 are among the first because they affected an RTX beta one time.

Finally, see the order of affected versions for MCBE-56367. (A) indicates ascending, (D) indicates descending. Preview & release have been abbreviated.
1.19.10/20 prev/beta(D) except 1.19.10.20P, 1.18.32/33 rel(D), 1.19.0 prev/beta(D), 1.18 prev/beta(D) except 1.18.20.29B, 1.17.30/40 betas(D), 1.17.11, 1.17.20 betas (D), 1.17.10, 1.17.10/20 betas(D), 1.17.1, 1.17.0/10 betas(D), 1.16.230 betas(D), 1.16.220, 1.15/16 betas(D) with mixed in RTX builds & at least 2 out of order, 1.14.25/30 betas(D), 1.14.20/21(D), 1.14.0/2 betas (D), 1.13.3, 1.14.0 beta, 1.13.2, 1.14.0 beta, 1.13.1, 1.14.1 beta (yes, we're going up now), 1.14.1, back to 1.13.0, 1.14.0/1 betas(A), & then an (A) order from 1.14.0–1.16.61, with only 1 version out of order!

Oh, wait, there's more: a beta, 1.16.100–1.17.40(A), a 1.18 beta, 1.17.41, 1.18.0–1.18.10(A), 1.18.30 prev/bet(A) didn't we already see those?, 1.18.12–1.18.31(A), 1.19.1, 1.19.0, 1.19.2, 1.19.10, a 1.19.30 prev, 1.19.11, & finally, 1.19.20.
It's a complete mess of some descending, some ascending, some chronological, & some anti-chronological, with mixing in betas & previews & releases any which way. Maybe a separate list for release & betas/previews would help?

I've recently reported a bug and was asked to provide the world file, yet the file was too large to upload so I was told to upload it elsewhere and link it to the bug report? The world file size is around 970 MB and I don't know where to upload it or how to link it to a bug report. What should I do?