It's a case of wanting the best of both worlds: A speedy startup, so as not to discourage people from testing and a thorough check to make sure we don't have oddball effects caused by mismatched files.branan wrote:As for why you see a delete every launch - I bet Minkata is set up with ThinExternal == External, so it does actually check every file at login. It's slower, but for a testing shard probably better to make sure everyone is on the same page.
However, it just occurred to me to ask this: Is the release notes file part of the ThinExternal manifest? I'm guessing it is, which probably explains why the whole problem arose in the first place. Throughout MOULa, there has never been an update to the release notes, so if an update only affects files lower level files (like some of the .dat files) then they'll never be scanned on subsequent updates. In the past, the release notes would change each month.
Even if that assumption is wrong, then possibly adding the release notes to the ThinExternal manifest, and making sure it gets updated for each new release, should then force a re-check of the entire fileset on first usage after any update?