As it is, when exporting a soundpack if one .dat custom sound file can't be read and validated properly, the creation of a soundpack immediately fails....
So I was just wondering if perhaps instead of not creating anything at all, Plus! could create a soundpack with all the "valid" custom sounds, and perhaps inform the user of any "corrupt" ones.
I purposely corrupted a sound file a while back when testing something, and then couldn't remember which one, so Plus! now fails when making a soundpack of all my custom sounds. Maybe the "corrupt" ones could have their information removed from the registry and the file deleted or something similar?
Just a small suggestion