r/Mojira • • Oct 24 '20

Discussion Why was MC-26678 marked as "Won't Fix?"

461 Upvotes

I'd like to preface my question by saying that I apologize if this is a duplicate question, but I searched and can't find a mention of it in this sub.

I'd like to ask why this bug was marked as "Won't Fix". In my opinion, it adds a nice touch to taking damage, and gives the game a bit more flare. To me, it just makes the game feel a teeny bit better, as someone who's played with the mod that fixes this.

Needless to say, I disagree with how this bug was resolved, considering my opinion, but I'm not intimate with the codebase, so perhaps there are factors at play that I just can't see.


r/Mojira • • Oct 03 '20

Invalid the first 1.17 bug report: axolotl buckets don't have a proper item name

Post image
101 Upvotes

r/Mojira • • Jun 23 '22

Discussion MC-253169 bug report marked as resolved but it's actually a bug.

93 Upvotes

https://bugs.mojang.com/browse/MC-253169

An admin asked me to make a post on this Reddit.

Space characters not loaded correctly if any other unrelated custom "bitmap" character fails to load.

This happens even with the official 1.19 "space" feature which allows creating custom spaces characters, so this IS A BUG, there is no point into marking that as RESOLVED.

Detailed info on how to reproduce the bug:

https://bugs.mojang.com/browse/MC-253169?focusedCommentId=1176073&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1176073


r/Mojira • • Apr 07 '21

Resolved MC-84789 was marked as "Works as Intended," when I think that's a bit of an oversight

71 Upvotes

MC-84789 is about how Wild Wolves don't beg for bones, but tamed ones do. Originally this was the other way around, and it was clearly made like that on purpose. I think there was perhaps a misunderstanding here.

Wild wolves begged for bones because you give them bones to tame them. Tamed Wolves didn't beg for them because it's physically impossible to give a tamed wolf a bone, it just sits if you try. Now they're doing the opposite, so Wild Wolves don't hint you should give them bones and Tamed ones ask for something you can't give them. This clearly can't be intended, right? It had logic behind it before.

I went into more detail in the comments of the bug report, and there's a video of the old behavior there too. It's been broken for about 5 years now and I'd hate to see it just marked as intended.


r/Mojira • • Oct 01 '21

Discussion MC-237493 closed without any explanation

58 Upvotes

https://bugs.mojang.com/browse/MC-237493

TL;DR of the bug: data collection was re-added in 21w38a, but there is currently no way to turn it off nor view what data is actually sent. This actually was a part of the game known as "Snooper Settings" in versions pre-1.13.

The ticket was closed as WAI with no explanation provided.

