[RELEASE] Texture Cache Maintenance utility
As it says in the first post, it's an example properties file. You don't have to use it. You should only use (ie. configure) the properties you need.

To answer your question, the command line properties trump the cfg file properties.

My advice would be to include in your cfg file only those properties that are different from the default. Most people don't need a cfg file at all.

Properties that might change from one invocation to another (eg. qa.nfo.refresh) are better left on the command line IMHO. A property such as qaperiod, which defaults to 30, should be added to your cfg as "qaperiod=-1" if you always want to use an infinite period.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.

Messages In This Thread
Crash on Gotham on OS X - by desepticon - 2014-05-29, 17:57
RE: [RELEASE] Texture Cache Maintenance utility - by Milhouse - 2016-10-11, 15:32
Cleaning - by AleisterHH - 2018-05-28, 22:03
RE: Cleaning - by Milhouse - 2018-05-28, 22:16
qax genre not updated - by Just-Me_A-User - 2018-06-12, 22:06
RE: qax genre not updated - by Milhouse - 2018-06-12, 23:40

Logout Mark Read Team Forum Stats Members Help
[RELEASE] Texture Cache Maintenance utility17
This forum uses Lukasz Tkacz MyBB addons.