Quote:
I think that TWX should limit its file writes to the TWX folder/directory. I fail to see any good reason to allow it to write to any other areas.
I routinely read and write files outside of my twxproxy dir. Most of my in-game files are written directly to c:\, as it's easier to find them that way. I would hate to force one person's convention down the throats of every other user.
Just disabling one's ability to write outside of the twxproxy dir wouldn't be enough, I could write a script to write an alternate version of twxproxy.exe (or any other program like twxc or whatever) that would then enable me to write to any other directory... perhaps with a latent command when the program is reloaded, then force the app to crash so they'd have to reload the program. There are no protections sufficient enough to stop someone both intelligent and malevolent.
Never run scripts from someone you don't trust, and never run them in an environment where they haven't been previously tested and never run them if they're written by someone that's on another team in the same game you're in.
I once wrote a script that warped a player around, turned all corp planets personal, turned all figs personal, left the corp then cby'd... but only if they were on an enemy corp. Fortunately for them they never ran the script...
Short story made long... don't run a .CTS file unless you inherently trust the person and their motives. Most people will not make a purely malevolent script public, of course, but that doesn't mean there aren't easter eggs hidden in the code. That's why I make all of my public scripts open source... removes that concern.
As for getting feedback... only way I've managed that problem is to develop a small group of players as testers. Then you can control the process better and educate them on what data they need to collect.
