Presets

Text and UI presets

Tellraw JSON Text Generator

Tellraw is a JSON text problem disguised as a chat command. This generator page focuses on the text-component parts that usually break: nested hover text, click actions, color, bold state, and safe command values.

Read inENRUDEESPT中文日本語VIFR한국어IDPLTR

Preset result

A tellraw message that players can read, hover, and click without hand-escaping JSON text components.

Output

Tellraw JSON output

/tellraw @a {text:"Open the dungeon gate",color:"gold",bold:true,hover_event:{action:"show_text",value:{text:"Click to run the gate trigger",color:"gray"}},click_event:{action:"run_command",command:"/trigger dungeon_gate"}}

Preset screenshot

The NBTForge workbench state used for the minecraft tellraw JSON text generator article, including the visible controls and generated output.

Build the preset

  1. Open the Text workbench and choose tellraw as the target output.
  2. Write the visible message first, then add color and style states.
  3. Add hover_event and click_event only after the plain message renders correctly.
  4. Copy the JSON output and test it with the same selector that will receive the final message.

Readable JSON before clever JSON

The fastest tellraw failure is malformed JSON. Build the visible text first, then layer interaction on top. NBTForge makes that order obvious because the text component is edited as fields before it becomes command output.

For map prompts, keep the first sentence short and place extra detail in hover text. Click actions should run a trigger or a safe command, not a long hidden command chain.

Where this fits in a command pack

Tellraw usually pairs with scoreboard triggers, title messages, sound feedback, and quest state. Save the command to Project when it is part of a multi-step interaction.

Use consistent colors for the same action family. For example, gold for objective prompts, green for success, and red for blocked actions.

  • Use /trigger for player-click flows when possible.
  • Keep hover text explanatory, not required for the main instruction.
  • Test with @s, @p, and @a depending on the final command context.

Fit the preset into a real project

Treat Tellraw JSON Text Generator as a tested starting point, not just a copied string. After the output works once, save it with a clear Project name, note the target Minecraft version, and keep the preset near related setup commands such as scoreboard, bossbar, loot, or reset lines.

Before publishing the preset to a map, server, or command pack, run it from the copied artifact rather than only from the live workbench. That catches missing dependencies, stale selectors, wrong edition choices, and commands that only worked because local test state already existed.

  • Keep the selected Edition and Version with the shared command.
  • Test selectors against a harmless command before using damage, kill, clear, or teleport.
  • Move long commands into Project or a function-style workflow instead of pasting them into chat.
  • Recheck warnings after changing entities, item components, passengers, or datapack resources.

FAQ

Can tellraw run a command when clicked?

Yes. Use click_event with run_command, then point it at a safe trigger or command that is valid for the player context.

Why does my tellraw JSON work in one version but not another?

Text-component formats have changed over time. Check the selected version family and rebuild the component instead of copying an old escaped JSON snippet blindly.

When should this preset become part of a command pack?

Use it as a command pack entry when the output depends on setup lines, reset commands, loot resources, scoreboard state, or repeated testing. Single safe commands can still be copied directly from Output.

Open this workflow

Start from the related Text workbench, then adjust the preset fields for your world.