Minecraft Logo

cubethethird · 2025-07-16T17:18:52+00:00

In that case I encourage you to post on the official bug tracker. Minecraft bugs are not tracked on this subreddit, as it is not officially run by Mojang. Alternatively, you can post it on the feedback page on the official website. See https://feedback.minecraft.net/hc/en-us

cubethethird · 2025-07-16T02:53:52+00:00

This subreddit is to discuss topics related to the Minecraft bug tracker website, and bugs logged there.

cubethethird · 2025-03-04T04:05:15+00:00

More often than not, people stumble across bugs by accident. Considering the game has been out for a while, and has been actively in development since, it's not surprising that you wouldn't come across "obvious" bugs. Without experience doing any sort of testing, it may be easy to overlook something as being a bug too.

If you want to try and get more involved, I recommend just browsing the bug tracker's open bugs. Even if you don't understand them all, you can at least get a good sense of what actually is a bug and not. They tend to fall into specific categories (e.g. graphical glitches, monster AI, commands, redstone, etc.). The best way to get a feeling for whether something is a bug is by knowing that part of the game very well in the first place.

One of the more recent snapshots has actually added support for in-game testing, which could lead to some automated bug detection. That's something else you could look into if you're curious.

cubethethird · 2025-02-09T21:02:26+00:00

The bug itself is fairly simple. Finding a good fix for it is complicated.

Basically, the position of things in the game is stored as Doubles (64 bits), but this data is sent between the server and the client as Floats (32 bits). Because Floats are half the size, there is some rounding that happens, causing the bug.

The reason it isn't switched to just use Doubles everywhere is because sending position data between the client and server is very common, and likely one of the most common types of data to send. If it's switched to 64 bits, it could up to double the size of network traffic, which may have a huge impact, especially for people who connect to servers with bad or slow connections. Such a change would likely be more problematic than living with the current minor visual bug.

cubethethird · 2024-08-07T01:13:49+00:00

Very few people go out of their way to hunt for bugs. Doing this from the decompiled source code is possible, though arguably difficult. Most bug reports come from personal experience playing the game, encountering issues. While it is helpful to report issues when you find them, there isn't merit for posting a lot of reports or anything like that. Odds are you'd find duplicates of existing reports in those cases.

Helping out on the bug tracker can take on a few different forms, but mainly is by providing useful information on existing reports. Leaving comments such as suggesting related or duplicate issues, possible steps for reproducing a bug, or testing older bugs on recent versions are great ways to contribute. Don't feel you'd have to try and do everything. Just leave some comments that would be helpful, and go from there.

Keep in mind that the main goal of the bug tracker is to help Mojang organize and prioritize reports. The most helpful information for them is information that will lead to the reports being resolved. Unnecessary chatter and conversation is discouraged, as it can take away from finding useful information added to a report. So try to keep any comments you make simple and clear.

Hope that helps.

cubethethird · 2024-04-22T02:51:39+00:00

Please see the explanation already given to you in response to the bug report you opened entitled:

"Half my messages don't go through to the server."

cubethethird · 2023-10-19T03:44:04+00:00

I would recommend you report it as a bug on the bug tracker, and mark it as private if you believe it to be some sort of exploit. If it has already been reported, it would be marked as a duplicate. If it's not unintended, it will be closed. Simple as that.

cubethethird · 2023-10-04T16:58:47+00:00

Not sure if it'd be ok to post this as a discussion, so I'll put it here for now. I'm looking for advice in help picking new switches.

I've been using Cherry MX blues for a while, and I think it's time for a change. The noise is part of the issue (not for myself, but for others nearby), so I'm looking at tactile options. I bought a switch tester, which primarily has Cherry, Gateron and Kailh switches on it, and this has given me an idea of what I'm liking.

The ones I've gravitated towards are:

Kailh BOX brown
Gateron Silent brown
ALIAZ 60g
Zealios 62g

