Expose RTD to plugins
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 16.2k
- Forks
- 1.9k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 80
Description
RTDs are currently not exposed to plugins. This means that a hypothetical ride construction window replacement plugin does not have access to a ride's available track elements and booster speed modifier, among other properties.
Eventually™, RTDs will be exposed to the world as objects like all other types of objects and available with the getObject and getObjects API. It would be nice if a solution were devised so that RTDs are visible to plugins as objects even though they are not truly objects, for forwards compatibility.
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 by tracing how plugins access ride data and how the getObject and getObjects APIs represent objects. The work is done when RTDs are visible to plugins as objects, including their available track elements and booster speed modifier, while remaining compatible with the eventual RTD object model.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100