First I should point out that it doesn't fail, the check and abort are by design 
KiXcrypt unpacks into a flat directory, so the check is there to ensure that you don't accidentally trash a file with the same name. As KiXcrypt removes the unpacked files when the primary script completes there is also a danger that you will remove files that you'd rather you didn't.
Code:
Any hope that a kixcrypt release with an overwrite option will be released any time soon?
No.
I've looked in the past at creating a (new) temporary sub-folder for unpacking the files to. If there is enough interest for me to start digging through the old code I may have a look at it again.
However there are quite a few packaging tools already available and the new tokenisation is good enough code obfuscation for most peoples need. I think that it is time for KiXcrypt to retire with a self indulgent smile at a job well done and let the young guns take up the reins.
