From f30c7bbca358d8d6443d43d66e26089fdfa95b4c Mon Sep 17 00:00:00 2001 From: Andrew Miner Date: Sun, 22 Mar 2015 10:23:09 -0700 Subject: [PATCH] Updated Mod Data Format (markdown) --- Mod-Data-Format.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Mod-Data-Format.md b/Mod-Data-Format.md index d4f3914..422a1dd 100644 --- a/Mod-Data-Format.md +++ b/Mod-Data-Format.md @@ -1,6 +1,6 @@ The Mod file format is a very simple command-based language which is very similar to [YAML](http://www.yaml.org). There are commands for entering all various kinds of data needed to describe a mod and what versions are supported. Most commands are optional, and can be entered in any order. Anywhere this isn't true will be called out below. -Each mod is described with its own directory under `/src/data`. The directory should be named using the Mod's slug name (see: [About Slugs](https://github.com/andrewminer/crafting-guide/wiki/About-Slugs)), and contain a file named `mod.cg` using the following format. +Each mod is described with its own directory under `/static/data`. The directory should be named using the Mod's slug name (see: [[About Slugs]]), and contain a file named `mod.cg` using the following format. ## Example @@ -70,4 +70,4 @@ Each line of the file should usually contain a single command. Each command has Multiple versions may be specified, and if so, they should be listed with the most recent first. - For each version listed, a subdirectory should exist with exactly the same name containing a [ModVersion data file](https://github.com/andrewminer/crafting-guide/wiki/Mod-Version-Data-Format) and an images subdirectory. \ No newline at end of file + For each version listed, a subdirectory should exist with exactly the same name containing a [[Mod Version Data Format]]). \ No newline at end of file