Text and UI presets
Tellraw preset with colors and click text
Tellraw preset with colors and click text is now a complete Text workflow with tool screenshots, generated command output, and a Minecraft result capture. Use this for chat prompts, clickable quest actions, lobby menus, or optional interactions where the player should choose a command. The gallery keeps setup fields, output review, and the visible HUD or chat result together so the preset can be audited before it becomes part of a map event, scoreboard loop, or command-block chain.
Preset result
A gold tellraw prompt that can be extended with hover text and click-trigger behavior.
Output
Tellraw click prompt command
/tellraw @a {text:"Open the gate",color:"gold",bold:true,hover_event:{action:"show_text",value:{text:"Click to request the gate",color:"gray"}},click_event:{action:"run_command",command:"/trigger dungeon_gate"}}Preset screenshot
Build the preset
- Open the Text workbench and confirm the target selector or id.
- Set the player-facing name, text, objective, or status value first.
- Tune color, style, timing, display slot, or value fields before copying.
- Review the generated command output and command length warning.
- Save the command to Project when it belongs to a multi-command workflow.
- Run the command in a clean test world and confirm the visible result matches the workbench.
Why this Text preset matters
Use this for chat prompts, clickable quest actions, lobby menus, or optional interactions where the player should choose a command.
The workbench keeps visible text, color, hover copy, and click command value together before JSON output. A screenshot-only snippet is not enough for these commands because the visible UI state has to match command output and map logic. Keep the preset as a checkpoint where the readable label, selector, id, and generated command can be reviewed together before the command is copied.
Testing and version details
Click commands should point at safe triggers or simple commands. Do not hide long command chains inside chat text.
Run the first smoke test in a restored world with only the needed commands active. HUD, chat, bossbar, and scoreboard results are easy to confuse when old objectives or bars remain from a previous test, so create or reset the state before judging the screenshot. Keep selectors narrow when the final map should affect one player.
- Use stable ids for stateful commands.
- Keep player-facing feedback short enough to read or recognize quickly.
- Save related setup and update commands together in Project.
Where to go next
Create the scoreboard trigger objective before relying on the click event in production.
For related text surfaces, compare the title quest message preset and scoreboard objective preset.
FAQ
Can I paste this Text command into chat?
Yes for a quick smoke test if the command is short enough and the selector is safe. For repeatable map behavior, move the command into a command block, function, or Project export.
Why include an in-game result image?
The result image confirms the command affects the HUD, chat, sidebar, sound marker, particle effect, or display entity in Minecraft, not only in the workbench output panel.
Should this be saved with related commands?
Yes. Bossbars, titles, tellraw prompts, and scoreboards usually need setup or follow-up commands, so keep the preset near the rest of the workflow.
Open this workflow
Start from the related Text workbench, then adjust the preset fields for your world.