Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-248192

F3 debug screen can be overloaded with content, rendering some of it unreadable on default settings

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 22w03a
    • Unconfirmed
    • (Unassigned)

      The bug

      In some cases, when using default GUI scale settings (and on most reasonable resolutions), F3 can display so much information that some of it is pushed off-screen.

      minecraft:grass_block is a notable offender - 1.18 had it assigned to many new block tags, which pushes the fluid tags section completely off the bottom of the screen.

      While this may be invalid due to F3 being a debug feature, the fact that this happens on the default settings and that the grass block is a very commonly encountered block means that this problem will only worsen as time goes on if not dealt with.

      How to reproduce

      1. Set GUI scale to Auto
      2. Press F3
      3. Look at a grass block

      Expected results

      The targeted fluid would be visible.

      Actual results

      minecraft:grass_block has enough tags assigned to it in the vanilla data pack that the targeted fluid section ends up off the bottom of the screen.

      Also note in the attached screenshots that the "For help" line on the left is also largely clipped at the 854x480 resolution.

      How to fix

      It may be advisable to split the F3 screen's info up to some extent. How all of the info would be accessed I'm not sure - perhaps the first press of F3 would show everything but targeted blocks/fluids/entities, pressing F3 again would lead to a screen solely focused on targeted blocks/fluids/entities, and pressing it a third time gets rid of the debug screen? Ultimately how this is dealt with (if at all) is at Mojang's discretion.

            Unassigned Unassigned
            Awesoman3000 Connor Steppie
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: