I'm thinking about using the launch script (posted on this forum by Spikee) which deletes verify_cache_key and then runs railworks64.exe, thereby stopping the verify files process from running during loading of the game. But before using the script I'd like to know the following... (1) Does removing verify_cache_key prevent modded files from being deleted and prevent files that have been extracted from .ap files from being deleted? Preventing such deletions is what I'm wanting to do here. (2) When is verify_cache_key installed (what triggers it to be installed)? It catches me out every time. (3) Does removing verify_cache_key prevent automatic updates from being installed when fixes or new versions of the game are available? I don't want to stop such updates, I just want to stop routes and content from being deleted and/or reinstalled in their default state. (4) Assuming answer (3) is "no", does removing verify_cache_key completely stop any chance of a verify process being run or will the game still be verified anyway when updates and new releases are installed? (5) Does verify_cache_key reappear while TSC is running? I'm thinking about what would happen if it reappeared and I was to change a graphics setting which caused TSC to prompt me to close and auto re-run it. The auto re-run would then bypass the launch script which deletes verify_cache_key. Would this immediately trigger a verify process while the game reloads? BTW, I realise that loading the game directly from Steam or its desktop icon would (obviously) bypass the script. (6) Is there anything else I need to bear in mind (side effects) to removing verify_cache_key? (7) Finally, am I wasting my time even trying to stop files from being deleted by TSC or Steam?
verify_cache_key is created as part of a verify; deleting it prevents any files flagged for deletion actually being deleted. Verify does not (or at least should not, but there have been reports that certain DLC items will trigger one when first installed)) run often when you start the game, are you thinking of the indexing of scenarios and/or the checking for any updates to Workshop subscribed items?
That file is a one-shot, included in the core depot and deleted by TSC itself after verifying content (and after first run, because Steam will always leave user content in place.) You will not need it unless you are having issues caused by modded files you can't pinpoint yourself. I do not need to take care because Steam doesn't know my E:\RailWorks. It only gets triggered by launching RailWorks64.exe, which looks up steam_appid.txt, tells Steam app 24010 is running to give its "Ok" to run as RailWorks cannot run without Steam by design .
