Minecraft text components can combine visible text with colors, hover details and click actions. They are useful for server navigation, map dialogue and command help, but the component must match the destination and game version.
This guide focuses on predictable behavior: build the visible message first, add one event at a time, and make every clickable label describe its action.

Build and test one interaction at a time
- Write the visible text first and confirm its color and formatting.
- Add a
hoverEventand test the tooltip. - Add a
clickEventonly after the hover output works. - Use
suggest_commandwhen players should review a command, and reserverun_commandfor deliberate actions.
Test the component in the exact destination: chat, a tellraw command, a book, a sign and an item name do not all accept identical wrappers. Never place an untrusted URL or a privileged command behind vague text such as “click here”. The label should state what the click will do.
Release checklist
Test as a normal player, not only as an operator. Confirm hover text on the intended client version, verify that suggested commands are editable, and check that URLs use the expected scheme. Keep a plain-text fallback for consoles, logs and accessibility tools that cannot expose hover interactions.
