Difference between revisions of "Modding:Mod compatibility"
Pathoschild (talk | contribs) (→SMAPI mods: link unofficial update to post) |
Pathoschild (talk | contribs) (→SMAPI mods: + source links for Anti-Cheat mod) |
||
Line 226: | Line 226: | ||
|id = anticheatviachat.anticheatviachat | |id = anticheatviachat.anticheatviachat | ||
|nexus id = 2887 | |nexus id = 2887 | ||
− | |github = | + | |github = funny-snek/anticheat-and-servercode |
|beta broke in = Stardew Valley 1.3.29 | |beta broke in = Stardew Valley 1.3.29 | ||
Line 236: | Line 236: | ||
|id = funnysnek.servercode | |id = funnysnek.servercode | ||
|nexus id = 2887 | |nexus id = 2887 | ||
− | |github = | + | |github = funny-snek/anticheat-and-servercode |
}} | }} | ||
{{/oldentry | {{/oldentry |
Revision as of 15:22, 24 October 2018
Sometimes a mod will stop working due to a major game update; SMAPI automatically disables incompatible mods. This page lists known SMAPI mods and their compatibility with the latest versions, and explains how to fix broken mods if possible.
For players
What to do
- For each mod you have installed, follow the instructions in the list below. If it's not listed, try updating to its latest version.
- If a mod is still failing, post a message in the coordination thread (with your SMAPI log attached) and we'll help.
SMAPI mods
- Players: See mods.smapi.io for a more user-friendly list.
- Modders: feel free to update this list! (See instructions.)
mod name | author | compatibility[1] | broke in | source |
---|
SMAPI mods (obsolete)
These mods are either obsolete, or have been abandoned by their authors and probably won't be updated unofficially. These will likely never be updated again.
Modding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentryModding:Mod compatibility/oldentrymod name | author | compatibility[1] | broke in | source |
---|
XNB mods
For mod developers
Updating a mod
See migration guides. You can...
- Add or update your mods in the list above (see format).
- Post a message in the coordination thread to ask questions or say when your mods are updated.
- Chat or ask questions in #modding on Discord.
Creating an unofficial update
To avoid conflicting with official updates, here's the recommended way to create an unofficial update. This assumes you're creating a basic update (not a continuation or reinvention), and the code is on GitHub (adjust the steps accordingly if it's elsewhere).
- Fork the code.
- Make your changes to that fork (see updating a mod).
- Increase the version in manifest.json by 0.0.1 and add -unofficial.1-yourName.
For example, if the current version is 1.0.0 and your name is SampleUser, change it to 1.0.1-unofficial.1-sampleUser. If you need to release a new unofficial update, just increment unofficial.1 to unofficial.2, etc. This ensures that official versions supersede unofficial ones (e.g. for update checks), and other users can release newer unofficial updates if needed. - Push your changes to GitHub.
- Post a release package to the coordination thread with a link to your fork on GitHub.
(If the mod uses the NuGet build package, there should be a release package named <mod name> <version>.zip in your bin folder.) - Submit a pull request to the original author (if applicable).
Overall compatibility
48% are compatible or have a working alternative. | |
32% have an update coming soon. | |
20% are broken and not open-source.¹ |
¹ Many of these broke due to a Stardew Valley update. Some may be updated by their authors later.
Footnotes
Cite error: <ref>
tag with name "optional-update" defined in <references>
is not used in prior text.