Every SMAPI mod or content pack must have a <tt>manifest.json</tt> file in its folder. SMAPI uses this to identify and load the mod, perform update checks, etc. The manifest info is also available to any mod in code (using <tt>this.ModManifest</tt> for the current mod's manifest, or [[../#Mod registry|mod registry]] for other mods' manifests).
−
Every SMAPI mod or content pack has a <tt>manifest.json</tt> file with info about it. That info is available in that mod's code (using <tt>this.ModManifest</tt>) and to other mods (using the [[#Mod registry|mod registry]]).
+
==Basic examples==
Here's the basic format (see below for details on each field):
Here's the basic format (see below for details on each field):
{| class="wikitable"
{| class="wikitable"
Line 39:
Line 39:
|}
|}
+
==Fields==
===Basic fields===
===Basic fields===
All mods should specify the following fields.
All mods should specify the following fields.
Line 122:
Line 123:
===Anything else===
===Anything else===
−
Any other fields will be stored in the <tt>IManifest.ExtraFields</tt> dictionary, which is available through the [[#Mod registry|mod registry]]. Extra fields are ignored by SMAPI, but may be useful for extended metadata intended for other mods.
+
Any other fields will be stored in the <tt>IManifest.ExtraFields</tt> dictionary, which is available through the [[../#Mod registry|mod registry]]. Extra fields are ignored by SMAPI, but may be useful for extended metadata intended for other mods.