I fully understand adding telemetry to help aid game development, I also would understand it being an opt-out rather than opt-in (most people don't care to change settings, so there will be a considerably smaller amount of data to work with), but there is absolutely no way to turn it off without modding the game, and that is an issue.

It's not too big of an issue right now, but it can be a slippery slope, and it can be used as a way to build profiles about players (remember Mojang is now owned by Microsoft, which might have some interest in that).

Please reconsider this report, or at the very least, provide a reasonable explanation as to why it's "working as intended".


r/Mojira • • Nov 29 '17

Investigation Fix posted for MC-11193 (redstone nondeterminism) and MC-81098 (redstone lag): Everyone happy with it so far

57 Upvotes

I've spent about a month working on a clean, non-invasive, bolt-on "turbo charger" for redstone lag and other undesirable behaviors. My full report is in A comment on MC-81098, and the optimizations also fix MC-11193 in ways that testers have been very happy with.

Please have a look at the explanation, and please have a look at the code. Even if you're not a coder, I'd like my comments to be easy to understand. This reddit thread would be a good place to ask questions and make suggestions. Feedback from others has already helped me improve my explanations and code comments, and I'd love to get more. And be sure to help me acknowledge all of the people who help me with functional testing.

ilmango is apparently working on another one of his epic machines, which wasn't doable without redstone wire. We're all looking forward to the video! Previously, it had been super laggy, but since Xcom and Gnembon put the new code into carpet mod, ilmango reports to me substantial performance improvement.

Side notes and related thoughts:

I've actually experimented with a LOT of optimization strategies, and this is just one of them. Initially, I went looking at the code critical path in redstone wire depowering, and I found a lot of inefficiencies. For instance, there is code in World that recomputes the same immutable neighbor block positions over and over and over again. I developed a caching strategy for those, and combined with some careful caching of block states (which are expensive to look up) and some tweaks to the way block states are tested in BlockRedstoneWire and World, I was able to double redstone wire performance, with no changes to the original update order. Since these are global optimizations, I decided it would be best to introduce them later and separately.

The block neighbor position caching was an interesting one. BlockPos objects are immutable, so I was able to make a global cache of arrays of neighboring BlockPos objects of recently used positions. I designed it as a direct-mapped cache in a fixed-size array, where I would hash the center block position and look in the table for hits and misses. Even with 65536 entries, though, I couldn't get over 90% hit rate, and there were unused cache entries. A 2-way set associative cache improved that a LOT, but the compute overhead was too much. Well, it turns out that the hash function that comes with Vec3i (the base class of BlockPos) is really crummy, at least for block coordinates. Across the board, I'm sure that using BlockPos objects in sets and for map keys is pretty suboptimal. Based on some realistic distributions of block coordinates for single player and multiplayer scenarios, I did an exhaustive search over prime coefficients (less than 65536) for X, Y, and Z components for hashing coordinates. After that, I got something like a 99.94% hit rate in a direct-mapped cache.

Some of you may remember when the author of Optifine complained about the rate at which BlockPos and a few other objects were allocated. I did experiment with a BlockPos factory that used a cache. The amount of heap allocation and GC went down A LOT, but Mojang's size setting they use for the eden generation of objects outperformed the cache, at least in my limited testing at the time. One useful thing it did do was make tick times a lot more regular.


r/Mojira • • Jul 28 '18

Meta Ask us everything about Mojang's Bug Tracker Mojira!

50 Upvotes

AMA is now over, but you can still ask us anything commenting in this post or creating a new thread!

Ask us helpers and moderators anything about Mojang's bug tracker Mojira! This includes all versions of the game (Bedrock, Java, Console...) and other areas which are covered by the bug tracker, like the Minecraft Launcher and Minecraft Realms.

You can ask us pretty much everythingbut try to keep it on-topic about Mojira.

This event officially ends on August 4th, but you might still get answers from us on this post afterwards, though probably not as fast. Keep in mind that you can create a post in this subreddit at any time if you have a question.

Please respect the following rules:

  • Stay on topic; this post is about Mojira, not about what Minecraft features are planned, etc.

  • For questions about specific reports, please create a separate post here in /r/Mojira or post a comment on that report

  • Don't ask if a certain bug has been reported; use the search function of Mojira for that.

🐞 Mojira -- πŸ“ƒ Reddiquette -- πŸ“– Issue Guidelines -- πŸ’¬ Community Support -- πŸ“§ Customer Support -- πŸ“” Game Wiki


r/Mojira • • Oct 28 '20

Invalid Regarding MC-26678 (Java Edition)

43 Upvotes

I originally got to know about this issue by a video from a YouTuber named "Shivaxi" he made a video awhile ago regarding the minecraft directional camera movement bug. Where he addressed a somewhat small visual bug which has to do with Desync I am pretty sure (so did Shivaxi say in his video) and that in 1.2.5 and earlier, the way this system worked was your camera bobbed in the direction you received damage from. But in 1.3 the way singleplayer worked had changed and now whenever you join a world you basically load into a server I'm pretty sure and that is why it caused the issue. And the code which calculated this (attackedAtYaw) whole process broke, if I am correct in 1.2.5 and earlier this process didn't work in the other multiplayer servers either with that whole logic. Nobody thought much about the issue and eventually it was forgotten about. Then Mojang also never bothered fixing this bug. Everyone thought there was no problem with this system so they even coded it on bedrock so this process works in the same buggy and unintended way and whenever you now get hit and damaged, your camera always tilts in left regardless of which way you are being attacked from. This issue was reported in The Bug Tracker and every request noting this issue was denied and they refused to fix this bug on java edition and also refused to change the way it works on bedrock, too. Not many people now know that the way I mentioned it worked previously before 1.3 was how the system it was originally intended to work in. This will be an easy fix in Java Edition and I also believe the way it works on bedrock could also be changed by implementing a system to calculate the way your camera will bob/tilt in. So basically this bug was resolved and marked as "won't fix" in the bug tracker. I believe they can very easily fix it so why not(as noted by the ways and reasons given earlier) I suck at coding and don't know much about what I'm talking about here from a technical standpoint but here is the video I was mentioning before which addresses this same issue in a more detailed and clear way. Link:- https://youtu.be/pAJPc71YOnY


r/Mojira • • Sep 11 '20

Meta The Minecraft: Java Edition bug tracker has just reached 200,000 reports!

40 Upvotes

Approximately seven years after the bug tracking was moved from being on the Minecraft Wiki to its own fancy JIRA website, we have just reached the milestone of 200,000 reports on the Java Edition bug tracker!

I want to thank everyone involved in the bug tracker - whether it is the developers working through the reports, the moderators and helpers taking the effort to going through reports to check their validity, and especially to everyone who is actually reporting the bugs. Through your actions, you are helping Mojang to improve the game we all love so much.

You may be asking why we are celebrating this - but what this means isn't that the game has 200,000 bugs (as some of you would claim), it means that, for the Java Edition, the community took the effort to report something that they believe is not correct in the game in the hope of getting it solved. Furthermore, through various templates and moderator notes, we are also able to help a tremendous amount of people with their technical and account support issues, either by providing a solution directly or pointing them in the right direction.

Overall, I believe the bug tracker has been a success through and through. So once again, thank you very much everyone, and keep reporting - we won't reach 300,000 without your help! :)


r/Mojira • • Aug 10 '20

Announcement Read before posting: This subreddit is not for bug reports!

38 Upvotes

Please go to https://bugs.mojang.com in order to report bugs!

This subreddit is for discussing bugs that are already reported on the bug tracker as well as the bug tracker itself, since the bug tracker is not a place for discussion.

It is not for reporting bugs. If you have a bug you want to report, please go to the bug tracker to report it!


We also have a Discord server! (Again, not for bug reports, but for discussing bugs already reported to the bug tracker.)


r/Mojira • • May 29 '20

Snapshot Report Snapshot Bugtracker Report - Year 20, Snapshot 22a

37 Upvotes

6 years ago, I took the time every snapshot day to keep a close eye on the bug tracker, and to list all valid bugs reported in the snapshot in a comprehensive list on the /r/minecraft snapshot post - starting today, the report returns due to an overwhelming amount of free time.

If you have any questions, leave a comment. Without further interruption, here it is:


  • 141 new bugs reported after the release of the snapshot (crash bugs are bold, major gameplay affecting bugs are italic, issues named "Private Issue" are private Issues, strikethrough are either fixed, or were marked as resolved but are still noticable)

MC-186062 - Warning "Could not find uniform named InSize in the specified shader program." when loading resources
MC-186064 - Clouds render in front of everything for some users
MC-186067 - Some structures' loot chests do not contain any items
MC-186071 - Clouds are visible and don't render correctly when they are turned off
MC-186074 - Particles render in the wrong order with transparent blocks when using certain graphics cards
MC-186075 - GPU usage in latest snapshot significantly higher than before, causing lag or crash for some users
MC-186078 - Transparent items render in front of transparent blocks on some graphics cards
MC-186079 - Superflat world has dark sky
MC-186080 - Entities, block entities, and items are rendered black on some graphics cards
MC-186084 - Piglin head and torso floats and detaches during celebration dance
MC-186085 - Jumping out of a boat while moving causes problems
MC-186086 - Campfire places cooked item entities intersecting with block
MC-186087 - World Seed reset to "0" after upgrade from one snapshot to another
MC-186088 - Block hitboxes once again cause semi-transparent blocks not to render behind them
MC-186089 - Functions load before entity tags do, causing loading errors.
MC-186091 - When you stop swimming, "diving underwater" sound occurs and vision flashes
MC-186092 - The head of a piglin becomes offset after performing their celebration dance
MC-186093 - Dungeons no longer generate in the same places as they did in previous versions
MC-186095 - Lava fog is dark in Y levels below 61
MC-186096 - Some Sturctures generated pre-20w21a still have no valid Spawns respective mobs does not count towards total because it is Invalid
MC-186097 - Pigs move very slowly
MC-186101 - Some commands in functions cause a NullPointerException
MC-186102 - Piglins that are wielding a sword, pickaxe, shovel, axe or a hoe use vindicator attacking animation
MC-186105 - Rain particles look lighter than they should
MC-186108 - Enchantment glint does not render on dropped/thrown items
MC-186109 - You can use multiplayer commands on a singleplayer world
MC-186111 - Debug mode is accessible in any gamemode
MC-186119 - Endermen get the wither effect when dodging wither skulls
MC-186123 - Piglin and Zombified Piglin right arm/leg/loincloth textures are identical to the left ones
MC-186124 - Lightning bolt doesn't render
MC-186127 - Compass' needle has no animation when changing the setworldspawn.
MC-186131 - Piglins and Hoglins cannot spawn naturally in peaceful
MC-186148 - "death.attack.witherSkull.item" displays raw translation string (is untranslated)
MC-186149 - "Debug Mode" world causes error on world list
MC-186169 - Water streams not transporting items flowing over hoppers between streams
MC-186172 - Shulkers open into blocks when unable to teleport
MC-186178 - Some data pack errors are confusing, including duplicated and unnecessary info
MC-186181 - Able to place a Dead Bush on Terracotta
MC-186183 - Shulkers open into other shulkers when unable to teleport
MC-186184 - Villagers can claim workstations at night time if workstation is right next to a bed
MC-186189 - Chunk generation of Worldgen has discontinuities in 20w22a when upgrading from 20w21a
MC-186190 - Errors from worldgen settings are extremely verbose
MC-186193 - Villager neck is inconsistent with other necks in-game
MC-186196 - Dead Bush able to generate on village terracotta
MC-186199 - Json data pack validation errors don't show line numbers
MC-186204 - Items render in front of other entities
MC-186206 - Water tinted rendered differently behind glass top versus sides
MC-186228 - Zombified Piglins' sleeve layers are not held upwards like their arms
MC-186241 - World border is rendered incorrectly
MC-186248 - "m" in Safe Mode button isn't capitalized
MC-186249 - Villagers are sleeping below the bed
MC-186253 - Held translucent blocks make the water, clouds, particles, and placed translucent blocks behind them invisible in third person mode.
MC-186263 - "b" & "l" in Create Backup & Load isn't capitalized
MC-186264 - "k" & "d" isn't capitalized in "I know what I'm doing" button
MC-186274 - Purple light from Ender Dragon's Death doesn't appear
MC-186284 - Player's point of view is upside down in 20w22a
MC-186311 - Piglin dance only occurs when they kill a Hoglin
MC-186314 - Villagers become fixated on potential job site
MC-186320 - Llama spit doesn't damage the player when the player is standing right in front of the llama's head.
MC-186335 - Bees age calculation inside hive/nest is broken
MC-186337 - The lighting of the "Client" doesn't correspond to that of the "Server"
MC-186343 - Dungeon intersects mineshaft
MC-186353 - The "s" and "m" in "Edit sign message" are uncapitalized
MC-186362 - Casting issue: Translucent block rendering breaks down after 16,777,216 blocks
MC-186398 - Basalt Pillars and Large Fungi Have Issues Generating Near Each Other
MC-186403 - Swimming up on the side of flowing water no longer prevents the player from drowning
MC-186420 - Lava deltas can generate inside of Bastion Remnants
MC-186455 - Persistent villagers without experience can despawn after converting to a witch
MC-186464 - Enabled data packs still show up in the "/datapack enable" list
MC-186468 - Although reload failed, the game will also tell you "Disable data pack [XXX]".
MC-186478 - Tag minecraft:tick doesn't work when joining a world
MC-186480 - Inner parts of slime blocks and honey blocks disappear again while the block is moved by a piston
MC-186492 - Lily pad placement in creative mode causes item on hotbar to flicker/vanish
MC-186503 - loot_table condition for player_generates_container_loot trigger is not optional
MC-186518 - Piglin slides their heads from side to side when a different group of piglins starts dancing
MC-186525 - Villagers look at a workstation they want to claim even if they are β€œtalking” to another villager at the moment
MC-186538 - Transparent blocks cause clouds to not render in front of them when looking through transparent blocks
MC-186546 - Endermen that have been turned hostile by other means than looking at them will turn neutral when looked at
MC-186596 - Able to spawn mobs within fences using spawn eggs
MC-186600 - Nether gold ore is gray on a map
MC-186601 - Certain faces of blocks are transparent, causing player to see through the world
MC-186614 - New Nether mobs make too many noises under certain circumstances
MC-186617 - Zombified piglins sound angry too many times when hit constantly
MC-186626 - /weather not working in custom dimensions
MC-186627 - Undead mobs do not burn in daylight in custom dimensions
MC-186631 - Shulker box not entering a hopper that it was being pushed to
MC-186647 - Villager price changes are extremely inconsistent, and completely break in combination with hero of the village
MC-186687 - Death message for being shot by a Wither Skull does not fit for all entities
MC-186690 - Mobs getting stuck in composters/cauldrons if there is air beneath them
MC-186695 - Eight misrotated blocks in savanna_small_house_7
MC-186696 - Totem of Undying causes red or blue tint in the screen
MC-186697 - Misrotated roof log at taiga_small_house_4
MC-186720 - Transparent Window with 10bpc on Xorg
MC-186733 - Riptide animation not showing in general when using too fast
MC-186734 - Zombified Piglin spawning on low y-levels
MC-186739 - Mobs on the same team as players becoming hostile when a player receives the instant health effect
MC-186756 - Entering a boat in water causes the held item to be used
MC-186770 - Switching from weapon to empty hand or vice-versa in Creative Mode while breaking a block desyncs sound and particles from items dropping
MC-186794 - Standing on a bed with a trapdoor above you allows you to temporarily float
MC-186797 - Functioning clock and compass in crafting output slot
MC-186823 - Grass paths don't decay underwater, despite being similar to grass
MC-186844 - Librarian and cartographer trade loop
MC-186848 - The librarian can hold functioning clocks and compasses
MC-186849 - Librarian trading output has functional clocks and compasses
MC-186851 - "death.attack.sting.item" displays raw translation string (is untranslated)
MC-186857 - "/datapack disable" shows success message after a data pack is disabled rather than after it is run, causing inconsistencies with "/datapack enable"
MC-186864 - Leather armour can appear white
MC-186879 - Standing in fire and water spams the extinguish sound
MC-186905 - "Superflat Customization" screen resets every time you open it and does not show previously saved settings
MC-186909 - Hand animation plays more than once when constantly right-clicking on a Creeper/Charged Creeper and Flint and Steel uses more durability
MC-186916 - There are unused strings in en_us.json
MC-186917 - The NBT tag "BeamTarget" from End Crystals does not allow decimal values
MC-186958 - Zombie reinforcements spawn on magma blocks
MC-186963 - Spreadplayers drops tps when used in an area with a lot of invalid blocks
MC-186972 - Dragon breath does inconsistent damage depending on the source
MC-186975 - The dragon is not properly centered on the portal
MC-187009 - Ruined portals can spawn in villages
MC-187015 - Hitting mob and quickly switching item doesn't reduce tools durability
MC-187016 - Array of furnaces loosing items
MC-187031 - Piglin swinging animation does not match attacking or targeting animation
MC-187069 - Visible Boss Bars appear empty upon restarting the game.
MC-187100 - End crystals try to heal dying Ender dragons
MC-187112 - Extra space in "Keep Jigsaws" button in jigsaw block
MC-187117 - Settings are not saved when exiting jigsaw block
MC-187123 - No error message when trying to generate from a nonexistent target pool
MC-187124 - No success message after generating from a jigsaw block
MC-187125 - Jigsaw block generation can create ghost blocks
MC-187126 - Jigsaw block UI is not closed when pressing "Generate"
MC-187129 - Jigsaw blocks do not generate the correct structure until "Done" is pressed and the UI is reopened
MC-187131 - Jigsaw block generation allows leaves to be replaced by path blocks
MC-187151 - Wither health bar does not update when the Wither is killed
MC-187174 - Worldborder does not take nether coordinates into account
MC-187188 - Painting NBT and registry contain a typo "Motive" instead of "Motif"
MC-187215 - Zombies with "CanBreakDoors" NBT rarely use their breaking doors ability
MC-187217 - Iron nuggets still using pre-texture update texture
MC-187243 - Parity: Lodestone compasses are distinct items in BE, but not JE
MC-187262 - Worldgen json ignores seed in custom dimensions
MC-187267 - Title text renders in front of sidebar
MC-187281 - Function reward removing the item an advancement detected creates a ghost item
MC-187282 - Spectator Mode | Name visible inside entities
MC-187306 - Breaking some block-like entities does not lower item's durability
MC-187307 - When switching from spectator to another gamemode after switching to spectator while in Lava causes player to be on fire

If you found a bug and you are not sure whether it has already been created or not, ask here.

End-of-Snapshot-Day Report

At this moment, I do not recommend to use this snapshot in your regular playthrough of the game. This is due to the broken loot tables for many structures. There are also some performance issues for some users.

20w22a ~ 1.16 Pre-release 1 ~ 1.16 Pre-release 2


r/Mojira • • Jul 04 '20

Meta Mojira AMA

36 Upvotes

Ask us helpers and moderators anything about Mojang's bug tracker Mojira! This includes all versions of the game (Bedrock, Java, Earth, Dungeons, Console...) and other areas which are covered by the bug tracker, like the Minecraft Launcher and Minecraft Realms.

You can ask us pretty much everythingbut try to keep it on-topic about Mojira.

This event will start on July 4th at 10AM CEST and last 24 hours, but you might still get answers from us on this post afterwards, though probably not as fast. Keep in mind that you can create a post in this subreddit or ask in our discord at any time if you have a question.

In your timezone: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Mojira+AMA&iso=20200704T10&p1=31

Please respect the following rules:

- Stay on topic; this post is about Mojira, not about what Minecraft features are planned, etc.

- For questions about specific reports, please create a separate post here in /r/Mojira or post a comment on that report

- Don't ask if a certain bug has been reported; use the search function of Mojira for that.

It will also be the birthday of 2 of our mods :D

🐞 Mojira -- πŸ’¬ Discord -- πŸ“ƒ Reddiquette -- πŸ“– Issue Guidelines -- πŸ’¬ Community Support -- πŸ“§ Customer Support -- πŸ“” Game Wiki


r/Mojira • • Jan 03 '21

Invalid bug

Post image
35 Upvotes

r/Mojira • • Jun 06 '18

Discussion Top 11 most critical bugs in Minecraft 1.13

35 Upvotes

I'm quite obviously biased towards the tech community, so I'm sure that others (e.g. builders, PvP, etc.) would have their own lists. But my friends and I have worked hard to compile a list of bugs, sort them by priority, and cut them down to the most serious. I like to acknowledge those who have helped, but too many people have contributed for me to do them justice. The list(s) are below.

UPDATE: Make that "top 12." One of the bugs was still under debate as to whether or not we should include it.

UPDATE: Ok, make that "top 13." We left out MC-2025 due to rumors that it had been fixed. We can't find any evidence for that in the decompiled code for 1.13-pre1, so I have developed a dead-simple fix for it, and I'll post it to Mojira after some further testing.

UPDATE: Added mention of how MC-130858 breaks things for builders too.

UPDATE: MC-2025 fix is ready: Reddit post, Mojira comment.

GOOD NEWS! MC-130722 and MC-130858 have been fixed! Many ❀️'s to Mojang!

Critical 1.13 bugs:

Bug numberMojira linkShort descriptionJustification
MC-130722https://bugs.mojang.com/browse/MC-130722Slime block diffuse skylight.Different from 1.12.2, causes excessive lag when moved
MC-130858https://bugs.mojang.com/browse/MC-130858Pistons are no longer transparentDifferent from 1.12.2, causes excessive lag when moved. Builders have used pistons to hide lights ever since they were introduced.
MC-128926https://bugs.mojang.com/browse/MC-128926Wrong observer timings
MC-126038https://bugs.mojang.com/browse/MC-126038Observers getting moved in "on" state rather than "off" state
MC-126769https://bugs.mojang.com/browse/MC-126769Observers detecting updates from redstone on top of them
MC-126595https://bugs.mojang.com/browse/MC-126595Blue Wither heads are intangible and invincible on the first tick
MC-126461https://bugs.mojang.com/browse/MC-126461When multiple minecarts in the same block are pushed by a piston they don't all move

Pre-1.13 bugs that are highly critical:

Bug numberMojira linkShort descriptionJustification
MC-119971https://bugs.mojang.com/browse/MC-119971Various duplications, deletions, and data corruption at chunk boundaries, caused by loading outdated chunks β€” includes duping and deletion of entities/mobs, items in hoppers, and blocks moved by pistons, among other problemsFix available on Mojira
MC-108469https://bugs.mojang.com/browse/MC-108469Chunk-wise entity lists often don't get updated correctlyFix available on Mojira
MC-54026https://bugs.mojang.com/browse/MC-54026Blocks attached to slime blocks can create ghost blocksFix available on Mojira
MC-119994https://bugs.mojang.com/browse/MC-119994Fires in the nether cause chunks to permanently load and cause lagFix available on Mojira
MC-122976https://bugs.mojang.com/browse/MC-122976Server Watchdog shuts down the server even running above 1 TPSFix available on Mojira
MC-2025https://bugs.mojang.com/browse/MC-2025Mobs going out of fenced areas/suffocate in blocks when loading chunksFix available on Mojira

r/Mojira • • Nov 05 '20

Invalid Amethyst crystals rapidly duplicate from clusters attached to moving slime blocks

32 Upvotes

r/Mojira • • Apr 28 '20

Meta From now on, we'll accept bug reports about certain parity issues on the bug tracker!

30 Upvotes

We now accept bug reports about vanilla parity issues on the bug tracker!

Parity issues are differences in the behavior of gameplay features between the Bedrock Edition and the Java Edition of the game.

However, we only accept bug reports about a parity issue if it fulfills the following criteria:

  • The feature affected by the parity issue is present in both Bedrock Edition and Java Edition in the latest release or development version

  • The feature behaves differently in one edition than in the other

  • The parity issue was introduced in Buzzy Bees (Bedrock Edition 1.14 / Java Edition 1.15) or later and was not present before

Any parity issues that do not fulfill these criteria should be posted on the feedback site and/or collected on the wiki page instead.

Please report parity issues matching the criteria above to the Java Edition (MC) project, the Bedrock Edition (MCPE) project, or both (whichever seems more appropriate), and assign the vanilla-parity label to it. Parity issue bug reports on the Java Edition project will additionally be assigned to the "Parity" category by a moderator.

The workflow regarding parity issue reports is as follows:

  • When a parity issue is solved by tweaking the behavior in the edition it was reported for, the parity issue report will be resolved as "Fixed" as usual.

  • If the reported behavior is deemed to be correct in the edition it was reported for, the report will be closed, and a new corresponding report will be opened on the other project (unless it already exists).

  • In case Mojang decides not to fix the reported parity issue, the report will be closed, and the feedback site is to be used to discuss that issue instead.

If a parity issue has been reported on both the Bedrock Edition and the Java Edition project, the two reports will be linked as related.


r/Mojira • • Jul 09 '21

Investigation Counter-examples for MCPE-21416 (despawning entities)

29 Upvotes

https://bugs.mojang.com/browse/MCPE-21416

(Edit to add for those not familiar with the bug or who didn't click the link: this is a BEDROCK ONLY issue.)

The above bug was reported four years ago and is currently the highest-voted bug in the Bedrock list, as far as I can tell. There are hundreds of reports in the comment list and a lot of good theories, suppositions, and guesses about what is going on. What there isn't is any discussion about people not experiencing this bug because...why would those players even be over there?

Is this a case where it's a minority of Bedrock users who ever encounter the bug, but nevertheless have managed to vote it to the top? Or do a majority of users encounter it, and like with most bugs only a few end up finding the Jira site and reporting?

So I wanted to ask the broader community here if any of you:

A) Play Bedrock Edition

B) Engage in entity-collecting behavior (villagers, farms, pets, minecarts, armor stands, etc.)

