When the official Mojang obfuscation mappings were released in snapshot 19w36a, they had a distinct feature that anyone giving them a cursory read would notice. A prank by the developers, the very first method mapped by the file was a method called "youJustLostTheGame", inside of the Blaze3D class. The method being the very first method mapped is important, as it ensures the joke has maximum impact and visibility. Unfortunately, an oversight by the developers was made in snapshot 21w13a when the Blaze3D class was updated with additional methods. You see, these methods were placed within the file without care for the joke, meaning it has been reduced to only being the 4th method visible, severely undercutting its effectiveness. This problem could be trivially solved by simply moving our beloved method up in the class back to its rightful place.

To further clarify this bug report, here's the start of the mappings for 19w36a (when the mappings were introduced):

com.mojang.blaze3d.Blaze3D -> cve:

    20:21:void youJustLostTheGame() -> a

And here's how the mappings have looked ever since 21w13a:

com.mojang.blaze3d.Blaze3D -> dnc:

    10:10:void <init>() -> <init>

    12:13:void process(com.mojang.blaze3d.pipeline.RenderPipeline,float) -> a

    16:17:void render(com.mojang.blaze3d.pipeline.RenderPipeline,float) -> b

    21:22:void youJustLostTheGame() -> a

Thank you.