Description of the bug
In the 1.20 update, signs can now be edited by right-clicking on them. For KitPVP's interactable signs, right-clicking on them will do whatever action you gave it, but it'll also bring up the sign-editing menu. If you have build permissions and exit the menu, the top line's color formatting will be removed, and the sign will lose its functionality. If you don't have build permissions and use something like WorldGuard, exiting the menu will display a "Sorry, but you can't place that block here." message.
I think with the build permissions, Minecraft will remove the original sign and place a new one to achieve the effect of "editing" the sign, hence why the sign seems to lose its functionality.
Screenshot of /kp debug
Additional screenshots or video (if applicable)
Right-clicking on an interactable sign:
If you have build permissions:
If you don't have build permissions:
Pastebin.com of any relevant .yml files (if applicable)
n/a
Description of the bug In the 1.20 update, signs can now be edited by right-clicking on them. For KitPVP's interactable signs, right-clicking on them will do whatever action you gave it, but it'll also bring up the sign-editing menu. If you have build permissions and exit the menu, the top line's color formatting will be removed, and the sign will lose its functionality. If you don't have build permissions and use something like WorldGuard, exiting the menu will display a "Sorry, but you can't place that block here." message.
I think with the build permissions, Minecraft will remove the original sign and place a new one to achieve the effect of "editing" the sign, hence why the sign seems to lose its functionality.
Screenshot of /kp debug
Additional screenshots or video (if applicable) Right-clicking on an interactable sign:
If you have build permissions:
If you don't have build permissions:
Pastebin.com of any relevant .yml files (if applicable) n/a