Changes

::::* A number of framework mods have older documentation floating around from versions where content packs were not supported and you would have to put the pack into the main mod's folder. Most of the time this isn't true, but certain mods, like More Giant Crops, Adopt and Skin or Custom Critters, don't have content pack support. ''Make sure to read the instructions on the framework mod's page for how to install content packs!'' Sometimes "no manifest" errors come from trying to install a pack that purposely has no manifest because it needs to go into one of the folders inside the main framework mod.

::::* A number of framework mods have older documentation floating around from versions where content packs were not supported and you would have to put the pack into the main mod's folder. Most of the time this isn't true, but certain mods, like More Giant Crops, Adopt and Skin or Custom Critters, don't have content pack support. ''Make sure to read the instructions on the framework mod's page for how to install content packs!'' Sometimes "no manifest" errors come from trying to install a pack that purposely has no manifest because it needs to go into one of the folders inside the main framework mod.

::* If you see an error ending with <code>because you have multiple copies of this mod installed</code>, the log parser will tell you the folders your extra copies are in. This is often caused by mods changing folder names, forgetting to remove old copies from your organizational subfolders when updating, or being inconsistent with whether you take everything out of the mod's subfolder when updating or leave it together. <small>(ex. when you first downloaded Artisan Valley, you took the <code>[CP]</code> <code>[JA]</code> <code>[PFM]</code> folders out of the <code>[PPJA] Artisan Valley</code> folder, but when you updated it, you put the whole <code>[PPJA]</code> folder into Mods).</small>

::* If you see an error ending with <code>because you have multiple copies of this mod installed</code>, the log parser will tell you the folders your extra copies are in. This is often caused by mods changing folder names, forgetting to remove old copies from your organizational subfolders when updating, or being inconsistent with whether you take everything out of the mod's subfolder when updating or leave it together. <small>(ex. when you first downloaded Artisan Valley, you took the <code>[CP]</code> <code>[JA]</code> <code>[PFM]</code> folders out of the <code>[PPJA] Artisan Valley</code> folder, but when you updated it, you put the whole <code>[PPJA]</code> folder into Mods).</small>

<ol><li value="7">If you've gone through these steps and are still having problems, the issue may be caused by an outdated XNB mod. Follow the instructions below to try resetting your content files. You can also always [https://stardewvalleywiki.com/Modding:Help#Using_mods ask for help!]</li>

<ol><li value="7">If you've gone through these steps and are still having problems, the issue may be caused by an outdated XNB mod. Follow the instructions below to try resetting your content files. You can also always [https://stardewvalleywiki.com/Modding:Help#Using_mods ask for help!]</li></ol>

===<span id="reset-content">Reset your content files</span>===

===<span id="reset-content">Reset your content files</span>===