Caching
The autodownloader supports three levels of caching: None, Memory, and Full. These are detailed below.

None
This is set by using the following entry in nwn2player.ini:
CachingStrategy=0
This option is the most secure, as it will force NWN2 to fully scan every required file several times during the download process: when the client first connects, again after any required downloads are completed, and yet again when the player chooses or creates their PC. No results are cached on the player's machine, not even in-memory. However, this comes at a price: if you have a lot of files, or any large files, it means the player must wait for all of these scans to finish every time they log in - even if they disconnect and reconnect.
 This option is recommended only if you have a very small module - -less than 100MB, including hak paks.

Memory
This is set by using the following entry in nwn2player.ini: CachingStrategy=1
This option is a compromise between “None” and “Full”. The first time a player attempts to connect, all required files are fully scanned for updates. These results are kept in the client's memory; subsequent scans will first check this in-memory cache against the local files, to determine if the files have been modified. Memory cache is erased when the client is exited, either by crashing or closing normally. Disconnecting and reconnecting to your server does not clear the memory cache. The only exceptions to this are resources marked as “critical” - they will always be fully scanned no matter which caching option is used.
 This is the minimum cache setting recommended, and is the default setting used.

Full
This is set by using the following entry in nwn2player.ini: CachingStrategy=2
NWN2: Autodownloader Server Admin Guide
Marc Paradise & Rob McGinnis
Last Modified: Apr. 07, 2009 3:44 PM
Obsidian Entertainment
Page 7 of 9
Full caching provides the ideal experience for your players and as such is the recommended configuration. Once files are verified, the results of that verification are cached and saved to the player's machine in an encrypted file. These cached results are used in subsequent checks to determine if players have modified their copy of the files. The only exceptions to this are resources marked as “critical” - they will always be fully scanned no matter which caching option is used.
This is the cache setting recommended for most PW servers.