Let SMAPI explain the mod stack before you change the farm.

Install on PC

1. Launch the clean game and back up the save folder before adding content or changing game versions.
2. Download SMAPI from smapi.io or its maintainer's release page. Extract the installer and run the script for your operating system.
3. Follow the installer's platform-specific launcher instructions. On Windows you can also test directly through StardewModdingAPI.exe in the game folder.
4. Launch once and confirm SMAPI reaches the title screen. Close the game.
5. Download a mod from the author's primary page. Check current game and SMAPI compatibility, required mods, optional integrations, and multiplayer notes.
6. Extract the mod so its own folder sits inside the game's Mods folder. Do not leave the ZIP there and do not nest it under multiple wrapper folders.
7. Launch through SMAPI and read every red or purple message before loading your important save.

Understand dependencies and content packs

A content pack contains data for a framework mod. It may add portraits, maps, events, dialogue, items, or locations without containing its own executable code. Install the named framework—often Content Patcher—at the compatible version, then install the content pack as a separate folder. Do not merge the pack into the framework folder. If a large expansion lists multiple requirements, verify each requirement and its own dependencies before diagnosing the expansion.

Saves and multiplayer

• Keep a save from before adding a major expansion, map, farm layout, NPC, or item framework.
• Removing cosmetic content is different from removing a mod that added locations, quests, crops, machines, or persistent items. Follow the author's removal notes.
• For multiplayer, identify which mods every player needs, which are host-only, and which are cosmetic client-only. Match versions before joining.
• Use separate mod groups or profiles for different farms when their required content differs.
• Do not test a broken update by repeatedly saving the farm. Preserve the last known-good save and mod set.

Read the SMAPI evidence

1. Update SMAPI first when a game update changes compatibility.
2. Use the compatibility list and the update notices in the console.
3. Open the parsed SMAPI log when requesting help; it records versions, skipped mods, missing dependencies, duplicate folders, and stack traces.
4. Remove the newest optional batch and relaunch. For a large set, binary-search optional mods while leaving required frameworks active.
5. When the game works cleanly, restore compatible mods in dependency order rather than copying the entire broken Mods folder back.