Crap I'm going to have to literally load your version and try it because deleting them I still get that (notepad++ editor?)
yeah, thats weird
Yes, I use notepad++. For all the files I normally work with, I use UTF-8. When I open your files though, they are listed as Western European->ISO-8859-1
So, there's two places that encoding is used - in the XML and in the file encoding data.
In XML it is just telling XML what encoding the file *should* be in - and as long as the XML engine reading the file reads that, then the file should also be in that encoding. To set the file encoding, in Notepad++ use the "Encoding" menu option. I don't know if this is the issue though, but it's good practice to make sure you're saving the files using the expected encoding.
This is insane. It has nothing to do with the comments at all. I'm willing to bet if you zip up the original code yourself and deliver it - it will work fine.
I use this script to deliver all my files.
It has always worked. I deliver these files in fact.Code:powershell "Compress-Archive '.\DeathIndicatorEx\*' '.\DeathIndicatorEx.zip'"
ren DeathIndicatorEx.zip DeathIndicatorEx.ext
move /y DeathIndicatorEx.ext "-----my dir ----\AppData\Roaming\SmiteWorks\Fantasy Grounds\extensions\"
Pause
Well I could NEVER get your files to work - not even the exact ones. I finally did the right mouse compress file by hand - renamed it to DeathIndicatorEx.ext - then manually copied it over to the extensions directory - and it worked. Every time. Every time I used my script - it did not.
Nothing has changed on my end at all. I left the comments in and it worked - IF I compressed the directory manually.
WHY is the current delivery choking on power shell generated files? What is different? What changed in how they read a zip that now makes this bad?