This is just the third and most definitely final time I am reporting this bug since 1.13 snapshots/pre-releases because all this time it still still still remained long-standing for an incredibly long time for whatever reason up to the present time. First of all, it was marked as resolved and confirmed in one of my previous bug reports with exactly the same bug recognized, but then it turns out that while that happened it just wasn't able to be fixed in any single version after 1.13, especially such as this week's recent snapshot for 1.16, making us very unsatisfied with such a bug report. So, let me put right into standpoint this visual bug that I've kept on reporting now that the developers don't seem to get the important point of fixing that bug.
Despite this week's snapshot's implementation of the experimental graphical rendering changes being done, along with a whole slew of other visual bugfixes being done at the same time as well, this bug that I'm reporting now appears to be one of the only visual bugs that have not been fixed at all, meaning that it has been completely ignored to be actually fixed while being resolved for some odd reason, thus, like mentioned before, making that bug controversially long-standing since 1.13 versions. Therefore, here's the actual logic behind this bug in not only visual, but also sound, terms, that the developers also didn't get completely:
The bug
The bubble columns that were added and then changed or fixed since 1.13 snapshots had a number of seemingly long-standing visual and sound bugs present in versions after 1.13, in that the two major elements for the columns, including the bubble popping particle (minecraft:bubble_pop) and the bubble popping sound connected to it (minecraft:block.bubble_column.bubble_pop), are missing. What I'm supposed to expect to happen is that the upward bubble columns are supposed to pop realistically when on the surface of the water, producing a bubble popping particle and sound concurrently. What actually happened, on the other hand, was that those bubble columns just rather disappear unrealistically than just popping leading the bubble popping particle and sound along with it to be unused, as evident by one of each of the screenshots shown below that I know of. Here's how it generally goes by clarification:
To reproduce
Build a tube
Fill it up with water
Place soul sand at the bottom of it
Watch the bubble columns resurface
→ ❌ No bubble popping particle or sound is produced
In conclusion, this visual and sound bug has just been remarkably long-standing and thus stringently common for a very while since 1.13 snapshots as it has never been fixed in any present version by any means despite being resolved and confirmed. Therefore, from this point onwards, as we need more realism to the game, this bug should be expected to be fixed before the 1.16 release, or otherwise, we'll keep sacrificing with it or even go hopeless. I hope the developers understand and indeed didn't underestimate this bug while you can.
Linked issues
duplicates 1
Attachments
Comments 6
Don't just count this bug as resolved because later on when one of the 1.16 pre-releases approach with that long-standing visual graphical bug not being fixed or left as it is for a very long time (even though I understand that just because it's resolved doesn't mean it's fixed for real), we will go extra desperate urging this bug to be fixed right away anyway along the series of these pre-releases. It goes without saying (and it is a concern, not an excuse):
WE
WANT
MORE
IN-
GAME
REALISM!!!
It is part of bugfixing after all.
As I have said, "Resolved" does not mean "Fixed" - this issue is being tracked MC-132067, please leave any input there - we do not have multiple tickets open for the same issue.
Maybe this helps:
"Resolved" does not mean "Fixed".
As I've said, I already understand "'Resolved' does not mean 'Fixed'" and already know the contextual difference between those two. However, my fairly important concern (not excuse) for you to note is that we needed to make the game as more realistic as possible by the time 1.16 fully releases so that the rest of the gameplay will go safely and usefully smooth enough for every player without too much sacrifice. Therefore, even though this sounds reasonably common, please don't always leave my bug report resolved for a long time without it being fixed, as evident by this issue tracked, MC-98316, because 1.16 is getting closer and we want these bugs like this fixed right away before the full release (that's a bummer if not). But again, for the hopefully final time (and I am a bit honest), I did take for granted that just because it's resolved doesn't mean it's fixed, and it may or may not mean that it'll be eventually fixed, but regardless, it is a very hopeless decision (unless you think it's okay) to leave a bug like this resolved forever without that eventual fix. So, henceforth, whatever you do, please understand that while "'Resolved' does not mean 'Fixed'," don't always keep it resolved and unfixed forever. You can if you want to but it is less recommended for closer-release reasons, so I beg you a little bit. And remember if you can, we need more realism in the game (i.e. to make the game more sensibly realistic). Other than that, though, thanks for the "RdnmF" sort of suggestion.
This is the ticket your report duplicates, MC-132067. It is not "Resolved", it is "Unresolved", as can be seen here:
[media]
Please understand that "Resolved" does not mean automatically "Fixed", please always read the "Resolution" to find out the current status of your report. In this case, it is a duplicate of another issue, namely MC-132067, which is still not resolved.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki