Expand features for local mod management
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 155
- Avg merge
- 16h 10m
- Merged PRs (30d)
- 59
Description
Is your feature request related to a problem? Please describe.
One of the biggest issues I have with RimWorld is that you can't rollback mods. Especially important if a new major version releases, e.g. 1.4. Some mods are already updated and now unusable with 1.3, and others are not updated and incompatible with 1.4. AFAIK Steam workshop only allows updates, no downgrades.
Same issues with mods that break with an update, it would be nice to just go back to what I'm used to have.
Describe the solution you'd like
Local mods could solve this issue. It would be great if RimSort could create / update local mods to keep multiple versions of a mod around and switch them if required.
Describe alternatives you've considered
Alternative is, well, doing everything manually. But it would be nice having it automated.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the existing mod-management flow; done would mean that RimSort can create or update local mod copies, retain multiple versions, and switch between them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100