1. When uploading a manually created ZIP file, you have to wait for a human moderator to review the file before it's available for download. The CurseForge moderators are pretty slow, so don't be surprised if it takes a day or two.
2. Make sure your ZIP file structure does not contain any "forbidden" things like extra folders (eg. MyAddon-v1.2.zip > MyAddon-v1.2 > MyAddon > MyAddon.toc), no folders (eg. MyAddon-v1.2xip > MyAddon.toc), OS-specific files (eg. Desktop.ini or .DS_Store), wowmatrix files, etc. There is a list of these things on one of the FAQs/KB pages on Curse/CurseForge/WowAce, but I don't know exactly where. Anyway, if your ZIP file contains any of these issues, it will be rejected.
(On a side note, make sure your email address is up to date on CurseForge, so you'll get the email messages notifying you when your file is approved or rejected. If it's rejected, the email message will tell you why.)
3. I'm assuming the addon you're trying to upload is the one linked from your profile, but you should really mention that kind of thing in your post.
4. If it's been more than 48 hours, and you have not received any email messages about the file, use the Report icon on your project (tiny red triangle in the bottom right corner of the browser window) to contact the CurseForge moderators more directly. Select "Requires moderator attention" as the report category, and ask what's going on with your file. Again, CurseForge seems pretty understaffed, so don't be surprised if it takes a day or two to get a response.
Your addon's textures should be contained in its own folder. If you need to override game default textures, it's best to do so using methods like :SetTexture in-game. I'd suggest your ZIP contains the following structure:
MyAddOn
--- Textures
------- texture files here
--- MyAddOn.toc
--- other addon files here
If your addon ZIP contains anything that needs to go somewhere other than the Interface\AddOns folder, then it cannot be installed or updated by programs like the Curse Client, and users will have to deal with it by hand. Obviously, this should be avoided if possible. The only time it really makes sense to distribute non-AddOn files is if your package is only a texture replacement (for example, replacing all the icon textures) and not an addon at all.
I commited some changes to my addon in my repo and normally the packager started building a package. It does not. Even worse Package status says just "no data available" normally i saw the recent build history there. What is happening?
I commited some changes to my addon in my repo and normally the packager started building a package. It does not. Even worse Package status says just "no data available" normally i saw the recent build history there. What is happening?
Even worse, you didn't supply the URL to your project so it could be looked into. >.>
hi, could you check whats wrong with the packager for Ark-Inventory
i keep getting rejected for third party exe/bat files but there are none on my side so i have no idea why its rejecting
edit:
i changed to a single externals entry for ace3, just trunk and it looks like theres a bat file in trunk\tests (i dont have externals in my workflow so i didnt notice it before), also the ace3 zips dont include it
is there a way to get all of ace3 without the tests folder or do i have to go back to one line per module?
edit2:
figured out how to exclude it in the pkgmeta file, wasnt sure if it would exclude an external it added in itself but it does, so now i just have to work out how to get rid of it in svn
Is there a known problem with automatic packaging? It used to work great, until a few days ago, it stopped doing anything for me. Check out https://wow.curseforge.com/projects/pusikas-spellflash-dk. Last 3 tags did not get packaged automatically. I did upload a zip now, and that worked.
I ran into a couple snags on the way but I manage to figure most of them out for myself before reading on further in the thread you linked which confirmed what I did was right.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
2. Make sure your ZIP file structure does not contain any "forbidden" things like extra folders (eg. MyAddon-v1.2.zip > MyAddon-v1.2 > MyAddon > MyAddon.toc), no folders (eg. MyAddon-v1.2xip > MyAddon.toc), OS-specific files (eg. Desktop.ini or .DS_Store), wowmatrix files, etc. There is a list of these things on one of the FAQs/KB pages on Curse/CurseForge/WowAce, but I don't know exactly where. Anyway, if your ZIP file contains any of these issues, it will be rejected.
(On a side note, make sure your email address is up to date on CurseForge, so you'll get the email messages notifying you when your file is approved or rejected. If it's rejected, the email message will tell you why.)
3. I'm assuming the addon you're trying to upload is the one linked from your profile, but you should really mention that kind of thing in your post.
4. If it's been more than 48 hours, and you have not received any email messages about the file, use the Report icon on your project (tiny red triangle in the bottom right corner of the browser window) to contact the CurseForge moderators more directly. Select "Requires moderator attention" as the report category, and ask what's going on with your file. Again, CurseForge seems pretty understaffed, so don't be surprised if it takes a day or two to get a response.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttp://www.curseforge.com/wiki/knowledge-base/projects/file-statuses/
My AddOn uses textures, that located in /Interface root folder.
So the structure of my AddOn is:
/World of Warcraft
---- /Interface
-------- /AddOns
------------ /My AddOn
------------------ AddOn Files (.lua,.toc,.xml)
-------- /Miscellaneous
-------------- Images (.blp)
Could you please point me, what .zip structure i should you in my case.
MyAddOn
--- Textures
------- texture files here
--- MyAddOn.toc
--- other addon files here
If your addon ZIP contains anything that needs to go somewhere other than the Interface\AddOns folder, then it cannot be installed or updated by programs like the Curse Client, and users will have to deal with it by hand. Obviously, this should be avoided if possible. The only time it really makes sense to distribute non-AddOn files is if your package is only a texture replacement (for example, replacing all the icon textures) and not an addon at all.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI commited some changes to my addon in my repo and normally the packager started building a package. It does not. Even worse Package status says just "no data available" normally i saw the recent build history there. What is happening?
-
View User Profile
-
View Posts
-
Send Message
AdminEven worse, you didn't supply the URL to your project so it could be looked into. >.>
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhi, could you check whats wrong with the packager for Ark-Inventory
i keep getting rejected for third party exe/bat files but there are none on my side so i have no idea why its rejecting
edit:
i changed to a single externals entry for ace3, just trunk and it looks like theres a bat file in trunk\tests (i dont have externals in my workflow so i didnt notice it before), also the ace3 zips dont include it
is there a way to get all of ace3 without the tests folder or do i have to go back to one line per module?
edit2:
figured out how to exclude it in the pkgmeta file, wasnt sure if it would exclude an external it added in itself but it does, so now i just have to work out how to get rid of it in svn
Is there a known problem with automatic packaging? It used to work great, until a few days ago, it stopped doing anything for me. Check out https://wow.curseforge.com/projects/pusikas-spellflash-dk. Last 3 tags did not get packaged automatically. I did upload a zip now, and that worked.
I ran into a couple snags on the way but I manage to figure most of them out for myself before reading on further in the thread you linked which confirmed what I did was right.