Gothic.ini: a new VR key lands at the end of the file and is never read back

未关闭 适合新手
#487 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
69/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
csharp, unity
领域
game-dev

调研方向

首先阅读 GothicIniWriter.WriteSetting,并跟踪当节存在但键不存在时它的处理方式。使用 VR 节不是最后一节的 Gothic.ini 重现问题,然后更改设置并重启。完成的标准是新键写入其所属的节中,并在下次启动时被找到,而不是反复追加到末尾。

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

描述

bug
Description

GothicIniWriter.WriteSetting: when the section is found but the key isn't, lines.Add appends the key at the end of the file, so it lands in the last section. The next write doesn't find it in its own section and appends it again.

Expected Behavior

A new key is written inside its own section and found again on the next start.

Actual Behavior

Seen on Quest 3, G2: six snapRotationAmount= lines under [ZBUGFIXES] (the last section, written by Spine). The snap rotation setting is back to the default on every start.

Reproduction Steps
  1. Use a Gothic.ini whose VR section exists but lacks the key (e.g. snapRotationAmount), and where that section isn't the last one.
  2. Change the setting in the menu a few times and restart.
  3. The key is appended at the end of the file again each time, and the setting is lost.

Environment Information

  • Reproducibility: Always (for keys missing from an existing, non-last section)
  • Platform: all
  • Game Version: main 83a1aebd2
Notes

BoroBongo has a fix: WriteSettingInSection behind DeveloperConfig.EnableIniWriteInSection in experimental/game-completion-candidate-vibecoded-borobongo. It's in no split yet, and his comment describes the same bug ("marvinPanel 20 times").

主要语言
C#
星标
33
派生
1
平均合并
1 天 17 小时
30 天内合并 PR
51

环境准备

从这里开始

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

Gothic-Unity-Project/Gothic-Unity 的其他 Issue

查看 Gothic-Unity-Project/Gothic-Unity 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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