Question about automatic packaging
So this is probably more related to Curseforge but I don't think forums there are as active and I know lots of devs use this process anyway.
So I am using travis-ci and BigWigsMod packager to automatically package my add-on to Curseforge and WoW Interface. On Curseforge, it sets my main file as my classic file, but I'd like for it to be my retail version as I develop primarily in retail and classic is more of a side though.
Does anyone know if there's any way to control this? Like a setting somewhere? Or is it just the most recent file uploaded? And in that case should I just make it package the classic version first in my .travis.yml?
Also, I have my . pkmeta set to use a manual changelog and the retail version uses it, but the classic version doesn't. What am I doing wrong there? Again, classic is packaged second.
Thanks for your time!
|