[MC-311565] SectionPath, SectionVisibility, and Frustum culling Octree hotkeys require a debug property

The SectionPath (F3 + E), SectionVisibility (F3 + V), and Frustum culling Octree (F3 + O) hotkeys are coded to require that the MC_DEBUG_HOTKEYS debug property be enabled. There is no point in hiding these hotkeys behind a debug property, as the debug renderers they control are now fully implemented in the Debug Options menu (F3 + F6).

Linked issues

duplicates 1

MC-301443 F3 hotkeys for SectionPath, SectionVisibility and Frustum Octree doesn't work Resolved

Comments 5

[Mod] ManosSef 2026-08-31T16:37:07Z

Thank you for your report!
We're tracking this issue in MC-301443, so this ticket is being resolved and linked as a Duplicate.

That ticket has already been resolved as Invalid. Please take a look at the parent ticket and see if an explanation is provided in the description or in the comments as to why this issue is invalid.

Please do not duplicate your own bug reports.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

Mickey42302 2026-08-31T16:40:35Z

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.

[Mod] ManosSef 2026-08-31T16:48:13Z

They still required a debug property back then too. It was just for Mojang only instead of everyone.

Mickey42302 2026-08-31T16:57:45Z

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.

[Mod] ManosSef 2026-08-31T17:05:40Z

That is because javac removes checks for constants that are always true or false (DEBUG_HOTKEYS was in fact a flag in SharedConstants even before 1.21.9). I do not believe Mojang manually went through and re-enabled every single debug feature they already had working in order to get them to work in 1.21.9. They already worked, but the code that made them work was being stripped out when compiling the code. Regardless of the current situation, it would still be a feature request to ask for the property to be removed.