Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Move all objects to object folders

未关闭
#397 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
停滞
技术栈
json
领域
content, game-dev

调研方向

首先检查仓库中零散的内置对象 JSON，以及任何现有的对象文件夹或 .parkobj 打包方式。确定仓库如何构建或导出对象，然后确认每个内置对象都使用对象文件夹，并且生成的 .parkobj 文件可由 OpenRCT2 读取。

由索引模型根据 Issue 内容生成。

描述

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.

  1. 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.
  2. 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.
  3. 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.
主要语言
F#
星标
26
派生
47
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

OpenRCT2/objects 的其他 Issue

查看 OpenRCT2/objects 的全部 Issue

相似的 Issue

更多 Content Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。