satisfactorymodding / satisfactorymodding/SatisfactoryModManager
Feature Request: Assisted `>debugmods` (Fred command for binary search)
Nobody has claimed this yet.
- Dominant language
- Svelte
- Stars
- 500
- Forks
- 94
- Avg merge
- 9d 19h
- Merged PRs (30d)
- 2
Description
Having to manually enable/disable mods when debugging is extremely tedious, error-prone and may even result in RSI (Repetitive Strain Injury) for a big enough mod list. It would be nice to have SMM assist in the process, similar to how git bisect automatically checks out the commits to test and allows the user to mark them as good/bad. It would also be nice to save a log detailing what mods were present in each test, in case the issue is more complex.
Contributor guide
No contributing guide indexed for this repository
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
Start by tracing the >debugmods Fred command and compare the requested workflow with git bisect. Define how users mark each test good or bad, how mods are enabled between tests, and what the per-test log must contain. Done should be a usable binary-search debugging flow with a saved mod history.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100