From 674061960f886115c341bddcb08cd827c90ae028 Mon Sep 17 00:00:00 2001 From: Andrew Miner Date: Fri, 16 Jan 2015 11:21:11 -0800 Subject: [PATCH] Updated Crafting Guide Data Format V2 (markdown) --- Crafting-Guide-Data-Format-V2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Crafting-Guide-Data-Format-V2.md b/Crafting-Guide-Data-Format-V2.md index 96bb964..35dcedd 100644 --- a/Crafting-Guide-Data-Format-V2.md +++ b/Crafting-Guide-Data-Format-V2.md @@ -39,7 +39,7 @@ item: Printed Calculation Circuit ## Basics -Each line of the file should usually contain a single command. Each command has the format: `: , , ...`. All of the available commands are described below. Multiple commands may be listed on the same line by separating them with `;` characters. Comments are entered using the `#` character, which can itself be escaped if you need to use it in an item name. Blank lines are ignored. +Each line of the file should usually contain a single command. Each command has the format: `: , , ...`. All of the available commands are described below. Multiple commands may be listed on the same line by separating them with `;` characters. Comments are entered using the `#` character, which can itself be escaped if you need to use it in an item name. Blank lines are ignored. Whitespace is generally irrelevant outside item names, but following the conventions described above makes things easier. You can check your file for errors by running the `./scripts/verify ` command on your file. This examine the file and print out any errors. If no errors are found, there is no output. While working on a data file, it is often handy to use the UNIX `watch` command to provide continuous feedback: `watch ./script/verify `.