Direct answer

In Minecraft Java Edition 26.3, commands and other click events embedded in sign text are not executed by default when the block is clicked. Newly placed signs also do not resolve text components by default. Mojang added a boolean sign block-entity field, allow_op_features, which defaults to false and can restore the previous behavior when set explicitly.

Which signs are affected?

  • Newly generated or newly placed vanilla command signs are affected by the new default.
  • Mojang documents migration behavior for signs saved in worlds from older versions: applicable old sign data gets allow_op_features set to true.
  • Third-party plugin sign menus may register their own click events, and may not use vanilla sign text commands at all. Check that plugin’s compatibility documentation.

Troubleshooting checklist

  1. Confirm the server is on 26.3 and verify whether the affected sign was newly placed or loaded from an older world.
  2. Test a copy of the sign’s world/datapack in a staging server with the same software and plugins.
  3. Identify whether the sign relies on vanilla text click events, a datapack, or plugin commands.
  4. For intentionally privileged vanilla sign behavior, use a 26.3-compatible datapack or administrative world-editing workflow that explicitly manages allow_op_features. Verify exact syntax against Mojang’s current data format before applying it.
  5. If a plugin owns the sign interaction, update or troubleshoot that plugin instead of changing vanilla NBT.

Security and safe rollback

Do not enable command execution indiscriminately on untrusted player-created signs. Preserve a pre-change copy of the world and datapack. If a migration breaks interactions, restore the tested copy and revisit the authoring system; world-format changes mean downgrading an already upgraded save is not a safe general rollback.

What this change does not mean

This is not a removal of signs, and it does not prove that every signs plugin stopped working. It specifically changes vanilla sign text processing and related block-entity data.

Official references

Official sources for version-sensitive details. Check the newest release notes before changing a production server.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000