and

B) Have never noticed a loss of interacted-with/named entities under unexplained circumstances (i.e. obviously not hostile attack, lightning, wandered off a cliff, etc.)

If there are a good number of players who have never encountered this bug, maybe we can figure out what they're doing differently from those of us repeatedly whacked by this bug.

I stopped playing Minecraft about 2 years ago after losing my second set of high-level traders along with all my cows and sheep. It was my favorite game at the time, but with my play style the bug is a game killer. The Jira report has gotten nowhere in spite of the efforts put in by players and moderators (17.1 seems like it might be even worse in fact) so I'm hoping we can uncover some truly new information here, by talking with players who have avoided any Great Disappearances.

The poll is just to collect some very rough idea of the breakout. It is asking about unexplained entity loss. As in, log out with a full village, log back in and half of them are gone. Horses disappeared with their lead still tied to the fence post. Hopper minecart doin' minecart things until suddenly it's not there any more. Good enough for an episode of Unexplained Mysteries or The X-Files.

52 votes, Jul 14 '21
10 I HAVE lost entities and I DID report to the Bug Tracker
18 I HAVE lost entities but I DID NOT report to the Bug Tracker
7 I HAVE NOT lost entities
17 I'm not sure/I don't interact with entities

r/Mojira • • Jun 08 '18

