What is going on with the simple addon upload system? I don't host my svn on CurseForge so I upload the zip directly. My zip is 677K in size. It's 677K on my system and it's 677K over on WoWInterface. However, on Curse when I upload it, it's being truncated down to 650K. Also, users are confused that it states "locally modified" and are concerned that something is wrong with it.
And while I'm on the soapbox, why on Earth would I want to release a version for WoW 1.0? Do we really need all "Supported Game Versions" back to November 2004? If so, how am I supposed to confirm it's backwards compatible without seriously violating Blizzard's legal terms?
Oh my gosh. My only response is why? This is nearly as bad as the entire site redesign a day before the Invasion event for WotLK went live. Ah, late 2008, I remember it well.
What is going on with the simple addon upload system? I don't host my svn on CurseForge so I upload the zip directly. My zip is 677K in size. It's 677K on my system and it's 677K over on WoWInterface. However, on Curse when I upload it, it's being truncated down to 650K. Also, users are confused that it states "locally modified" and are concerned that something is wrong with it.
And while I'm on the soapbox, why on Earth would I want to release a version for WoW 1.0? Do we really need all "Supported Game Versions" back to November 2004? If so, how am I supposed to confirm it's backwards compatible without seriously violating Blizzard's legal terms?
converting from LF to CR\LF line endings is not helping compression at all imho, on the contrary.. it adds an extra byte for every line of text in a source file...extra byte that can affect your "all the way up" compression :)
converting from LF to CR\LF line endings is not helping compression at all imho, on the contrary.. it adds an extra byte for every line of text in a source file...extra byte that can affect your "all the way up" compression :)
Yea, that was a bug due to the way it was being processed, it has since been fixed but is in QA right now since it required a rewrite of the processor
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
What is going on with the simple addon upload system? I don't host my svn on CurseForge so I upload the zip directly. My zip is 677K in size. It's 677K on my system and it's 677K over on WoWInterface. However, on Curse when I upload it, it's being truncated down to 650K. Also, users are confused that it states "locally modified" and are concerned that something is wrong with it.
And while I'm on the soapbox, why on Earth would I want to release a version for WoW 1.0? Do we really need all "Supported Game Versions" back to November 2004? If so, how am I supposed to confirm it's backwards compatible without seriously violating Blizzard's legal terms?
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumthe zip changes are because Curse is now mangling uploaded zip files..
see
https://www.curseforge.com/forums/wow-sites/wow-sites-feedback/127329-file-checksums-and-timestamps-changed-after-upload
and
https://www.curseforge.com/forums/wow-sites/wow-sites-feedback/127754-stop-changing-our-code
Oh my gosh. My only response is why? This is nearly as bad as the entire site redesign a day before the Invasion event for WotLK went live. Ah, late 2008, I remember it well.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumconverting from LF to CR\LF line endings is not helping compression at all imho, on the contrary.. it adds an extra byte for every line of text in a source file...extra byte that can affect your "all the way up" compression :)