38
edits
Changes
Jump to navigation
Jump to search
Line 8:
Line 8: + + + + + + + + + + + + + +
Modding:Player Guide/Troubleshooting (view source)
Revision as of 02:44, 20 February 2020
, 02:44, 20 February 2020→The basics
# Make sure you have Stardew Valley {{version|link=0}} or later.<br /><small>Click the "?" button on the title screen, and the version will appear in the bottom-left.</small>
# Make sure you have Stardew Valley {{version|link=0}} or later.<br /><small>Click the "?" button on the title screen, and the version will appear in the bottom-left.</small>
# If you use SMAPI, make sure you have the [https://smapi.io/ latest version of that].<br /><small>The SMAPI version is shown at the top of the SMAPI console window.</small>
# If you use SMAPI, make sure you have the [https://smapi.io/ latest version of that].<br /><small>The SMAPI version is shown at the top of the SMAPI console window.</small>
# If you use SMAPI, upload a log to [https://smapi.io/log the log parser], following the instructions on that page to find where your log is stored. It can help you diagnose common errors.
# The very top of your log will show a list of all your mods that need to be updated with links to the mods. You can also use [https://www.nexusmods.com/stardewvalley/mods/2536 Mod Update Menu] to keep track of your updates from the in-game menu. '''The first thing to try when you're having issues with mods is to update everything shown there, even if some of the mods seem to be working fine right now.'''
# Check the part of your log under the list of mods you're using, below where it says <code>Filter messages:</code> That will show a list of warnings. The warnings in orange text under <code>Changed save serializer</code>, the list of mods under <code>Patched game code</code>, and the list of mods with <code>No update keys</code> can generally be ignored at first. '''The most important part to look at is this section in red:'''
<pre style="white-space:pre-wrap; width:55%; color:red; margin-left:60px;">16:56:04 ERROR SMAPI Skipped mods
16:56:04 ERROR SMAPI --------------------------------------------------
16:56:04 ERROR SMAPI These mods could not be added to your game.</pre>
::* If you see an error ending with <code>because it's no longer compatible</code>, the mod didn't load because it's too outdated. Check [https://smapi.io/mods the compatibility page] to see if there's a working unofficial update.
::* If you see an error ending with <code>because it's not a SMAPI mod</code> or <code>because it doesn't have a manifest.json</code>, you've either tried to install an outdated XNB mod by putting it into your Mods folder (see [https://smapi.io/xnb this page] for more information), or a mod was installed incorrectly so SMAPI can't read it as a mod.
:::* Mods need to have a correctly formatted <code>manifest.json</code> file in the correct folder level in order for SMAPI to read them. If you've installed a mod that SMAPI is telling you may be an XNB, or you get an error in your log about a mod that doesn't have a manifest, double check that it's installed correctly. <br><small>When you unzip mods, the folder for the mod should never look like <code>PineapplesEverywhere-1.0.4.zip-500-1-0-4-1547827625</code>--if it does, there may be loose files like a readme.txt, example images, or stray junk files directly inside that folder and SMAPI won't be able to find the manifest. To fix this, find the <code>PineapplesEverywhere</code> folder inside of that folder and drag it into Mods.</small>
:::* Make sure you don't have any stray .zip files inside your Mods folder, including the SMAPI installer.
:::* Most framework mods, like Content Patcher, Json Assets, Custom Furniture, or TMXL Map Toolkit (formerly TMXLoader), support content packs, separate mods that use the framework's code as a base to add or change content. These will be in folders that look like <code>[CP] Apples Nowhere</code>; sometimes that folder will be bundled together in a subfolder with parts of the mod that use other frameworks, like an <code>Apples Nowhere</code> folder with <code>[CP] Apples Nowhere</code> and <code>[JA] Apples Nowhere Objects</code> inside. Most content packs for framework mods should go directly into your Mods folder and will have their own manifests.
::::* 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>
<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>
===<span id="reset-content">Reset your content files</span>===
===<span id="reset-content">Reset your content files</span>===