Investigation Final and proper fix to MC-2025 (simple, reliable, and mathematically correct), posted to Mojira

29 Upvotes

MC-2025 is dead, or it should be. Someone named Kademlia figured out the correct solution TWO YEARS AGO. About a year ago, I figured out the underlying cause (IEEE floating point rounding artifacts). Then we spent the the next year arguing about better solutions. The one Kademlia suggested is the correct one, and it should have been implemented that way a long time ago.

Important: The Mojira entry is over-spammed, so this reddit post is to serve as the only place for further discussion. However, as far as I am concerned, the discussion should be over.

History and obsolesce of other solutions

I have added strikethrough to my recent work on MC-2025 that addresses the rounding error problem directly. That solution is unnecessarily complex and has no real advantage over the solution presented here. I was comfortable tinkering with alternate solutions because I'd heard rumors that MC-2025 had already been fixed. But we can't find any evidence of a fix from decompiling 1.13-pre1, so it's time for us to get practical.

Along with plenty of other people, I, Xcom, and MrGrim (Michael Kreitzer), and Kademlia came up with basically the same solution independently. Xcom's has been in Carpet Mod for ages, and MrGrim has been using it in his own custom JAR for probably about as long. We should all be really embarrassed that Kademlia figured it out about two years ago, well before any of the rest of us, but we basically ignored it and argued. (Links to comments at the end of this post.)

