satisfactorymodding / satisfactorymodding/SatisfactoryModManager
Clearer communication of mod Damaged/Broken status
Open
Nobody has claimed this yet.
- Dominant language
- Svelte
- Stars
- 500
- Forks
- 94
- Avg merge
- 9d 19h
- Merged PRs (30d)
- 2
Description
I have seen a number of people get confused about how mods being marked Damaged or Broken are displayed inside the application, thinking the red/yellow text was just a styling thing
Potential ideas (probably don't enact all of them):
- Also add strikethrough to the mod name
- Also add the red/yellow crosshatch like ficsit.app does with the mod icon (not sure how useful this is
- Add a pop-up before the game is allowed to launch. Presents the list of Broken/Damaged mods with expand/collapse sections to read their compat info messages
- Add a banner that appears when your profile has Broken/Damaged mods installed
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
The issue does not identify files, tests, or an entry point. First compare the proposed ways of communicating Damaged/Broken mods in the application, then agree on one concrete behavior and its completion criteria before locating the relevant UI code.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100