Use new ride types where appropriate
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 26
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
OpenRCT2 split up five ride types some time ago. This change has not yet been applied to this repository, so currently OpenRCT2 still converts it on the fly. The objects in question should be modified.
Also, it would be a good thing if the DAT conversion script could be modified to take the new ride types into account.
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
Start by locating the object definitions and the DAT conversion script, then compare the five ride types split in OpenRCT2 with the types currently used here. Update the affected objects and conversion logic so the new ride types are represented without relying on on-the-fly conversion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- game-dev, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100