Save Track Design scenery cap issues
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 16.2k
- Forks
- 1.9k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 80
Description
Whenever I try to save a track design and I reach the maximum scenery elements allowed to be associated with a ride, most of the time the game will allow me to deselect scenery elements, but not reselect them or any others.
I can't really describe how to replicate this issue from scratch, though usually the "Select Nearby Scenery" option on a ride with many elements can result in this error happening.
Contributor guide
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 with the Save Track Design flow and the Select Nearby Scenery option on a ride near its scenery-element cap. Reproduce the state where deselected scenery cannot be reselected, then trace the related game logic. Done means scenery can be deselected and reselected, including other elements, when the cap is reached.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100