terox 314 Posted September 30, 2015 The recent 1.52 patch which turns filepatching off by default has been implemented as a security fix. What is basically does is stop access to files that are outside of pbo folders. For example if your mission execvm's a script in an external folder Filepatching no longer permits this by default. This however is not supposed to effect any scripts being run in this way serverside, but, unfortunately it does. Point to note, this does not break any #Include preprocessor commands, they remain unnaffected However, if your server is set up to run files in this way, loadfile, call, preprocessfile, exec, execVM, you can work around this issue by implementing the following server commandline parameter: -filepatching servercfg entry: allowedFilePatching = 1; This now allows me to execVm a script locally that is in the server's userconfig folder. 1 Share this post Link to post Share on other sites