MC-251890run_command click events send value as command instead of chat message
When clicking on a text component that has a run_command click event, the value is treated as a command instead of a message. For text in books and in chat specifically, this means that the preceding slash must now not be included for the command to run. Commands on signs still work with the preceding slash.
Steps to reproduce:
Run the command /tellraw @s {"text":"click me","clickEvent":
{"action":"run_command","value":"/say hi"}Click the message
What I expected to happen:
The /say hi command would run
What actually happened:
I received an error:
Unknown or incomplete command, see below for error
/say hi<--[HERE]
Linked Issues
Created Issue:
run_command click events send value as command instead of chat message
When clicking on a text component that has a run_command click event, the value is treated as a command instead of a message. For text in books and in chat specifically, this means that the preceding slash must now not be included for the command to run. Commands on signs still work with the preceding slash.
Steps to reproduce:
Run the command /tellraw @s {"text":"click me","clickEvent":{"action":"run_command","value":"/say hi"
{}}}Click the messageWhat I expected to happen:
**The /say hi command would run
What actually happened:
I received an error:
{{Unknown or incomplete command, see below for error
/say hi<--[HERE]
}}
When clicking on a text component that has a run_command click event, the value is treated as a command instead of a message. For text in books and in chat specifically, this means that the preceding slash must now not be included for the command to run. Commands on signs still work with the preceding slash.
Steps to reproduce:
Run the command /tellraw @s {"text":"click me","clickEvent":{"action":"run_command","value":"/say hi"
{}}}Click the messageWhat I expected to happen:
**The /say hi command would run
What actually happened:
I received an error:
{{Unknown or incomplete command, see below for error
/say hi<--[HERE]
}}When clicking on a text component that has a run_command click event, the value is treated as a command instead of a message. For text in books and in chat specifically, this means that the preceding slash must now not be included for the command to run. Commands on signs still work with the preceding slash.
Steps to reproduce:
Run the command /tellraw @s {"text":"click me","clickEvent":{"action":"run_command","value":"/say hi"
Click the messageWhat I expected to happen:
The /say hi command would run
What actually happened:
I received an error:
Unknown or incomplete command, see below for error
/say hi<--[HERE]
When clicking on a text component that has a run_command click event, the value is treated as a command instead of a message. For text in books and in chat specifically, this means that the preceding slash must now not be included for the command to run. Commands on signs still work with the preceding slash.
Steps to reproduce:
Run the command /tellraw @s {"text":"click me","clickEvent":{"action":"run_command","value":"/say hi"
Click the messageWhat I expected to happen:
The /say hi command would run
What actually happened:
I received an error:
Unknown or incomplete command, see below for error
/say hi<--[HERE]When clicking on a text component that has a run_command click event, the value is treated as a command instead of a message. For text in books and in chat specifically, this means that the preceding slash must now not be included for the command to run. Commands on signs still work with the preceding slash.
Steps to reproduce:
Run the command {{/tellraw @s {"text":"click me","clickEvent":
{"action":"run_command","value":"/say hi"}}}
Click the messageWhat I expected to happen:
The /say hi command would run
What actually happened:
I received an error:
Unknown or incomplete command, see below for error
/say hi<--[HERE]
When clicking on a text component that has a run_command click event, the value is treated as a command instead of a message. For text in books and in chat specifically, this means that the preceding slash must now not be included for the command to run. Commands on signs still work with the preceding slash.
Steps to reproduce:
Run the command {{/tellraw @s {"text":"click me","clickEvent":
{"action":"run_command","value":"/say hi"}}}
Click the messageWhat I expected to happen:
The /say hi command would run
What actually happened:
I received an error:
Unknown or incomplete command, see below for error
/say hi<--[HERE]When clicking on a text component that has a run_command click event, the value is treated as a command instead of a message. For text in books and in chat specifically, this means that the preceding slash must now not be included for the command to run. Commands on signs still work with the preceding slash.
Steps to reproduce:
Run the command /tellraw @s {"text":"click me","clickEvent":{{{}
{"action":"run_command","value":"/say hi"}{}}}
Click the message
What I expected to happen:
The /say hi command would run
What actually happened:
I received an error:
Unknown or incomplete command, see below for error
/say hi<--[HERE]
When clicking on a text component that has a run_command click event, the value is treated as a command instead of a message. For text in books and in chat specifically, this means that the preceding slash must now not be included for the command to run. Commands on signs still work with the preceding slash.
Steps to reproduce:
Run the command /tellraw @s {"text":"click me","clickEvent":{{{}
{"action":"run_command","value":"/say hi"}
{}}}Click the message
What I expected to happen:
The /say hi command would run
What actually happened:
I received an error:
Unknown or incomplete command, see below for error
/say hi<--[HERE]When clicking on a text component that has a run_command click event, the value is treated as a command instead of a message. For text in books and in chat specifically, this means that the preceding slash must now not be included for the command to run. Commands on signs still work with the preceding slash.
Steps to reproduce:
Run the command {{/tellraw @s {"text":"click me","clickEvent":
{"action":"run_command","value":"/say hi"}}}
Click the message
What I expected to happen:
The /say hi command would run
What actually happened:
I received an error:
Unknown or incomplete command, see below for error
/say hi<--[HERE]
When clicking on a text component that has a run_command click event, the value is treated as a command instead of a message. For text in books and in chat specifically, this means that the preceding slash must now not be included for the command to run. Commands on signs still work with the preceding slash.
Steps to reproduce:
Run the command
{"action":"run_command","value":"/say hi"}{{/tellraw @s {"text":"click me","clickEvent":}}
Click the message
What I expected to happen:
The /say hi command would run
What actually happened:
I received an error:
Unknown or incomplete command, see below for error
/say hi<--[HERE]When clicking on a text component that has a run_command click event, the value is treated as a command instead of a message. For text in books and in chat specifically, this means that the preceding slash must now not be included for the command to run. Commands on signs still work with the preceding slash.
Steps to reproduce:
Run the command /tellraw @s {"text":"click me","clickEvent":
{"action":"run_command","value":"/say hi"}Click the message
What I expected to happen:
The /say hi command would run
What actually happened:
I received an error:
Unknown or incomplete command, see below for error
/say hi<--[HERE]
![[Mojang] Gegy](../../../data/avatars/users/10122.svg){kind=small}
[Mojang] Gegy![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
![[Bot] Piston](../../../data/avatars/users/31202.png){kind=small}
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
is duplicated by
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
Duplicate of MC-251890 which has been fixed for a future version of Minecraft.
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Thank you for your report!
We're tracking this issue in MC-251890, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Fixed. Please check the Fix Version/s field in that ticket to see in which version this behavior was or will be fixed.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
yeah i just did it in 1.18 and it didnt work