From 4eac47715b63b433d2103efb621305f2effd72b5 Mon Sep 17 00:00:00 2001 From: Andrew Miner Date: Sun, 22 Mar 2015 12:49:48 -0700 Subject: [PATCH] Updated Mod Data Format (markdown) --- Mod-Data-Format.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/Mod-Data-Format.md b/Mod-Data-Format.md index 4fcddc4..b519382 100644 --- a/Mod-Data-Format.md +++ b/Mod-Data-Format.md @@ -2,6 +2,13 @@ The Mod file format is a very simple command-based language which is very simila Each mod data file is stored in 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 format described later on this page. +Each mod should also have its own directory under `/static/browse`. This directory should contain: + +* a 160x160 `icon.png` file used to represent the mod in various places on the site +* (optional) a `tutorials` directory. See [[Tutorial Data Format]] for details. +* a directory for each item (named using the item's slug). Each directory should have a 48x48 + `icon.png` file for that item. See [[Mod Version Data Format]] for details. + ## Example ```yaml @@ -70,4 +77,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 [[Mod Version Data Format]]. \ No newline at end of file + For each version listed, a subdirectory should exist under `/static/data//` containing a `mod-version.cg` file. See [[Mod Version Data Format]] for details on this file's format. \ No newline at end of file