Track configuration changes
Open
Nobody has claimed this yet.
lang: c++
to-discuss
- Dominant language
- Python
- Stars
- 14.4k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
All configuration changes, e.g. mod updates, keybindings, graphics settings, etcetc should be logged. That way, a user can determine what caused some break.
Actually all software in the world should do it this way.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
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 name any files, tests, or entry points. Start by locating how configuration changes such as mod updates, keybindings, and graphics settings are handled, then define the logging scope and format; done means users can review changes and identify what caused a problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100