Move all objects to object folders
Open
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 26
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
I think it would make more sense if we stored all of the built in objects in object folders. (eg: object.json in a folder with any accompanying image files) I have a few reasons for this.
- Presently, having nearly all of the built in objects as loose jsons has caused a lot of trouble among new object makers. As this repo is one of the main resources for people looking to make new objects. Especially those that only exist in OpenRCT2. So having the jsons loose teaches them bad habits that's just resulting in broken objects being sent out. I've already seen a fair number of people sharing unexportable jsons of climates/peep names or wondering why their .parkobj isn't getting read as the game only reads "object.json" from parkobj.
- This would automatically build all of the built in objects as .parkobj, which would result in some minor but still nice file size reductions thanks to everything getting zip compression, instead of just the objects with images.
- And lastly, this is pretty minor but it would make doing work on this repo a bit more consistent since every object would have the same structure. It would also make it easier to add new/replacement images to existing objects whenever original sprite fixes are needed.
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 inspecting the repository's loose built-in object JSONs and any existing object folders or .parkobj packaging. Determine how the repository builds or exports objects, then confirm that every built-in object uses an object folder and that the resulting .parkobj files are readable by OpenRCT2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- content, game-dev
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100