38
edits
Changes
Jump to navigation
Jump to search
Line 19:
Line 19: − :::* 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.
Modding:Player Guide/Troubleshooting (view source)
Revision as of 03:36, 20 February 2020
, 03:36, 20 February 2020→The basics
::* 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.
::* 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>
:::* 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>
# If you've narrowed down the issue to a specific mod or group of mods, try performing a clean reinstall. Remove all folders for the mod that's causing the issue, making sure to check the mod page for a list of every folder that's included. (If you're downloading mods from Nexus, you can look under "Preview File Contents." On ModDrop, you can find that information under "Files" on the sidebar.) Then, redownload the mod and follow the installation instructions on the mod page. If you normally use a mod manager, reinstall the mod manually to make sure your issue wasn't caused by the mod manager placing files in the wrong locations.
# If you've narrowed down the issue to a specific mod or group of mods, try performing a clean reinstall. Remove all folders for the mod that's causing the issue, making sure to check the mod page for a list of every folder that's included. (If you're downloading mods from Nexus, you can look under "Preview File Contents." On ModDrop, you can find that information under "Files" on the sidebar.) Then, redownload the mod and follow the installation instructions on the mod page. If you normally use a mod manager, reinstall the mod manually to make sure your issue wasn't caused by the mod manager placing files in the wrong locations.
# 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. If you still get the error, look through the common issues on this page or [https://stardewvalleywiki.com/Modding:Help#Using_mods ask for help!]
# 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. If you still get the error, look through the common issues on this page or [https://stardewvalleywiki.com/Modding:Help#Using_mods ask for help!]