Edit: Even more embarrassing, apparently Wolfie Mario proposed this same fix in 2013. We joke about 5-year-old bugs in Minecraft, but this is a 5-year-old FIX. See links below.

Floating point is never exact anyway

Here is what people have to understand about this bug. There is no and can never be perfect stability in axis-aligned bounding box (AABB) dimensions. The exact size of the AABB depends on where in the world the entity is located, due to limits of floating point precision. To begin with, the typical mob width is 0.6, which is (a) not representable in floating point, and (b) stored as a 32-bit float, so when converted to double-precision, you get something more like 0.6000000238418579. However, it's not particularly important that it's this weird number. I demonstrated in a comment on my last reddit post that even something that you can store exactly in floating point (e.g. 0.59375) is just as vulnerable to rounding drift. I had developed a method for computing center coordinates and AABB faces so that they are losslessly inter-convertible, but the AABB dimensions end up varying from 0.6000000238418579 depending on the world coordinates, so you basically never get an AABB of that size in the first place.

What causes MC-2025?

The underlying cause of MC-2025 is that sometimes an AABB ends up slightly smaller than the desired width. If this happens before the entity is pushed up against a boundary (i.e. blocks or walls), then upon chunk save and reload, the AABB size will be recomputed such that it is intersecting the wall, allowing the entity to be pushed into the wall, suffocate, and die. You can see my Mojira comment and previous /r/mojira post for what the numbers looks like. Although the rounding artifacts get larger at larger world coordinates, the drift we see is miniscule. Closer to the world origin, we have seen error on the order of 2-46. Compare this to the fact that (due to MC-4), entity coordinates send to clients are quantized to multiples of 1/4096 (2-12).

