CurseForge and Overwolf are joining forces!
Awesome More Information
  • 0

    posted a message on Automatic Packaging Marks Addon for Classic

     I've noticed this has stopped happening on subsequent builds after I manually changed an earlier build to 8.2.5 (and disabled Classic).

    Posted in: Updaters
  • 0

    posted a message on Automatic Packaging Marks Addon for Classic

    Hi there - my addon, https://www.curseforge.com/wow/addons/raiderio - has been getting set as a Classic addon during the automatic packaging step despite this addon not being intended for Classic.

     

    I can manually adjust builds after the fact to state that it should be for Retail not Classic, but would like a way to specify this within the pkgmeta (or in the project configuration somewhere).

     

    Can anyone advise where we need to make changes to fix this?

    Posted in: Updaters
  • 0.955281418658443

    posted a message on Updates not pushing to Curse

    We're seeing a similar issue with the Raider.IO addon.  Since it sounds like some here are saying it is fixed for them, I wanted to reach out to bring it up that our situation does not appear fixed.

     

    Currently our addon https://wow.curseforge.com/projects/raiderio shows as having the latest release from 2 days ago.  However we've been pushing a tagged commit once to twice per day to github, and have had a webhook setup to send this to CurseForge for packaging. In the CurseForge Dashboard I can see that the hooks have been received from github, but the recent calls don't attempt to package a build.

     

    All these commits have been tagged.

     

    Thanks for any assistance you can provide.

     

    Posted in: General Chat
  • To post a comment, please or register a new account.