Even then, say if the zip contained a Runtime | ----Pose | --------MATV3Catsuit folder type structure, only duplicate filenames will be overwritten, not the subfolder itself. Folders don't get overwritten per se. You can confirm this with a simple test. Create two folders, both named 'X' or whatever, you'll have to create them in different places, of course. Put some files in one and leave the other empty. copy the empty one to the same place the other one is located. You'll get the warning - click yes. Open the folder with the files and they are still there. Put some different files in the empty folder and copy again. The new files are added to the original files in the target folder...etc. So really, you need to think in terms of the folder's contents as potential duplicates, not so much the folders themselves, if that makes sense. The main difference between copying an entire folder rather than opening it and copying the files is that with folders, once you click 'Yes,' you get no further warnings. If there are 10 duplicate names, then all 10 get overwritten. If you just selected the files themselves and copied them, you'd get a warning for each duplicare file about to be overwritten - unless you click 'Yes to All' at the warning dialog. As I said, IMO this is probably only a concern with things like reflection maps where everybody and their sibling has their own version of 'gold.jpg' for some reason. Even then, they're usually in a uniquely named subfolder. It seems fairly rare for folks to dump things in the root folder - not when you can create your own folder with '!!!!' in front of it to get top billing :-)

"Democracy is a pathetic belief in the collective wisdom of individual ignorance." - H. L. Mencken