Mickey42302

I’m aware that the MC_DEBUG_HOTKEYS property had not been added yet. However, even when the IS_RUNNING_IN_IDE flag was set to true (this is what controlled them back then), the hotkeys did not register. You can personally verify this by overriding the flag with a patch.

This is not a duplicate. That issue referred to the fact that the debug hotkeys were completely broken in that snapshot. It has long since been fixed. I am referring to the fact that they still require a debug property to be used.

How is this an invalid report? I highly doubt that an unholy amount of lag is intentional.

I don’t see why this shouldn’t be addressed. If the developers want the debug renderers to be useful to the community, they kind of need to work properly.

Here are the screenshots. Please be advised that the screenshot for 1.21.8 is from before the debug properties were added. During this time, you had to use modifications to enable the heightmap debug renderer. This is the last version where it worked properly. I did not add any code which modified the heightmap debug renderer itself; it only added a way to enable it.

As for the latest snapshot, the performance issues were actually even worse when I was in the process of getting the screenshot you needed. You can see this for yourself in the FPS chart.

And to be honest, any issues with the renderers are worth fixing. The point of the renderers and other tools is to assist with debugging. If the debug features don’t work properly, that defeats the purpose of them being in the game.

With all due respect, is this ever going to be fixed? I reported this bug almost 6 years ago.

It’s not difficult to patch. All you have to do is change the translation strings, like I did here:

https://github.com/Mickey42302/Yukon/tree/main/src/main/resources/assets/minecraft/lang

Can this bug report be considered valid since the “/warden_spawn_tracker” command is now accessible via the “DEV_COMMANDS” debug property?