Modding:Player Guide/Getting Started - Revision history

imported>Pathoschild: /* Can I have different mod groups? */ switch tip from ModDrop to Stardrop (content provided by Exefer on the talk page)

2026-04-28T15:39:39Z

Can I have different mod groups?: switch tip from ModDrop to Stardrop (content provided by Exefer on the talk page)

← Older revision		Revision as of 15:39, 28 April 2026
Line 340:		Line 340:
	Tips:		Tips:
	* Don't forget to copy SMAPI's bundled Console Commands and Save Backup mods to your new folder if needed.		* Don't forget to copy SMAPI's bundled Console Commands and Save Backup mods to your new folder if needed.
	* ~~On Windows only, the~~ [https://~~moddrop~~.com ~~ModDrop~~] mod manager ~~also~~ supports ~~up to three '~~mod ~~loadouts' which~~ you ~~can~~ switch between.		* [https://github.com/Floogen/Stardrop Stardrop] is an open-source, cross-platform mod manager that supports multiple mod profiles, letting you easily switch between different setups.

	{{Modding guide footer		{{Modding guide footer

imported>OnionNinja: /* Find mods */ Marked Moddrop as unsafe and delinked.

2026-02-20T00:46:51Z

Find mods: Marked Moddrop as unsafe and delinked.

← Older revision		Revision as of 00:46, 20 February 2026
Line 39:		Line 39:
	\| Most mods are released here.<br /><small>An account is required, but it's free; just don't choose a package when you register.</small>		\| Most mods are released here.<br /><small>An account is required, but it's free; just don't choose a package when you register.</small>
	\|-		\|-
	\| ~~[https://www.moddrop.com/stardew-valley/~~ ModDrop]		\| ModDrop
	\| ~~Many~~ mods are ~~released here~~.		\| ModDrop used to be a source for Stardew mods but is currently not recommended due to lack of supervision on the part of the site owners. Mod developers are encouraged to monitor it for stolen mods, but players should avoid it.
	\|-		\|-
	\| [https://forums.stardewvalley.net/index.php?resources/ Official forums]		\| [https://forums.stardewvalley.net/index.php?resources/ Official forums]

imported>Pathoschild: /* Can I have different mod groups? */ add note about copying SMAPI's bundled mods

2025-03-20T17:24:34Z

Can I have different mod groups?: add note about copying SMAPI's bundled mods

← Older revision		Revision as of 17:24, 20 March 2025
Line 336:		Line 336:
	<li>If you want access to all of the Steam features, make sure to launch Steam before executing the script.</li>		<li>If you want access to all of the Steam features, make sure to launch Steam before executing the script.</li>
	</ol>		</ol>
	\|-
	\|}		\|}

	On Windows only, the [https://moddrop.com ModDrop] mod manager also supports up to three 'mod loadouts' which you can switch between.		Tips:
			* Don't forget to copy SMAPI's bundled Console Commands and Save Backup mods to your new folder if needed.
			* On Windows only, the [https://moddrop.com ModDrop] mod manager also supports up to three 'mod loadouts' which you can switch between.

	{{Modding guide footer		{{Modding guide footer

imported>Pathoschild: /* Can I have different mod groups? */ simplify instructions for non-Steam game approach

2025-03-20T17:22:06Z

Can I have different mod groups?: simplify instructions for non-Steam game approach

← Older revision		Revision as of 17:22, 20 March 2025
Line 292:		Line 292:

	===Can I have different mod groups?===		===Can I have different mod groups?===
	Yep, SMAPI has built-in support for different mod groups. The instructions may seem complex, but it's easy once you get the hang of it:		Yep, SMAPI has built-in support for different mod groups. The instructions may seem complex, but it's easy once you get the hang of it.

	For ~~simplicity~~, you can ~~also~~ just rename the Mods folder ~~to something else~~.		(For a quick test, you can just rename the <samp>Mods</samp> folder instead.)

	{\| class="wikitable"		{\| class="wikitable"
Line 307:		Line 307:
	# Right-click the shortcut, choose <samp>Properties</samp>, and add this to the end of the <samp>Target</samp> field: <code> --mods-path "Mods (multiplayer)"</code> (changing folder name as needed). '''Don't delete any of the existing text in that field! This should be added to the end of what's already there.''' Done correctly, it should look something like <code>"your-path-here\SteamLibrary\steamapps\common\Stardew Valley\StardewModdingAPI.exe" --mods-path "Mods (multiplayer)"</code>.		# Right-click the shortcut, choose <samp>Properties</samp>, and add this to the end of the <samp>Target</samp> field: <code> --mods-path "Mods (multiplayer)"</code> (changing folder name as needed). '''Don't delete any of the existing text in that field! This should be added to the end of what's already there.''' Done correctly, it should look something like <code>"your-path-here\SteamLibrary\steamapps\common\Stardew Valley\StardewModdingAPI.exe" --mods-path "Mods (multiplayer)"</code>.
	# Double-click that shortcut to launch SMAPI with the specified mod folder.		# Double-click that shortcut to launch SMAPI with the specified mod folder.
	\|-
	~~\| Windows (Steam~~, ~~Non-Steam Game Method)~~		Tip: if you often need to switch between different folders, you can [[Modding:Installing SMAPI on Windows#Launch SMAPI as a non-Steam game\|add a 'non-Steam game' launcher to Steam]] and change its launch options instead.
	~~\| ~~
	~~# Create a separate folder for each mod group in [[#Find your game folder\|your game folder]], like <code>Mods</code> and <code>Mods (multiplayer)</code>.~~
	~~# Add SMAPI as a Non-Steam Game to your library a second time. Follow the second set of instructions in~~ [[Modding:Installing SMAPI on Windows#~~Steam\|installing~~ SMAPI ~~on Windows]] - it is highly suggested you alter the title in your Steam Library to differentiate between mod groups, such~~ as ~~"Stardew Valley Modded" and "Stardew Valley Modded Multiplayer".~~
	~~# Right~~-~~click the new SMAPI entry in your~~ Steam ~~Library, select "Properties", and~~ add ~~this to the end of the Target field: <code> --mods-path "Mods (multiplayer)"</code>. '''Don't delete any of the existing text in that field! This should be added to the end of what's already there.~~'~~'' Done correctly, it should look something like <code>"your-path-here\SteamLibrary\steamapps\common\Stardew Valley\StardewModdingAPI.exe" --mods~~-~~path "Mods (multiplayer)"</code>.~~
	~~# Click the "Play" button in the new SMAPI entry in~~ Steam to ~~make~~ Steam launch ~~SMAPI with the specified mod folder and all Steam features~~.
	\|-		\|-
	\| Linux		\| Linux

imported>Pathoschild: /* Can I have different mod groups? */ remove "Windows (Steam)" section (no need for a custom launch command, we're just appending an argument to the existing one)

2025-03-20T17:13:21Z

Can I have different mod groups?: remove "Windows (Steam)" section (no need for a custom launch command, we're just appending an argument to the existing one)

@@ Line 307: / Line 307: @@
 # Right-click the shortcut, choose <samp>Properties</samp>, and add this to the end of the <samp>Target</samp> field: <code> --mods-path "Mods (multiplayer)"</code> (changing folder name as needed). '''Don't delete any of the existing text in that field! This should be added to the end of what's already there.''' Done correctly, it should look something like <code>"your-path-here\SteamLibrary\steamapps\common\Stardew Valley\StardewModdingAPI.exe" --mods-path "Mods (multiplayer)"</code>.
 # Double-click that shortcut to launch SMAPI with the specified mod folder.
 |-
 | Windows (Steam, Non-Steam Game Method)

imported>Flaminglasrswrd: added alternate game folder on linux

2025-01-04T02:39:19Z

added alternate game folder on linux

← Older revision		Revision as of 02:39, 4 January 2025
Line 70:		Line 70:
	\|-		\|-
	\| Linux		\| Linux
	\| GOG: <code>~/GOGGames/StardewValley/game</code><br />Steam: <code>~/.local/share/Steam/steamapps/common/Stardew Valley</code>		\| GOG: <code>~/GOGGames/StardewValley/game</code><br />Steam: <code>~/.local/share/Steam/steamapps/common/Stardew Valley</code><br />Steam(alt):<code>/home/user/.steam/steam/steamapps/common/Stardew Valley</code>
	\|-		\|-
	\| Mac		\| Mac

imported>Margotbean: formatting

2024-11-19T15:01:19Z

formatting

← Older revision		Revision as of 15:01, 19 November 2024
Line 173:		Line 173:
	\|-		\|-
	\|rowspan="3"\| PC		\|rowspan="3"\| PC
	\| Linux / SteamDeck~~<ref>However, modding on SteamDeck may increase power usage.</ref>~~		\| Linux / SteamDeck*
	\| ✓ fully supported		\| ✓ fully supported
	\|-		\|-
Line 202:		Line 202:
	\| ✖ no mod support		\| ✖ no mod support
	\|}		\|}
			<nowiki>*</nowiki>''<span style="font-size: smaller;">Modding on SteamDeck may increase power usage.</span>''

	Almost all mods will work on any supported platform, since SMAPI rewrites them for compatibility.		Almost all mods will work on any supported platform, since SMAPI rewrites them for compatibility.

imported>PenguinNexus: SteamDeck is a PC, not a console.

2024-11-19T14:52:19Z

SteamDeck is a PC, not a console.

← Older revision		Revision as of 14:52, 19 November 2024
Line 20:		Line 20:
	* [[Modding:Installing SMAPI on Mac\|macOS]];		* [[Modding:Installing SMAPI on Mac\|macOS]];
	* [[Modding:Installing SMAPI on Linux\|Linux]];		* [[Modding:Installing SMAPI on Linux\|Linux]];
	* [[Modding:Installing SMAPI on Steam Deck\|Steam Deck]] (the handheld ~~console~~);		* [[Modding:Installing SMAPI on Steam Deck\|Steam Deck]] (the handheld PC);
	* or [[Modding:Installing SMAPI on Android\|Android]].		* or [[Modding:Installing SMAPI on Android\|Android]].

Line 173:		Line 173:
	\|-		\|-
	\|rowspan="3"\| PC		\|rowspan="3"\| PC
	\| Linux		\| Linux / SteamDeck<ref>However, modding on SteamDeck may increase power usage.</ref>
	\| ✓ fully supported		\| ✓ fully supported
	\|-		\|-
Line 182:		Line 182:
	\| ✓ fully supported		\| ✓ fully supported
	\|-		\|-
	\|rowspan="5"\| console		\|rowspan="4"\| console
	\| Nintendo Switch		\| Nintendo Switch
	\| ✖ no mod support		\| ✖ no mod support
Line 191:		Line 191:
	\| PS Vita		\| PS Vita
	\| ✖ no mod support		\| ✖ no mod support
	\|-
	~~\| Steam Deck~~
	~~\| ✓ fully supported, but may increase power usage~~
	\|-		\|-
	\| XBox One		\| XBox One

imported>Pathoschild: link to auto-generated mod compatibility list instead of obsolete page

2024-11-18T21:01:33Z

link to auto-generated mod compatibility list instead of obsolete page

← Older revision		Revision as of 21:01, 18 November 2024
Line 53:		Line 53:
	</ul>		</ul>

	Before you download a mod, check if it works with the [[Version_History\|latest version]] of the game. For SMAPI mods, see the [~~[Modding~~:~~Mod compatibility\|~~mod compatibility list]]; SMAPI will also automatically disable most incompatible SMAPI mods. You're on your own for XNB mods; try checking the mod description or comments for those.		Before you download a mod, check if it works with the [[Version_History\|latest version]] of the game. For SMAPI mods, see the [https://smapi.io/mods mod compatibility list]; SMAPI will also automatically disable most incompatible SMAPI mods. You're on your own for XNB mods; try checking the mod description or comments for those.

	===Find your game folder===		===Find your game folder===

imported>Pathoschild: /* Update mods */ rework to add 'clean update' instructions, since that's now the recommendation for many mods

2024-11-09T17:26:33Z

Update mods: rework to add 'clean update' instructions, since that's now the recommendation for many mods

← Older revision		Revision as of 17:26, 9 November 2024
Line 144:		Line 144:

	===Update mods===		===Update mods===
	To update a mod, ~~just replace~~ its ~~files with the new versions (making sure to keep generated files like <code>config.json</code>)~~.		There are two main ways to update a mod. Before updating a mod, don't forget to check its mod page for any special update instructions.

	~~More detailed steps~~:		; Clean update
	~~# Download~~ the new ~~mod version~~.		: Just delete the mod from your <samp>Mods</samp> folder, then install the new version normally. This is the safest way to update (since it removes any old files), but it'll also reset any mod settings to their default values.
	# ~~Check~~ the mod ~~page for any special update instructions~~.
	# Unzip it somewhere else (not in your <code>Mods</code> folder).		; Merge update
	# Open the mod's old and new folders, so the <code>manifest.json</code> is visible in both.		: If you want to keep your old settings, you can replace the mod's files with the new versions while keeping generated files like <code>config.json</code>.
	# Copy all the files/subfolders from the new folder into the old folder.
			: To do that:
			:# Download the new mod version.
			:# Unzip it somewhere else (not in your <code>Mods</code> folder).
			:# Open the mod's old and new folders, so the <code>manifest.json</code> is visible in both.
			:# Copy all the files/subfolders from the new folder into the old folder.

	===Remove mods===		===Remove mods===