CurseForge Packager and Classic Support
Some add-ons only require a minimum amount of changes in order to be compatible with the Classic version of WoW. This is often done within the code itself, however, there are some things that should be handled by the packager, so I offer the following suggestions:
- Build-specific tags:
@retail@ / #@end-retail@
@classic@ / #@end-classic@
This is most useful in the ToC file, to separate the interface/version numbers.
Classic-specific pkgmeta or pkgmeta entries. Some libraries, etc, aren't compatible with Classic, so classic builds need their own inclusions/exclusions, etc.
A project setting to automatically build a classic package based on the above pkgmeta information.
Building on this, I've been attempting to put together my starting set of addons for Classic but most of the ones being discussed in the community are not here or at least not well identified. Improvements to the Twitch Mods Addons interface should relieve some confusion and attract more community participation.
In the Twitch interface, it would be great if the user could designate the Retail and Classic versions of the game. The interface would then only show addons specific to that version. There should also be an ALL MODS option to allow people to attempt to use versions intended for the other game if they wish to attempt it.