153
edits
Changes
Jump to navigation
Jump to search
Line 31:
Line 31: − + − + Line 41:
Line 41: − +
Modding:Modder Guide/Release (view source)
Revision as of 16:59, 8 September 2019
, 16:59, 8 September 2019→For content pack mods: fixed sub headers
** If it's an assembly reference: right-click on the reference in Visual Studio or MonoDevelop, choose ''Properties'', and change 'Copy Local' or 'Local Copy' to false.
** If it's an assembly reference: right-click on the reference in Visual Studio or MonoDevelop, choose ''Properties'', and change 'Copy Local' or 'Local Copy' to false.
==For content pack mods==
===For content pack mods===
The 'release package' for a content pack mod is just a <tt>.zip</tt> file containing a mod with your files, which must include at least a <tt>manifest.json</tt> and a <tt>content.json</tt>. See the specific guidelines for your framework mod that you are using.
The 'release package' for a content pack mod is just a <tt>.zip</tt> file containing a mod with your files, which must include at least a <tt>manifest.json</tt> and a <tt>content.json</tt>. See the specific guidelines for your framework mod that you are using.
===Create a content pack===
====Create a content pack====
# Create a folder with the name you want (see [[#Folder name|folder naming convention]]).
# Create a folder with the name you want (see [[#Folder name|folder naming convention]]).
# Inside the folder:
# Inside the folder:
# Launch the game, and make sure your new content pack appears under "Loaded X content packs" in the SMAPI console.
# Launch the game, and make sure your new content pack appears under "Loaded X content packs" in the SMAPI console.
===Release your content pack===
====Release your content pack====
# Add an [[Modding:Modder Guide/APIs/Manifest#Update checks|update key]] to your manifest (if you haven't already).
# Add an [[Modding:Modder Guide/APIs/Manifest#Update checks|update key]] to your manifest (if you haven't already).
# Update the <tt>Version</tt> field in the manifest. (Increase it for each release! SMAPI will use it for update and compatibility checks.) See [http://semver.org/ semantic version] for more information on version numbering.
# Update the <tt>Version</tt> field in the manifest. (Increase it for each release! SMAPI will use it for update and compatibility checks.) See [http://semver.org/ semantic version] for more information on version numbering.