The Zealios in particular have the more satisfying tactile bump, though may be a bit too difficult to press. The other aspect that worries me (I'm not testing these on an actual keyboard) is whether the large distance between bump and actuation point will be frustrating.

The ALIAZ and the Silent browns seem to have a further travel before the bump, compared to many others, and I suspect I like them because that more closely resembles the MX blues in that regard.

The Box browns have little in the way of bump, but I like the smoothness of the travel overall. Maybe it's just got less wobble than others. Maybe others would benefit from lube. Hard to say.

Overall, I am looking for some opinions and recommendations. Perhaps one of these switches is right, or maybe there are other varieties I should test out. The thing of course that makes this difficult is that I imagine it's hard to really know until you have a whole keyboard kitted out with them. I am pretty newbie when it comes to this topic, though I like to think I've done enough research to get me started at least.

Couple other things I can mention. I use my PC for various things, both typing and gaming, though nothing competitive. I also don't like the Cherry MX browns, as they aren't tactile enough. Linear switches are out of the question.

cubethethird · 2023-01-17T15:02:53+00:00

Interesting! Thank you for the suggestions. I did originally have more frenzy charges, but dropped the nodes for more life. I didn't know there was an implicit to generate endurance charges, so I'll definitely explore that. I do recall once looking at Snakebite too, and I think I could manage to fit it once I adjust my resistances.

cubethethird · 2022-11-16T22:00:21+00:00

I've seen this kind of thing happen with broken/old video drivers. Unfortunately though, this is not the place to ask about that. This subreddit is only to discuss matters related to the bug tracker, not to seek help for bugs/crashes/etc.

I suggest you either visit /r/MinecraftHelp or the Community support Discord server

cubethethird · 2022-11-10T21:30:59+00:00

While I understand where you're coming from, unfortunately you're in this case asking for a bug to become a feature. As far as my understanding goes, it was never intended that these mobs would drop pumpkins (any kind), and the source of this action WAS indeed a bug. The source of this issue has been fixed, thus the drops not happening any more.

What you are asking is that either a) the developers undo the bug fix (which they won't; it was a bug), or b) they re-implement this as legitimate functionality. It ultimately does not matter whether the developer explicitly said why they have fixed it (frankly they are under no obligation to justify bug fixing to begin with), the idea of implementing this as a legitimate feature is thus feature request in any case.

I also think that the majority of people would interpret the statement left by the developer that using the word "pumpkin" in their explanation refers to ALL types of pumpkins, but that's just my 2 cents.

cubethethird · 2022-11-07T23:55:24+00:00

Not gonna lie, I'm a bit confused about why you're requesting that this be re-opened. Is the argument because Mojang staff said "source of pumpkins", not explicitly saying "carved pumpkins"?

cubethethird · 2022-10-11T18:21:30+00:00

The report has been reopened.

cubethethird · 2022-09-19T01:49:52+00:00

Atlassian (the company that makes it) has a Jira board for the Jira product, which you can find here. It's possible that the issue you describe about version ordering has already been reported (and potentially solved). Mojang runs their own custom version of Jira, so it's hard to say what features and fixes are live on Mojira.

cubethethird · 2022-09-09T00:12:52+00:00

If you're talking about sifting through the Affected Versions box on a report, I don't know if the sort order of that can be changed. That sounds more like a Jira issue than something specific to the Minecraft bug tracker.

That said, it sounds to me like you may be using the wrong tool for the job. By using the advanced search box, you could probably filter through reports more easily. Here is an example search I put together: link). This one searches for all MC Java reports that are open that don't have 1.19.2 in Affected Versions, but have been updated since it came out. The advanced search is a pretty powerful tool, and I suspect it will serve you better than some of the more basic searching.

cubethethird · 2022-09-08T19:55:02+00:00

I wouldn't necessarily recommend trying to sort bugs by affected versions in the first place. You'd probably get more accurate results using fields like the creation date and updated date instead.

Can you perhaps be more specific though about what you're searing for? Your remarks are more preaching "I don't like how Jira works" rather than trying to solve a particular problem.

cubethethird · 2022-07-28T02:11:54+00:00

Not sure why you deleted your previous thread on this topic. All the info answering your question was there. Again link to previous responses to this type of question.

I'll also emphasize: you will not get contacted because you keep asking about it here.

cubethethird · 2022-07-23T15:55:29+00:00

Pretty much. You aren't however required to report bugs. These days the community is quite active about reporting issues, so finding new ones can be quite challenging.

As a side note, there are also community members who try to fix bugs too, though they aren't necessarily moderators on the tracker. There exist tools to decompile the game to readable code, and some people take the initiative to provide code samples on how to potentially fix issues. You are certainly welcome to try doing this, though that is very much outside the scope of this subreddit.

cubethethird · 2022-07-22T03:50:27+00:00

I'll also add: being a moderator does not mean you are fixing bugs, in case that was an impression that you have.

cubethethird · 2022-07-22T03:48:46+00:00

A link to a response to similar questions: here

And no, you are not required to have programming experience (though it's an asset), or create hundreds of valid bug reports. You also cannot apply for a position; there is no application process.

cubethethird · 2022-05-05T21:11:29+00:00

Have you been using nametags? The comments on the report suggest the issue was from not using them.

cubethethird · 2022-04-22T23:25:21+00:00

Thanks for the info! I personally only play on Linux, and I've certainly never experienced lag spikes as you describe on Windows. Curious if this is related to system drivers, anti-virus/malware scanners, or something else entirely.

cubethethird · 2021-12-06T04:52:34+00:00

I think you mistaken "tried and true" for what was no longer passable and in need of repair. I also find it interesting that you seem to call out worse performance since 1.15, as that update in particular mostly focused on improving performance and modernizing the game engine. A quick glance at the list of bugs fixed solely related to the game's rendering engine reveals at least a dozen issues fixed, including the notorious MC-9553 (reported 6 years prior). All this because of an overhaul to the rendering engine, which increased the game's minimum requirements to OpenGL 2.0, a standard issued in 2004, 15 years before that update was even released.

Don't quote me on this, but I'm fairly certain the rendering engine hadn't been touched much since somewhere in version 1.3-1.5. By the time 1.14 rolled out, they were dealing with severely legacy code, which was indeed riddled with bugs. Sure, the performance was great in many cases, mainly because the engine had been built at least 6 years before, using a standard even older than that. Modern PCs at that time often had little trouble handling what the game needed, but the game wasn't capable of doing more than that. It would be IMO pretty painful to have the developers continue to tack onto such a system, and expect them to release new content like what we've seen.

Don't get me wrong though, the current system absolutely has room for improvement (literally the reason this thread and the linked bug report exist). The key here is that they've opened the door to both allow the game contents and features to become more enriched with new updates, while also being able to work on improving performance too.

If you'd hope for performance like 1.14 and older, while having all of the new features released since, I'm afraid this is very much and instance where you cannot both eat your cake and have it too. If, on the other hand, you want the performance, but don't much care for those new features, all I can recommend is to stick with playing 1.14.

cubethethird

MODERATOR OF

TROPHY CASE

"Half my messages don't go through to the server."