I'm listed as a maintainer on many mods, so unfortunately I can't actively develop all of them. To set expectations, I maintain them in a few rough tiers listed below.
These are mods I actively develop, maintain, and support. I usually update them within an hour of a major game update, and they're part of my monthly mod update cycle.
That includes...
- Tools:
- SMAPI and its web services (e.g. update check API, mod compatibility list, etc);
- StardewXnbHack;
- Mod build config package;
- Mod translation class builder package.
- Mods:
These are mods I maintain and support. I actively answer comments on the mod pages and might release occasional improvements, but mostly I just fix bugs to make sure they're stable and work for everyone.
That includes...
- Bouhm's mods:
- Cantorsdust's mods:
- ChroniclerCherry's mods:
- Teban100's mods:
- Zoryn's mods:
These are mods I keep compatible. I might release rare improvements, but mostly I just keep them compatible with game/SMAPI updates and fix critical issues. I'll often read comments, but might not actively answer questions there if I'm busy (e.g. due to a recent game update).
That includes...
- Bouhm's mods:
- ChroniclerCherry's mods:
- Catalogues Anywhere;
- Change Slime Hutch Limit;
- Custom Crafting Stations;
- Customize Anywhere;
- Expanded Preconditions Utility;
- Farm Rearranger;
- Hay Bales as Silos;
- Limited campfire Cooking;
- Multi Yield Crops;
- Multiplayer Mod Checker;
- Platonic Relationships;
- Profit Margins;
- Shop Tile Framework;
- Snack Anything;
- Tool Upgrade Costs;
- Upgrade Empty Cabins;
- funny-snek's mods:
- 21 mods by Omegasis (backup maintainer);
- 46 mods by spacechase0 (backup maintainer).
I often submit pull requests to update other mods, but I don't maintain or support them otherwise. Mod authors are welcome to post unofficial updates based on my pull requests.
This includes over 100 mods on Nexus I was given editor access to, but which might be missing some of the requirements listed below.
Ideally you should maintain your mods, or find someone interested in actively maintaining or co-maintaining them.
If absolutely needed though (e.g. you're leaving the community), I can keep your mods compatible. This has a few requirements:
- The mod must be open-source.
- You can revoke permission anytime, but while I'm maintaining them you agree I can refactor the code, fix bugs, or make any improvements as needed.
- You must give me editor access to both the mod page and the Git repository so I can release updates.
(On Nexus, see Manage > Permissions > User Permissions. On GitHub, see Settings > Manage Access.) - Don't forget to message me to discuss how I'll maintain them first!
Due to the number of mods I maintain, when there's a major game/SMAPI update I'll start with popular mods and GitHub repos which contain many mods (so I can update multiple at once).
Unfortunately that's not really feasible. It depends on the mod's support tier:
| issue | priority mods | supported mods | keeping the lights on |
|---|---|---|---|
| incompatible with game/SMAPI update | ☑ yes | ☑ yes | ☑ yes |
| critical bug (e.g. save corruption) | ☑ yes | ☑ yes | ☑ yes (if time permits) |
| major bugs | ☑ yes | ☑ yes | ☐ sometimes (if time permits) |
| general bugs | ☑ yes | ☑ yes | ☐ rarely |
| new feature development | ☑ yes | ☐ rarely | ☐ very rarely |
A mod might move up in support tiers over time as I become more involved in them (e.g. the CJB mods moved from keeping the lights on to priority mods over time).
Do you get Nexus donation points for the mods you maintain?
Usually no. Often the mods are either not opted in, or the original authors still receive the donation points.
Yep! All the mods I maintain will always be free and open-source, but it takes a lot of time and money (e.g. database and web hosting, domains, coffee, etc). Every dollar donated helps support ongoing development and is greatly appreciated!
See Support SMAPI ♥ on the SMAPI site if you'd like to donate.