CleverRaven / CleverRaven/Cataclysm-DDA
Google sheet for reporting issues with mapgen
- Dominant language
- C++
- Stars
- 13.2k
- Forks
- 4.6k
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 205
Description
### Is your feature request related to a problem? Please describe.
A lot of the mapgen is outdated and doesn't fit the theme anymore / has weird spawns / spawns too often or not often enough / ... and not everyone wants to make an issue about it so I've made a spreadsheet people can be pointed to whenever they have a complaint and I'll take a look at it.
### Solution you would like.
Link to the spreadsheet: https://docs.google.com/spreadsheets/d/1vb336orvGpthZb869UXZc6GZCr_z0fBVTJU82izb2I0
### Describe alternatives you have considered.
Opening an issue for each separate problem, not everyone has or wants to have a github account, write down a detailed explanation and hope someone picks it up.
A spreadsheet is (for me at least) more organized and makes it easier to keep track of issues.
### Additional context
Please play nice and don't delete rows that others have added or grief the spreadsheet, if it happens too much I will stop this :)
Contributor guide
Research direction
Start by reading the issue body and reviewing the linked Google Sheet to understand the proposed mapgen reporting workflow. Done would require a maintainer decision on whether and how this external spreadsheet should be adopted or linked by the project.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100