From 0cf1cb5727b856a5d30b84f318e0ea88f7e46605 Mon Sep 17 00:00:00 2001 From: Andrew Miner Date: Thu, 28 Apr 2016 07:38:23 -0700 Subject: [PATCH] Updated Adding support for a new Mod (markdown) --- Adding-support-for-a-new-Mod.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Adding-support-for-a-new-Mod.md b/Adding-support-for-a-new-Mod.md index fd22f8d..1648259 100644 --- a/Adding-support-for-a-new-Mod.md +++ b/Adding-support-for-a-new-Mod.md @@ -15,8 +15,7 @@ npm install grunt test cd ../crafting-guide npm install -grunt clean build -./scripts/server +grunt clean start ``` _**NOTE:** If you're using Windows (instead of MacOS or Linux), you'll want to perform all of these commands using the [Git for Windows](https://msysgit.github.io/) shell. You will also need to install [rsync](https://www.itefix.net/content/get-cwrsync) manually. Finally, windows users should leave out the word `sudo` from all commands._ @@ -48,7 +47,7 @@ Create the mod's overall data file by following the [Mod Data Format](https://gi Next is the hard part. From the last step, you should have a `mod-version.cg` in your Mod's current version directory. Now, for each item whose image you exported, follow the [Mod Version Data Format](https://github.com/andrewminer/crafting-guide/wiki/Mod-Version-Data-Format) reference to enter all the groups, items, recipes, and other information needed to describe your mod. -Be sure to test frequently using the `grunt test` command. +Be sure to test frequently using the `grunt test` command, or run `grunt watch` to continuously run tests as you work. ## 7. Test Locally