Command block screen is opened before the update packet is received, causing blank and disabled default value controls to be displayed for a while
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
- Enter a lag-inducing command into a powered repeating command block, e.g:
/execute if entity @e[distance=100000]
- Close and reopen the command block GUI
→
The command input field will briefly appear blank
Linked Issues
is duplicated by2
relates to3
MC-136982Command block data is erased upon pressing Enter in the GUI before the client receives the update packetConfirmedMC-89087Command Block GUI takes a brief time to update (output bar shown when disabled, mode buttons in wrong state)FixedMC-210155Command block output no longer is displayed immediately after running a commandFixed
LowCreated Issue:
Command block's blockdata is read after a few ticks after opening interface
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 grayed out "Done".
What I expect:
The controls immediately displays its values after opening the interface.What actually happened:
After opening the interface all controls are in the default state and grayed out "Done" button. Then after a few ticks all controls display its values.To reproduce:
Put a command block, customize it, close the interface, open it again. The bug is reproduced. You'll notice empty text fields and then it's filled automatically.Environment
Windows 10
Attachments3
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 grayed out "Done".
What I expect:
The controls immediately displays its values after opening the interface.What actually happened:
After opening the interface all controls are in the default state (except for the leftmost button, it is in "Chain") and grayed out "Done" button. Then after a few ticks all controls display its values.To reproduce:
Put a command block, customize it, close the interface, open it again. The bug is reproduced. You'll notice empty text fields and then it's filled automatically.
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 grayed out "Done".
What I expect:
The controls immediately displays its values after opening the interface.What actually happened:
After opening the interface all controls are in the default state (except for the leftmost button, it is in "Chain") and grayed out "Done" button. Then after a few ticks all controls display its values.To reproduce:
Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields and then it's filled automatically.
Command block'sblockdata is readafter a few ticks after opening interfaceCommand block's interface controls are set after a few ticks after opening interface
duplicates
is duplicated by
duplicates
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 grayed out "Done".
What I expect:
The controls immediately displaysits values after opening the interface.What actually happened:
After opening the interface all controls are in the default state (except for the leftmost button, it is in "Chain") and grayed out "Done" button. Then after a few ticks all controls display its values.To reproduce:
Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields and then it's filled automatically.
Please update Status and Resolution
is duplicated by
![[Mod] Torabi](../../../data/assets/gravatar/torabi.png){kind=small}
relates to
Wrong duplicate link
This duplicatesMC-87218
Command block's interface controls are set after a few ticks (depending on read speed) after opening interface
Command block's interface controls are set after a few ticks (depending on disk read speed) after opening interface
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
Windows 10
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
grayed out "Done".What I expect:
The controls immediately display its values after opening theinterface.What actually happened:
After opening the interface all controls are in the default state (except for the leftmost button, it is in "Chain") andgrayed out"Done" button. Then after a few ticks all controls display its values.To reproduce:
Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields and then it's filled automatically.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.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 few ticks all controls display its values, because the command block screen is opened before the client received an update packet.My suggestion is to make the command block screen open when the client received the update packet of the command block block entity.
To reproduce:
Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields and then it's filled automatically.
Command block's interface controls are set after a few ticks (depending ondisk readspeed) after opening interfaceCommand block's interface controls are set after a few ticks (depending on connection speed) after opening interface
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.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 few ticks all controls display its values, because the command block screen is opened before the client received an update packet.My suggestion is to make the command block screen open when the client received the update packet of the command block block entity.
To reproduce:
Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fieldsand thenit's filled automatically.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 the user 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 few ticks all controls display its values, because the command block screen is opened before the client received an update packet.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.
To reproduce:
I recommend you to do this on a remote server to make a use of the latency. Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields without an explanation of what's happening and then after a while it's filled automatically.
Command block's interface controls are set after a few ticks (depending on connection speed) after opening interfaceCommand block screen is opened before the update packet is received, causing blank and disabled controls to be displayed for a while
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 tellingthe userthat 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 few ticks all controls display its values, because the command block screen is opened before the client received an update packet.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.
To reproduce:
I recommend you to do this on a remote server to make a use of the latency. Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields without an explanation of what's happening and then after a while it's filled automatically.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 few ticks all controls display its values, because the command block screen is opened before the client received an update packet.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.
To reproduce:
I recommend you to do this on a remote server to make a use of the latency. Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields without an explanation of what's happening and then after a while it's filled automatically.
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 afew ticksall controls display its values, because the command block screen is opened before the client received an update packet.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.
To reproduce:
I recommend you to do this on a remote server to make a use of the latency. Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields without an explanation of what's happening and then after a while it's filled automatically.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, because the command block screen is opened before the client received an update packet.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.
To reproduce:
I recommend you to do this on a remote server to make a use of the latency. Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields without an explanation of what's happening and then after a while it's filled automatically.
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, because the command block screen is opened before the client received an update packet.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.
To reproduce:
I recommend you to do this on a remote server to make a use of the latency. Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields without an explanation of what's happening and then after a while it's filled automatically.
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.
To reproduce:
I recommend you to do this on a remote server to make a use of the latency (sorry for my bad English). Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields without an explanation of what's happening and then after a while it's filled automatically.
Command block screen is opened before the update packet is received, causing blank and disabled default value controls to be displayed for a while
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
relates to
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
![[Helper] Misode](../../../data/avatars/users/93314.png){kind=small}
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.
To reproduce:
I recommend you to do this on a remote server to make a use of the latency (sorry for my bad English). Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields without an explanation of what's happening and then after a while it's filled automatically.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
Confirmed in 1.16 Release Candidate 1. Steps to reproduce:
- Enter the following command into a repeating command block. And power it. This will produce some lag (due to
MC-54932)./execute if entity @e[distance=100000]- Close and reopen the command block GUI
→Original steps to reproduce:
I recommend you to do this on a remote server to make a use of the latency (sorry for my bad English). Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields without an explanation of what's happening and then after a while it's filled automatically.
![[Mod] j_p_smith](../../../data/avatars/users/92851.png){kind=small}
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
Confirmed in 1.16 Release Candidate 1. Steps to reproduce:
Enter the following command into a repeating command block. And power it. This will produce some lag (due toMC-54932)./execute if entity @e[distance=100000]- Close and reopen the command block GUI
→Original steps to reproduce:
I recommend you to do this on a remote server to make a use of the latency (sorry for my bad English). Put a command block, customize it, close the interface, open it again. The bug is reproduced after you right click. You'll notice empty text fields without an explanation of what's happening and then after a while it's filled automatically.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
- Enter a lag-inducing command into a powered repeating command block:
/execute if entity @e[distance=100000]- Close and reopen the command block GUI
→
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
- Enter a lag-inducing command into a powered repeating command block, e.g:
/execute if entity @e[distance=100000]- Close and reopen the command block GUI
→
relates to
relates to
relates to
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
Rather mark this as a duplicate of MC-87209 as that report contains also screenshots
The bug
As described in MC-87209, the command block GUI briefly appears blank after it is opened. The Done button is disabled during this period, however, pressing the Enter key will cause all the default settings (impulse, unconditional, needs redstone, no command entered) to be saved in the command block, overwriting the previously saved data.
How to reproduce
- Enter a lag-inducing command into an always-active repeating command block, e.g:
execute if entity @e[distance=100000]
- Close and reopen the command block GUI
→ The command input field appears blank (MC-87209) - Press the Enter key before the GUI has finished loading
→ The command block is reset to an impulse, needs-redstone command block with no saved command (this may take a few seconds to occur due to the lag)
Alternatively, this can be reproduced by opening the GUI of any command block while holding the Enter key.
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
I can't seem to view that video. Does MC-87209 describe this issue?
Thanks, fixed.
Is this still an issue in the latest snapshot 16w44a? If so please update the affected versions.
This is an automated comment on any open or reopened issue with out-of-date affected versions.
Confirmed in 1.16 Release Candidate 1. Steps to reproduce:
→