But, OMG, do the rounding errors mean that AABB's accumulate shrinkage over time? Actually, no. The statistics on IEEE rounding do not have that kind of bias. What has not been stated is that the AABB is just as likely to end up larger than the expected width; on save and reload, the entity ends up slightly away from the wall, and we don't notice any problem. In reality, the AABB size ends up undergoing random wobble around the expected value all the time, and that wobble isn't functionally any different from the kind we'd get even if we tried to force the AABB size to be stable!

This reasoning leads us to one clear conclusion: The simplest, least invasive, and most correct solution is to just store the AABB in NBT data on chunk save and restore the AABB exactly as it was saved upon reload. The solution is as follows.

Solution to MC-2025

Based on MCP symbols for 1.12.2, the following methods on Entity need to be modified:

  • public NBTTagCompound writeToNBT(NBTTagCompound compound)

  • public void readFromNBT(NBTTagCompound compound)

Saving the AABB on chunk unload

In writeToNBT, somewhere within the try block, do the following:

AxisAlignedBB aabb = this.getEntityBoundingBox();
compound.setTag("AABB", this.newDoubleNBTList(
    aabb.minX, aabb.minY, aabb.minZ, aabb.maxX, aabb.maxY, aabb.maxZ));

Restoring the AABB after chunk reload

There are two places in readFromNBT that call setPosition, which resets the AABB based on entity width. It is very important that this new code be inserted after those calls. This needs to be the very last thing inside of the try block.

So right after this:

if (this.shouldSetPosAfterLoading())
{                
    this.setPosition(this.posX, this.posY, this.posZ);
}

Insert this code:

if (compound.hasKey("AABB")) {
    NBTTagList aabb = compound.getTagList("AABB", 6);
    this.setEntityBoundingBox(new AxisAlignedBB(aabb.getDoubleAt(0), aabb.getDoubleAt(1),
                                                aabb.getDoubleAt(2), aabb.getDoubleAt(3),
                                                aabb.getDoubleAt(4), aabb.getDoubleAt(5)));
}            

Note: If you load an old world that lacks the Entity AABB tags, some entities will be loaded with bad bounding boxes, and they may get pushed into walls. The reason for not proactively fixing those cases is that people have been known to decoratively encase mobs inside of glass blocks, and we shouldn't break that. However, from that point on, the saved AABB will be used, and entities will never again get accidentally lost inside of walls.

Links


r/Mojira • • Nov 27 '17

Invalid MC-4923: we need a replacement for this behaviour

29 Upvotes

1-tick fire blocks were previously used to manually activate BUD's and observers. This was used to start/stop flying machines (placing blocks is often not a viable option) or activate piston doors.

Please consider readding this feature. As far as I can tell it had no downsides and doesn't clash with any other game behaviour. Alternatively add an intended replacement.

edit: link


r/Mojira • • Aug 23 '23

Discussion [WEB-1429] Old Authentication servers for legacy versions are offline

27 Upvotes

[WEB-1429] Old Authentication servers for legacy versions are offline

Since we have been requested to move here, I have decided to start this "master discussion thread" for this issue. Since the issue has received many redundant comments, admittedly from me too.


r/Mojira • • Nov 18 '21

Question What is the weirdest valid bug you've seen on the bug tracker?

27 Upvotes

Just saw a post here about MC-240774, in which half a door will clear the NBT of a banner

Out of all the valid bugs (Could be the fixed ones) which one is the weirdest one you've seen?


r/Mojira • • Jun 09 '21

Resolved Request to re-open MC-208735

27 Upvotes

MC-208735 was marked as fixed in 21w20a, but it isn't. The bug describes a flaw in axolotl pathfinding: they try to pathfind to the nearest water source, even if they cannot reach that water source. This happens even if there is another water source that is accessible, just farther away, and results in the axolotl drying out and dying. The only thing that was changed in 21w20a is that the axolotls don't spin around anymore; they still try to reach the nearest water source, even if that water source is one they can't actually pathfind to. And they still die from it. Occasionally the axolotls will turn to walk away, as if they're pathfinding somewhere else, but they always turn around after a few seconds and try to go back to the water they can't reach. It can still be reproduced following the same steps, and I've otherwise already updated the description to remove mention of them spinning.

Edit: new bug report is here, if anyone's curious: https://bugs.mojang.com/browse/MC-228464


r/Mojira • • Sep 11 '17

Discussion Rays Works, his server crashing bug, and empathy between developers and community

26 Upvotes

I am going to leave it to others to debate the ethics of Ray posting his video. It's a dangerous exploit, and now we're going to have griefers crashing servers all over the world until this bug gets patched. This is going to suck.

However, if you have the patience to read on, I make an argument that to the typical technical minecrafter, what Ray did was the best way he could possibly have handled this, and something I saw him say suggested to me that he knew he was going to get a lot of criticism but was willing to take a beating to serve the greater good. How could making it easier for hackers be "for the greater good"? And why would Ray feel he was having to make a personal sacrifice in order to do this? Read on...

Prologue: Mojang devs deserve far more empathy and credit than they get

Before I get into the nitty gritty, let me be clear that I offer no actual criticism to Mojang developers. They were known awesome developers before they were hired, they're cool people, there are only a handful of them, and they have a LOT of work to do. There are many millions of Minecraft users who comprise many different communities, and Mojang are working to appeal to the majority, because they are a BUSINESS, and they only make more revenue when they get more users. I'm sure Realms makes some decent revenue, but most of us pay only once, and then we expect years upon years of new features and update. On top of that, Mojang developers suffer all kinds of abuse. I've even heard about death threats. That's on top of massive pressure they get to fix some really challenging bugs, as if those bugs were like not a big deal or something.

