satisfactorymodding / satisfactorymodding/SatisfactoryModManager

In-App/At-Website Bug Reporting

Open
#267 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Svelte
Stars
500
Forks
94
Avg merge
9d 19h
Merged PRs (30d)
2

Description

I look at Nexus Mod Manager when making this enhancement request, but it would be really helpful for the entire community if bugs could be reported publicly in a forum-like format, to be more able to make an informed decision whether or not a mod is stable enough for your setup, and having that in the SMM feels like the most streamlined it could be. I have a large mod installation (130 mods loaded at present), and it is quite troublesome having to go through several different developer's personal discord servers/websites because there is no centralized area for bug reporting - it is much more time consuming than it needs to be. Moreover, it feels like one helluva chore to get crashlogs to the eyes that need to see them. I personally understand that this request is an undertaking, but I gotta put it out there anyway.

Also to note: a centralized bug-reporting system would encourage more bug reports, and thus quicker and more streamlined updates and more stable mods, which benefits the entire community as a whole. If at all possible, setting up a suggestion system alongside this (since they are in the same realm of development) would definitely help drive mods to much greater heights.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name any files, tests, or entry points. Begin by mapping how the SMM app and website currently handle users, mods, crash logs, and community communication; done would require an agreed scope and design for a centralized public bug-reporting system, with suggestions considered separately.

Written by the indexing model from the issue text.

Assessment

Domain
backend, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.