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

Command block screen is opened before the update packet is received, causing blank and disabled default value controls to be displayed for a while

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • None
    • Minecraft 15w35b, Minecraft 15w35e, Minecraft 15w36d, Minecraft 15w37a, Minecraft 15w38b, Minecraft 15w50a, Minecraft 16w36a, Minecraft 1.11.2, Minecraft 17w06a, Minecraft 1.12, Minecraft 1.12.2, Minecraft 17w45b, Minecraft 17w46a, Minecraft 1.13-pre6, 1.14.4, 19w37a, 1.15 Pre-release 5, 1.15 Pre-release 7, 1.15, 1.15.1, 1.16 Release Candidate 1, 1.16, 1.16.1, 1.16.2 Release Candidate 2, 1.16.2, 20w51a, 21w14a, 1.21
    • None
    • Confirmed
    • Creative
    • Networking
    • Low
    • Platform

      The bug

      When you right click on a customized command block, you will notice empty text fields and/or "Chain" state of the leftmost button, and also disabled "Done" button.

      What I expect:
      The controls immediately display its values after opening the command block screen or telling you that it is loading.

      What actually happened:
      After opening the interface all controls are in the default state (except for the leftmost button, it is in "Chain") and disabled "Done" button. Then after a while all controls display its values.

      My suggestion is to make the command block screen open when the client received the update packet of the command block block entity, like a chest. Or, tell the user that the command block's data is being loaded.

      How to reproduce

      1. Enter a lag-inducing command into a powered repeating command block, e.g:
        /execute if entity @e[distance=100000]
      2. Close and reopen the command block GUI
        →  The command input field will briefly appear blank

            Unassigned Unassigned
            Amrsatrio Amr Satrio
            Votes:
            11 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              CHK: