Thanks Torhal for getting the file unwedged.
I can confirm that the project does appear in CC4 even with a Beta tag. Oh well - no harm, no foul.
It would be nice to get that Experimental documentation updated since it seems a bit confusing on what happens, what you can do and what others will be able to see (on CurseForge) - at least confusing to me anyway LOL.
- Registered User
Member for 13 years, 6 months, and 21 days
Last active Mon, Aug, 15 2016 11:28:15
- 0 Followers
- 5 Total Posts
- 0 Thanks
Apr 13, 2010Thanks for making it Normal, but I am concerned that the project (and file) will be now syndicated to Curse, which is not what I really wanted at this point.Posted in: Need Help?
I made the project Experimental so that it would not be syndicated - I wanted the project to be initially a 'closed' beta (you stumbled upon it in CurseForge - viz, you are probably a developer, or via me letting people know via a link to CurseForge). Once I get a Release version of this addon out there then it would go through a more 'open' beta cycle on Curse itself.
Ya the Experimental documentation needs to be updated since it led me to expect a 'closed' beta style availability.
Also, the 'Waiting on Project' status needs to be in the project statuses documentation - the only mention of that was on this forum over a year ago.
Apr 13, 2010To Phanx:Posted in: Need Help?
Thanks for the 24 hour approval time frame information. The 'Waiting on Project' status threw me since the project was approved (even receiving an e-mail saying as such).
I have not seen that status when uploading a file, and the only other mention of that status was on this forum, where it had to be unwedged by the admins.
Thanks also for the mention about the CurseForge repository. I however use my own version control, so am not looking to switch that. Be that as it may, if Curse is really nudging developers to make using CurseForge's repository mandatory, I really wish they would just say so.
I think I am misunderstanding something here. AFAIK via reading the project documentation (which seemed to be confirmed by Phanx's post above), an Experimental project simply would not syndicate to Curse until I had either a) manually requested that it do so, or b) that I had released it via tagging a file as Release, in which case it would auto-magically get syndicated after approval.
Otherwise, files would be available for download from CurseForge (vs Curse), with the disclaimer that the project is 'Experimental' and thus caution is warranted.
There was no mention of 'Normal' projects Vs 'Experimental' projects and file uploading in the documentation I saw (reference below), nor as I was creating the project and uploads. I was under the same impression as Phanx. The various documentation and project creation process texts should be corrected if this is not the case.
Apr 12, 2010G'day Torhal,Posted in: Need Help?
Hmm, maybe I wasn't clear.
The 'Waiting on Project' is for the file upload - not the project. Indeed, the project was approved yesterday.
However, the file that I uploaded is in the mysterious 'Waiting on Project' status.
Here is the file's link name a la CurseForge:
Here is the ZIP's URL:
If I can provide more information (screenshots?) let me know.
Apr 12, 2010Hi there,Posted in: Need Help?
I created a new project called LootList yesterday. Today, I uploaded a ZIP file with the initial Beta version.
It's status has been "Waiting on Project" for about 4 hours now. What is it that I need to do to get the file approved?
CurseForge link is http://wow.curseforge.com/addons/lootlist/files/
- To post a comment, please login or register a new account.