You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
This is true. However, due to that same zip compression, reading the objects comes at a small overhead due to having to decompress them. This may be insignificant, due to the decompression time being offset by reduced read times. However, it isn't negligible, I think.
In that case, by how much so? How much longer does it take to load all the objects with or without zip compression?
Unless it's longer by a great amount, i feel like smaller sizes would be better overall. On my end and on an individual object level i can't tell the difference between the loading times of a json object and a well made parkobj at all.
Activity
AaronVanGeffen commentedon Aug 9, 2025
This is true. However, due to that same zip compression, reading the objects comes at a small overhead due to having to decompress them. This may be insignificant, due to the decompression time being offset by reduced read times. However, it isn't negligible, I think.
ZeeMaji commentedon Aug 9, 2025
In that case, by how much so? How much longer does it take to load all the objects with or without zip compression?
Unless it's longer by a great amount, i feel like smaller sizes would be better overall. On my end and on an individual object level i can't tell the difference between the loading times of a json object and a well made parkobj at all.
IntelOrca commentedon Aug 11, 2025
Fwiw, you can zip the files with no compression should the load times be longer.