Minecraft bugs vs. technical users

I've posted fixes to a couple Minecraft bugs, and I'm hopeful those will be adopted. One reason I did that is because I am aware that I am a small part of a very very tiny sub-community of "Hard Core Technical" Minecrafters. From Mojang's perspective technically-inclined Minecrafters do bring in some positive attention. People like Xisuma, Mumbo, Tango, Impulse, Panda, Gnembon, and others don't corner the market on youtube content, but they do suck a lot of adults into the game who bring their kids along for the ride. At the same time, some of these technical minecrafters make a big stink sometimes, and negative attention can have a snowball effect. And the stink they (and I should include myself in this because I have been dumb enough to make some negative comments before I understood things better) make is awfully big for the size of their community. The bugs that drive people nuts in the technical community have essentially no impact on anyone else. You think blocks being deleted at chunk boundaries is going to affect Bed Wars?

So this is perspective. I feel motivated to fix bugs for a lot of reasons. I'm good at it, I enjoy it, I love Minecraft, etc. But Mojang developers have a lot on their plates. Bugs that bother a small minority of users logically cannot get top priority. As a tiny fish in a huge pond, I feel the only reasonable solution is to fix the bugs myself. So I fixed a few, and Gnembon put them into carpetmod, and now people can use them. At the same time, Mojang developers cannot simply take my fixes and plop it into Minecraft. Besides "Who the hell is this theosib dude? Isn't he the one who annoyed Dinnerbone in IRC?", it's not obvious what all the side-effects will be. Maybe after I've posted a few dozen, and the devs get confident that I know the codebase well enough to account for the side-effects, things will be different. But so far, I've posted only two patches that fix only a handful of obscure bugs pertaining to rare timing conditions when chunks load and unload.

Bug busting is no picnic.

I do want to say that fixing those bugs was not easy. I have been coding since the late 1970s, I have been in software engineering professionally for over 20 years, and I have a PhD in computer engineering. People are not taught to debug; they only pick it up after years of hard work. And to be sure, I'm not such big stuff: There's a whole community out there of "bug busters," and discovering that existence, I find that there's a great deal I can learn from them. Anyhow, to try not to make this story too long, the bug pertaining to hoppers duping items is nowhere near any hopper-related code. It's much higher up in the call tree. To dupe items, you have to get a chunk to unload and get reloaded on the same game tick, at the same time that a hopper's cooldown timer expires and it wants to push an item. Only after seeing Gnembon's video on this was I able to create a simplified test rig, and it would take hours upon ours of AFKing in a minecart (to load and unload some chunks containing hopper pairs) to reproduce it. But that's not enough. Then I had to catch it in the act, so I implemented a logging system, and it took me several tries to correctly implement a heuristic to catch the duping in action, triggering the log dump. I found that for an instant, there would be two of the same hopper pushing the same item at around the same time. The fix I posted to Mojira is deceptively simple, because this was a pain in the butt to figure out.

But let's compare isolated MCP users to Mojang developers.

ME: I do have a demanding day job, along with plenty of side consulting work, but I play Minecraft and worked on these bugs to de-stress. I could fix the bugs or not fix the bugs, and there would be nobody to yell at me about it. These bugs were very interesting to me, and I felt motivated to work on them specifically. I also happened to get a little bit of free time after the kids were in bed.

MOJANG DEVS: They have primarily new features they have to work on, and that takes up most of their time. This is their main job, and if they don't perform on the work their bosses tell them to do, there will be problems for them. Moreover, even when they do do a good job, they still get yelled at by ridiculous numbers of people in their user community. When a long day of development work is done, there isn't a lot of time and energy left to fix bugs that affect a small number of users. And don't forget that every time they fix something, they get yelled at by people whose work is broken by the fix, even in snapshots!

Being a celebrity can be bad for your health

Being a Mojang developer is no different from being a rock star or other celebrity. Imagine what it's like to have millions of fans. That's wonderful. But a little negativity can wreck a hell of a lot of positive attention. Imagine what it's like to be the target of thousands of professional critics who spend their days nit-picking every little thing you do, down to how much salt you put on your eggs in the morning. This is life at Mojang. This is why Notch left. This is why so many celebrities start taking narcotics.

Just to survive, Mojang developers put up walls against the world, to shut out all the negativity. And this wall applies no more and no less to loud and entitled technical users. They feel that because they're smarter that they should have special priority, but negativity is negativity, and our friends at Mojang just don't need more of it! They face an onslaught of criticism from thousands of people who feel entitled to their demands, and there's no way for the developers to separate out any small bits of potentially useful criticism from the massive amounts of useless garbage.

And then there's the hard-core technical community.

I can't speak for everyone, but I did not think all of this through when I first got involved in technical Minecraft. I would build complex contraptions, only to find them wrecked by game bugs. When I would go to report the bugs, I would discover that some had been in the game for years. Thinking only of what I was interested in, I wanted to know what kind of messed up priorities were at work here, and I said some unkind things on Mojira (that I haven't deleted since I don't feel I should go around hiding my mistakes). Fortunately, a veteran Minecraft user (Meri) who does understand Mojang was patient and forthright enough to straighten me out. In retrospect, I may have used bigger words, but how was I a lot different from these kids who flame them for creepers blowing up their precious creations?

So let's get back to Ray.

This Mojang wall has the unfortunate consequence of making people in this technical community feel systematically ignored. To them, posting bugs on Mojira is essentially useless. I think it's more a flaw in Mojira's code than anything else, but once a bug is posted, and the moderators (who have a crap ton of work to do too) have verified it, there is absolutely no indication at all that any of the developers are aware of the bug. This is because there no way to make this indication. But to the technical users, Mojira is black hole. Indeed, in their experience, the only way to get a bug fixed is to make a huge stink about it. One example comes from a Gnembon video where he talked about a bug with hoppers and brewing stations. Now, Gnembon wasn't trying to make a big deal out of it or cause any trouble, but the fact that he included a link in his video description got the bug a lot of votes on Mojira, and a few months later, it got fixed. In the minds of many technical users, they firmly believe that if it had not been for Gnembon's video, that bug would still be unfixed. That's probably not true (although I'm sure the votes helped), but that is what they believe. And to be sure, Gnembon's is not the only case like this. Some of Panda4994's videos have lead to bug tracker votes and subsequently fixes, and it is a firmly held belief that those videos were instrumental in getting the bugs fixed.

