Text and UI presets
Minecraft Title Command Generator
A title command generator should produce more than one line. The message, subtitle, and timing work together, and separating them is how polished map feedback turns into inconsistent command blocks.
Preset result
A small title command sequence with timing and JSON text kept together so map feedback is easy to test.
Output
Title command sequence
/title @a times 10 60 20
/title @a title {text:"Trial Started",color:"gold",bold:true}
/title @a subtitle {text:"Survive the first wave",color:"gray"}Preset screenshot
Build the preset
- Open Text and select title output before writing the player-facing message.
- Set title timing first so fade-in, hold, and fade-out match the scene.
- Add a subtitle or actionbar line for the instruction that players need after the title appears.
- Save the sequence to Project if it belongs to a boss phase, quest step, or minigame state.
Title, subtitle, and actionbar roles
Use the title for the emotional label: Trial Started, Boss Defeated, Door Locked. Use subtitle or actionbar for the practical instruction: survive the wave, collect the key, return to lobby.
NBTForge keeps these as text-component output so color, bold state, and JSON formatting can be checked before the command is copied.
Timing matters
The /title times line is part of the preset, not an afterthought. Short timings feel like alerts; longer timings fit scene changes and boss introductions.
When this command runs repeatedly, use actionbar instead of full title spam. Save both patterns as separate project steps if the map needs both.
- Use short fade-in for combat feedback.
- Use longer hold time for quest chapter titles.
- Reset or replace titles when a player can trigger the event repeatedly.
Fit the preset into a real project
Treat Minecraft Title Command 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
Do I need /title times every time?
No, but including it in the preset makes the behavior predictable across command blocks and functions.
Can the same text editor build tellraw and title JSON?
Yes. The text-component structure is shared, but the surrounding command changes.
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.