WoWInterface - For multi-client zip files can we have the page describe versions supported?

WoWInterface (https://www.wowinterface.com/forums/index.php)

- Site help, bugs, suggestions/questions (https://www.wowinterface.com/forums/forumdisplay.php?f=18)

- - For multi-client zip files can we have the page describe versions supported? (https://www.wowinterface.com/forums/showthread.php?t=58747)

For multi-client zip files can we have the page describe versions supported?

An awesome change with TBC and Classic Era is the ability to include multiple toc files in one zip and have it up to date with those versions.

I've taken advantage of that for some addons, checked the 9.0.5, 2.5.1 and 1.13.7 compatibility, but the pages only display 9.0.5 in the topright.

https://www.wowinterface.com/downloa...7-TinyPad.html
https://www.wowinterface.com/downloa...07-Select.html
https://www.wowinterface.com/downloa...-Grounded.html
https://www.wowinterface.com/downloa...ddonUsage.html
https://www.wowinterface.com/downloa...Portraits.html

The versions it's compatible with is buried behind the File Info tab on the right sidebar.

Can we have it more prominently displayed which versions of the game our addons support?

Yep this is really great news.

I'll work on something to make the compatibility more visible.

Quote:

Originally Posted by Gello (Post 339175)

I've taken advantage of that for some addons

Not sure if you're aware, but just in case: The Curse API/Client doesn't truly support multi-version files. Apparently it (setting multiple game versions) "confuses" the client and it will only display one of them. They're supposedly working on a fix, but that's all I can find on the subject. Most people say it won't be Soon™. Hence why most of my add-ons are still multiple packages. :/

Thanks Dolby!

Quote:

The Curse API/Client doesn't truly support multi-version files.

Yeah my experience with curse has been unpleasant over the years. I've stopped posting beta versions on curse long ago and some addons I just post on wowinterface and don't even bother with curse.

This feature sounds interesting. Is there documentation somewhere I could read?

The Skillet and Skillet-Classic project repositories are on GitHub and CurseForge (for the localization) and are currently uploaded to WoWI, CF, and TukUI using the BigWigsPackager and GitHub actions.

Skillet (retail) is enough different from Skillet-Classic that I'm OK with keeping it separate but so far, the Skillet-Classic source is identical between BCC and Classic(_era) so I believe these two packages could benefit.

I learned about it here: https://github.com/Stanzilla/WoWUIBugs/issues/68
(scroll down to last post)

Quote:

In a future set of builds the client will support loading distinct TOC files on a per-client basis. The implementation we've been informed about is as follows:

If an addon is loaded on the BCC client, the client will first look for a TOC file whose name is suffixed by "-BCC" (eg. "MyAddOn-BCC.toc") and load that if present. If not, the client will fall back and load "MyAddOn.toc".
If an addon is loaded on the Classic client, the client will first look for a TOC file whose name is suffixed by "-Classic" (eg. "MyAddOn-Classic.toc") and load that if present. If not, the client will fall back and load "MyAddOn.toc".
If an addon is loaded on the Retail client, the client will first look for a TOC file whose name is suffixed by "-Mainline" (eg. "MyAddOn-Mainline.toc") and load that if present. If not, the client will fall back and load "MyAddOn.toc".
If an addon fails to find a client-specific TOC and no fallback "MyAddOn.toc" is present, the addon will not be loaded.

The envisioned advantages of this approach are that it will enable us to control the files that are loaded on a per-client basis without requiring separate packages - which the initial request didn't account for - and the same also applies to other TOC attributes such as dependencies.

It's a nice system. It seems to be live now on the 2.5.1 TBC Classic and 1.13.7 Classic Era clients too.

One of my addons is Classic Era and TBC Classic only. For that one I just created a file-BCC.toc and let the original Classic toc be 11307. And it's current on both versions.

A few more (the ones listed in first post here) are now up to date on all three clients by having a file-BCC.toc and file-Classic.toc.

Thats great news ... so great it should be a wowinterface news-entry ;)

Related to this ... when flagged classic or bcc compatible shouldn't an addon automaticly get the related "Optional Categories"-Entry set?

Quote:

Originally Posted by Rilgamon (Post 339316)

Related to this ... when flagged classic or bcc compatible shouldn't an addon automaticly get the related "Optional Categories"-Entry set?

Either that or the category listing for those flavors should also list add-ons that support those versions. Good idea, though. Saves having to manually edit the categories.