Why arent the old scattered dlls in the various plugin folders simply crushed by the new fscript version whenever it's updated ?
my concern is the opposite -- i think trying to delete/modify these files is likely to be problematic to do in an automated fashion.
for me the main goal should be on the other end of the issue -- making fscript2 not need to create or modify files.
i dont think there is anything wrong with forcing existing plugin writers to update their fscript based plugins, and i can even make farr ignore the old directories or do other things, i just think that trying to have one plugin delete/modify files in other plugin directories is very likely to fail in confusing ways on windows vista and win7, which is just not going to let you do this in the program files subdirectory.