I tried to use the /trigger command inside the clickEvent of a sign.
{Text1:'{"text":"Set Team","color":"dark_red","bold":true,"underlined":true,"clickEvent":{"action":"run_command","value":"trigger team set 1"}}'}
Expected Result
-> The player without any op-permissions can click the sign to execute the command.
Actual Result
-> The player needs to have op-permissions to execute this command by clicking on the sign even though it is a command that usually doesn't require any permissions.
Since executing these commands via klicking on a JSON text in a tellraw or a book works I expected it to work in signs as well.
Additional Information
I made sure to constantly enable the trigger objective via a ticked function
I tested other non-op commands like /me and they also don't work in signs
Linked issues
Attachments
Comments 3
Can you still reproduce this issue in the latest version? I cannot seem to in 1.20.5 Pre-Release 1. I had set the click event to run the '/me' command which does not require opperator permissions, and it executed as expected on a default survival world with commands off. Have I reproduced the issue properly? (If not, please correct me)
This is my test:
[media]
It's probably the spawn protection that prevents the clickability of signs.
Set spawn-protection=0
inserver.properties