What's the best way to report bugs to Mojang?

As a result of this belief that only media attention will get bugs fixed, more technical users have turned to youtube to bring attention to these bugs. ilmango's "bug of the week" series is one example. Rays Works' recent video is just another. Like I say, you can debate the ethics of this all you want. All I can tell you is what I perceive to be going on in Ray's mind, although I have not asked him to be sure.

Regardless of what really goes on inside Mojang, these antagonistic beliefs are reality within the community. Quoting anonymously a technical user on Discord, "They're working on 1.12.2 today, and there's a very high chance they're doing it to fix that bug lol. Without rays video they probably would have just made the bug private and not do anything."

So I believe the main motivation to make the video was that Ray felt he was using the only effective means possible to get Mojang developers to become aware of this bug. I believe he felt he was doing a service to the community as a whole to bring enough attention to a serious problem that Mojang would see fit to fix it. And Ray has already indicated that he was perfectly willing to accept the inevitable criticism he would receive, in order to serve his friends in the Minecraft community.

It gets worse. When Mojira moderators hid the bug (which was the right thing to do, BTW), the community reaction was one of paranoia. People were making comments that suggested Mojang wanted to cover it up and ignore it rather than fix it. And then there are twitter comments from Slicedlime and Searge, criticizing Ray for his video. What they said is technically correct, but it is only further polarizing the community, because it's basically saying that Ray was being a jerk for trying to be helpful.

What can we do about this?

I have no idea how to get the technical community to understand that Mojang developers are busy, hard-working people making rational decisions about how they spend their time at work. And I have no idea how to get people at Mojang to understand what's going through the minds of technical users who feel their frustrations are falling on deaf ears.

How do you convince people that others are not evil and that we all just need to learn some empathy?

Epilogue: Ray's dragon videos have nothing to do this.

I need to preempt what some people are going to say about Ray and his dragon videos that "ripped off Panda4994." I come from an academic community where properly citing related work is as important as personal hygiene. Where I come from, I believe Ray could have done a better job of citing Panda. However, youtube is NOT a peer-reviewed venue, and in general, most youtubers do a lousy job of citing similar projects from the past. Why is Ray getting all this flak for doing no worse than so many other content creators? The criticism Ray received for his dragon videos came two things. One was the title of his second video, although the title is technically correct. The other is that he failed to cite a beloved veteran in the Minecraft community who had done something very similar years earlier. To some people, not knowing about Panda4994 is bizarre. I certainly know about and idolize Panda. But Ray didn't initially know about Panda or his prior dragon video and still didn't really understand how important Panda has been in the community when Ray made his second video (where he did cite Panda). Coming back to this idea of empathy, I would like people to understand that Ray was not by any means intending to rip anyone off or give insult one of the most cherished members of the Minecraft community. He just made a video about something he did, which is an XP farm faster than other kinds of XP farms due to dragons dropping higher-XP orbs. (It is also, incidentally, faster than Panda's farm, but Ray apparently didn't realize there had been other dragon XP farms, so he wasn't comparing to them.)

Regardless of what Ray may have actually been thinking, the community reaction was swift and venomous. Yes, he made a social faux pas. Should he get this much of a pounding? If so, why are we not this critical of so many other youtubers who do even worse? Ray's response has been to put up a wall (not terribly unlike what we see from Mojang), shield himself from the criticism, and move on with his life. The rest of us should move on too.


r/Mojira • • May 31 '22

Discussion MC-252295, a counter-argument on the usage of "whilst" in Minecraft

25 Upvotes

A few days ago, I came across the bug report MC-252295, which points out the existence of the word whilst in a number of Minecraft death messages, and argues at length in favor of its replacement with while. The whole thing is absolutely fascinating, and also completely incorrect – or at least, I think so.

Let's start by analyzing the bug report itself. In it, 22 death message strings are listed; just one of them uses the word while, but the other twenty-one use whilst. So, an inconsistency does exist. Fair enough.

The bug report then advocates for the replacement of whilst with while in all cases on stylistic grounds, pointing out that Minecraft's source language is American English (this is true) and that the word while is widely preferred in American English (this is also true). The bug report does contradict itself by on one hand stating that this constitutes a "spelling" error but then later correctly admitting that both spellings are accepted in American English. The author does not appear interested in rectifying this issue, but whatever, it's not a huge problem.

Some argue that there is actually a usage difference between while and whilst; the former would be used to emphasize time, similar to "at the same time as", while the latter would be used to emphasize contrast, similar to "whereas". This attempted distinction is incorrect; I could find not find it in any dictionary. On the contrary, all dictionaries and websites that I looked at (example, example, example) list these two words as direct synonyms that can each carry either meaning.

Now, my counter-argument is that usage is only half of the story here; what's missing from consideration is tone.

To my American ears, whilst has a slightly archaic ring to it. This is supported by what I see in its entry in the Collins English Dictionary, where it's given usage notes of "mainly British, formal, or literary".

The thing that's so fun about words that are formal and/or literary is that, when used in casual contexts, they can suddenly become hilarious. This sort of thing is never incorrect, mind you, it's just stylistically incongruous; when used effectively, it conveys a sort of faux affectation that is very, very funny.

Back to Minecraft. I would argue that the devs have gone out of their way to make Minecraft death messages elicit this sort of understated humor, either by using formal language or by using overly convoluted phrasing. Here are some examples of what I mean:

<player> went up in flames was chosen when the simplified <player> burned up could have conveyed the same meaning;

<player> was slain by <player/mob> was chosen instead of the simpler <player> was killed by <player/mob>;

<player> didn't want to live in the same world as <player/mob> was chosen instead of the simpler <player> was pushed into the void by <player/mob> or similar;

<player> experienced kinetic energy was chosen instead of the simpler <player> crashed-landed or similar;

<player> was impaled on a stalagmite was chosen instead of the simpler <player> died because of a stalagmite; and, most recently,

<player> was obliterated by a sonically-charged shriek was chosen instead of the simpler <player> was killed by the Warden's shriek or similar.

For this reason, I believe that the usage of whilst is not only not incorrect, but also completely intentional. I do not think that MC-252295 should qualify as a bug; and to the extent that it does, I think that any fix should favor keeping whilst instead of removing it.