GUI or Script validation checks - Security

#1 If you're distributing .cs files, there's no helping you. But for .dso files, it should be quite trivial to go right in the source where they are written/read and add a custom encryption or simply some arbitrary changes on how the data is written/read so it breaks compatibility with standard Torque DSO files.

Also, it's trivial to remove the ability of generating new DSO files. Look into the exec() and compile() console functions' source code. You can also do so without breaking the ability of executing the prefs file or have a separate function for loading prefs which is not capable of compiling and runs the prefs in "safe mode", where several things are not allowed in the script (declaring functions, packages and creating objects).

#2 Hi Thanks for your reply. I've already done the compileAll and removed various things from scripts, removed the .cs files. Someone with knowledge could just replace these dso files with compiled versions of their own .cs file to replace what is there (or from the torque demo). I think the best method would be authentication at each stage via a web server. But this would probably be a slow process, and resource hungry each time a verification takes place. Any other suggestions?

#3 I need to understand .dso files a bit more - in a dedicated server environment, are dso files checked for comparison with a players installation of the game? Such as file size, from what I remember if art/mission in the days of TGE were not the same on the dedicated server you would need to download the latest version of the game. Not sure if this applies to dso files.