The Bug:
When right-clicking a non-waxed sign with clickEvent data, the sign is edited, instead of the clickEvent running.
Steps to Reproduce:
Place a command block and run the command provided below.
/setblock ~ ~1 ~ minecraft:oak_sign[rotation=8,waterlogged=false]{back_text:{color:"black",has_glowing_text:0b,messages:['{"text":""}','{"text":""}','{"text":""}','{"text":""}']},front_text:{color:"black",has_glowing_text:0b,messages:['{"clickEvent":{"action":"run_command","value":"say Hello"},"text":"TEST"}','{"text":""}','{"text":""}','{"text":""}']},is_waxed:0b}
Right-click the sign.
Expected Behavior:
Instead of the sign being edited, the clickEvent should run.
Linked issues
is duplicated by 1
Comments 3
WAI per changelog:
Click commands on Signs can only be invoked when the Sign is waxed
If a Sign with a click command is not waxed, interacting with it will not invoke the command and instead open up the edit screen as usual
Do read changelogs before reporting behaviors as bugs.
Works As Intended as per the 23w12a changelogs.
I'm pretty sure this is intentional (See the article on minecraft.net).