Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
Here on CurseForge, go to your project, and click the Follow button - you'll see a modal that allows you to follow comments on the project. As for Curse itself, go to http://www.curse.com/my-profile/activity and click the envelope symbol next to a project - any that is orange will send you e-mail alerts.
If Beta is your default, that should work just fine. As for not using the pkgmeta.yaml, yours is malformed. Check the documentation here: http://wildstar.curseforge.com/docs/packaging
The reason the automatic packaging isn't working is that the packager only works from the main branch: You're doing your work on a branch named Beta.
Yes, the Client will work with multiple Addons in a single zip, as will the packager. Zipping them all individually and placing those into a containing zip, however, will not work.
It seems that changes to a previously uploaded file on wildstar.curseforge.com don't get transfered to curse.com. I've uploaded a file as beta and changed it a day later to release, but curse.com doesn't recognize it as newest released file (after two days). Is this on purpose?
1) It uses the project's URL slug if no package-as is specified. There's no reason to parse the source URL attempting to figure out which portion is the repository name when all that's required is a simple field in the pkgmeta file.
2) It isn't directly visible from GitHub, but anyone who decides to clone your repository will have that information either via their commit GUI or by typing "git log" from a commandline.
2: The changelog is all commits between tags. The e-mail address and all of the other information included there is the same information that is readily available via GitHub; in fact, that's where the information is pulled from.
0
Here on CurseForge, go to your project, and click the Follow button - you'll see a modal that allows you to follow comments on the project. As for Curse itself, go to http://www.curse.com/my-profile/activity and click the envelope symbol next to a project - any that is orange will send you e-mail alerts.
0
No, you have access to your GitHub or BitBucket repository as soon as you set the source URL on your project and select your packaging options.
0
Moderators don't even see a project in the queue until it's had a file uploaded, so you should probably do that ASAP. :D
0
Yeah, betas synchronize to Curse so there's really no way to do this at the moment.
0
If Beta is your default, that should work just fine. As for not using the pkgmeta.yaml, yours is malformed. Check the documentation here: http://wildstar.curseforge.com/docs/packaging
0
The reason the automatic packaging isn't working is that the packager only works from the main branch: You're doing your work on a branch named Beta.
Yes, the Client will work with multiple Addons in a single zip, as will the packager. Zipping them all individually and placing those into a containing zip, however, will not work.
0
We've been working on figuring out the cause of this issue since Wednesday morning, and have a few leads so hopefully this will be resolved very soon.
0
I can't find a CandyUI anywhere on the site. :/
0
What project is this? I don't see a Source tab on any of the projects you have listed.
0
You're good to go now.
0
No, it's a bug. I'll poke someone about it.
0
Ouch - those links don't show through at all. :/
I've brought the projects to the attention of someone who can fix the version issues. Thanks!
0
Which project(s)? I'll need to know so I can poke someone to try to get them synchronized properly with Curse.com
0
1) It uses the project's URL slug if no package-as is specified. There's no reason to parse the source URL attempting to figure out which portion is the repository name when all that's required is a simple field in the pkgmeta file.
2) It isn't directly visible from GitHub, but anyone who decides to clone your repository will have that information either via their commit GUI or by typing "git log" from a commandline.
0
1: Read http://wildstar.curseforge.com/docs/packaging - look for "package-as"
2: The changelog is all commits between tags. The e-mail address and all of the other information included there is the same information that is readily available via GitHub; in fact, that's where the information is pulled from.