Original Summary

Sharing Moonlit Restoration, a newly released Godot mystery visual novel from High Player. It has nine connected chapters, restoration and evidence puzzles, three optional romantic conclusions, and an independent ending. This is a commercial release at US$9.99; the trailer is viewable without buying the game. The useful development lesson was save validation. Campaign progress is checked by replaying an action journal. Late in testing, one autosave took roughly 600ms because the current state, temporary file and backups repeated semantic validation. That delay happened on dialogue advancement, not only in the save menu. The fix caches hashes of complete payloads already produced by legal runtime actions or successfully replayed. A cold process or modified payload still goes through replay. Focused Chapter 9 checks measured roughly 59–62ms for an action plus the same atomic autosave on the production Mac. Mutated trust, route, node and journal data remained rejected. This is a local measurement, not a benchmark for every machine. AI tools were used for story text, art, translation and code: GPT-6 Astra and GPT Image 2, with separately licensed piano and fonts. Route traversal and evidence reachability were checked independently of the generated text. Actual renderer captures also caught choice panels covering character faces, so short prompts now size the panel to their content. Trailer: https://www.youtube.com/watch?v=nk43X5fR2Ps Game: https://high-player.itch.io/moonlit-restoration The game includes English and Simplified Chinese. macOS Universal has local checks; the Windows x64 download is explicitly experimental because native Windows playtesting is pending. For developers using journal replay, where do you draw the boundary between revalidating a save and trusting a state already validated in memory?   submitted by   /u/Foryou-whitesir [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/6 13:14:14