Log files a game or its mod loader rewrites on every run look like a game update #109

Closed
opened 2026-10-24 23:23:40 -05:00 by ethan-hann · 0 comments
Owner

Dogfooding Control: Resonant on 0.9.7 (Windows): after a few minutes of play the after-play dialog said "5 files in the game's own folder also changed while you played, as an update would", and History then showed "4 mod files updated" for the session. The five files were crloader.log and four crmods/<mod>/<mod>.log files that the mod loader rewrites on every start. No game file or mod changed. Many modded games behave like this, so every session warns about an update that never happened, adds a version-and-mods snapshot, and makes History noisy.

This reverses the part of D7 that left built-in ignore rules out (decided 2026-10-24: that was an old call, made before update rollback and the after-play update note existed). Proposal:

  1. When adding a game (manual, template or library import), add a "Leave out log files" rule (**/*.log) to Files to leave out by default, shown and removable like any rule, with a plain explanation. Existing games are not changed silently.
  2. After a session, when the only files that changed in the game's own folder are logs (or other files that look like run-time output: *.log, *.dmp, crash folders), say so instead of the update note, and offer "Leave these out from now on", which adds the matching rule for that game in one click (and keeps this session's choice as it is).
  3. Record the call in D7 (and D13/D41 where they describe the after-play update note), and check that a rule never matches the saves folder (the editor already warns about that).

Check on real installs first: list which file kinds games and mod loaders rewrite during play (logs, crash dumps, shader caches inside the install folder) across the games on the dev PC, and only default-exclude kinds that are never part of a game or a mod.

Dogfooding Control: Resonant on 0.9.7 (Windows): after a few minutes of play the after-play dialog said "5 files in the game's own folder also changed while you played, as an update would", and History then showed "4 mod files updated" for the session. The five files were `crloader.log` and four `crmods/<mod>/<mod>.log` files that the mod loader rewrites on every start. No game file or mod changed. Many modded games behave like this, so every session warns about an update that never happened, adds a version-and-mods snapshot, and makes History noisy. This reverses the part of D7 that left built-in ignore rules out (decided 2026-10-24: that was an old call, made before update rollback and the after-play update note existed). Proposal: 1. **When adding a game** (manual, template or library import), add a "Leave out log files" rule (`**/*.log`) to Files to leave out by default, shown and removable like any rule, with a plain explanation. Existing games are not changed silently. 2. **After a session**, when the only files that changed in the game's own folder are logs (or other files that look like run-time output: `*.log`, `*.dmp`, crash folders), say so instead of the update note, and offer "Leave these out from now on", which adds the matching rule for that game in one click (and keeps this session's choice as it is). 3. Record the call in D7 (and D13/D41 where they describe the after-play update note), and check that a rule never matches the saves folder (the editor already warns about that). Check on real installs first: list which file kinds games and mod loaders rewrite during play (logs, crash dumps, shader caches inside the install folder) across the games on the dev PC, and only default-exclude kinds that are never part of a game or a mod.
ethan-hann added this to the 1.0 milestone 2026-10-24 23:23:40 -05:00
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ethan-hann/SavePoint#109
No description provided.