Item presets
Minecraft Written Book Command Generator
Written book commands combine item data and JSON text pages. This page keeps the book title, author, pages, display name, and custom_data in one workflow so map instructions can be edited without hand-escaping every page.
Preset result
A written book item command for NPC dialogue, map instructions, server rules, or quest manuals.
Output
Written book Give output
/give @p minecraft:written_book[custom_name={text:"Dungeon Manual",color:"gold",italic:false},written_book_content={title:"Dungeon Manual",author:"NBTForge",pages:["Welcome to the dungeon. Find the vault key, then return to the gate.","Tip: talk to the Relic Trader before the boss room."]},custom_data={book_id:"dungeon_manual"}] 1The longest command line is 332 characters, 76 over the 256-character chat input limit. Pasting it into chat can truncate the line and make Minecraft report a syntax error even when the generated command is valid.
- Use a Command Block: run
/give @s command_block, place it, then paste this command into the block command field. - Use a
.mcfunctionfor a reusable datapack: save the line without the leading slash atsaves/<world>/datapacks/<pack>/data/<ns>/function/<name>.mcfunctionwith a minimalpack.mcmeta, run/reload, then run/function <ns>:<name>. Do not paste.mcfunctioncontent into chat.
Preset screenshot
Build the preset
- Open Give and choose written_book as the item.
- Set the book title and author before writing page text.
- Write each page as readable text, then add styling or JSON behavior only when needed.
- Copy the command and open the book in-game to check page length and wrapping.
Books need page-level testing
A command can be valid while the book is still unpleasant to read. Keep pages short, test line wrapping, and split instructions across pages rather than forcing one dense block.
NBTForge is useful because the item fields and page content can stay together as a preset instead of living in a separate note file.
Use books as project assets
Written books often pair with NPCs, villager shops, quest rewards, and command-pack tutorials. Save the book command in Project beside the commands that hand it to the player.
Use custom_data when the book should be removed, replaced, or detected later.
- Use title and author for the book UI.
- Use custom_name for inventory display.
- Use custom_data for command logic.
Fit the preset into a real project
Treat Minecraft Written Book 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
Can written book pages use JSON text styling?
Yes, but keep the page readable first. Add styling after the plain text has the right length and flow.
Should I use a book or tellraw for instructions?
Use books for persistent reference text. Use tellraw or title commands for immediate prompts.
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 Give workbench, then adjust the preset fields for your world.