WoWInterface

WoWInterface (https://www.wowinterface.com/forums/index.php)
-   Site help, bugs, suggestions/questions (https://www.wowinterface.com/forums/forumdisplay.php?f=18)
-   -   Different Addon versions for Retail and Classic (https://www.wowinterface.com/forums/showthread.php?t=57394)

LudiusMaximus 08-29-19 03:18 AM

Different Addon versions for Retail and Classic
 
I have an addon that has one version for retail and another for classic.
The code is really fundamentally different even though the functionality is the same.

Even if I managed to get the code for both retail and classic in the same files using
Code:

_G.WOW_PROJECT_ID == _G.WOW_PROJECT_CLASSIC
to decide which code to use, I would sill like to provide two alternative toc files.

Will WOWI at some point have the option to upload one retail and one classic version for the same addon?

SDPhantom 08-29-19 04:27 AM

Even if you put two TOC files in the same folder the game will only load the one that matches the name of the main folder.

LudiusMaximus 08-29-19 05:09 AM

Quote:

Originally Posted by SDPhantom (Post 333416)
Even if you put two TOC files in the same folder the game will only load the one that matches the name of the main folder.

Yes, I did not mean to put two different toc files into the same addon folder.
I meant that I am providing two downloads of my addon, each with a different toc file.

LudiusMaximus 08-29-19 05:14 AM

Or can I simply select the classic client in the compatibility section and WOWI will treat this as a download of its own; i.e. it will not be treated as "the most recent" version of the addon?

SDPhantom 08-29-19 07:55 AM

It marks the same file as compatible with both versions. Not exactly what you're looking for. From what I get, you're asking about attaching 2 files to the same project like Curse does. WoWI doesn't do that. You can add optional downloads, but the system still lists those as separate projects and puts a link to it in a different tab. This is mainly for plugins and patches.

You were asking if this support was to be added in the future, and I don't know what Dolby has planned. This is why I was avoiding answering this.

LudiusMaximus 08-29-19 08:11 AM

Quote:

Originally Posted by SDPhantom (Post 333421)
It marks the same file as compatible with both versions. Not exactly what you're looking for. From what I get, you're asking about attaching 2 files to the same project like Curse does. WoWI doesn't do that. You can add optional downloads, but the system still lists those as separate projects and puts a link to it in a different tab. This is mainly for plugins and patches.

Yeah, exactly. That's what my question was aiming at.
In the meantime I have seen that many addons, which exist for both versions, have two separate addon pages on WOWI. E.g.

https://www.wowinterface.com/downloa...-InFlight.html
and
https://www.wowinterface.com/downloa...-InFlight.html

or
https://www.wowinterface.com/downloa...yBossMods.html
and
https://www.wowinterface.com/downloa...s-Classic.html


Other addons in spite of being compatible with classic and retail only provide one single file. E.g.
https://www.wowinterface.com/downloa...artender4.html

So in this case of bartender you can only download the addon with the retail toc file at WOWI.
Whereas on Curse you can get it either with retail or with classic toc file.

It's probably not that big a deal, because literally nobody is prevented from using an addon only because it does not have the correct version in the toc file. :p

Dolby 08-29-19 08:16 AM

We are working on a way for authors to provide 2 files for download if they wish (being built to provide for the possibility of even more release types). We like the option and flexibility of allowing either 2 files on one page or having seperate pages for each like it is now.

If you use the API to upload you can actually upload a classic file to your current project. Just do a GET on the update endpoint https://api.wowinterface.com/addons/update and you'll see the new fields at the bottom for classic that you can use in your POST.

This is very early stages so there are some features missing and one big one is that the files won't show in Minion just yet however I'm working on that along with a way to upload a classic file via the webui too. Also there is no visual indication that the classic file you uploaded via the api is pending in the moderation queue.

LudiusMaximus 08-29-19 08:18 AM

Cool, thanks!

Xrystal 08-29-19 10:09 AM

This would really be great as I hate having multiple projects for the same addon rofl.

StormFX 08-30-19 07:09 PM

@Dolby: Multiple files on the same page would be great. It would allow for some further enhancements, eg, no-lib packages, etc. :p

Dolby 09-01-19 02:03 PM

Just a heads up I'll be re-working the classic upload via the API based on feedback. I recommend everyone wait for those changes if you are looking to both classic and retail releases listed on your info page.

StormFX 09-04-19 01:25 PM

Quote:

Originally Posted by Dolby (Post 333515)
Just a heads up I'll be re-working the classic upload via the API based on feedback. I recommend everyone wait for those changes if you are looking to both classic and retail releases listed on your info page.

How long, do you think? I was using the API to post retail/classic versions so I didn't have to create separate pages. I don't want to screw anything up. :p

Dolby 09-04-19 01:27 PM

If you have a page that has both retail and classic files then its fine to use. I'll keep the old stuff as legacy for a bit.

Some were trying to use it to only have a classic file on their addon page and this wont work like that just yet. So that prompted me to work on a totally different way based on wow api version.

StormFX 09-04-19 02:03 PM

Awesome. I just wanted to verify whether I needed to wait for further updates.

Xrystal 09-04-19 03:22 PM

Quote:

Originally Posted by Dolby (Post 333581)
If you have a page that has both retail and classic files then its fine to use. I'll keep the old stuff as legacy for a bit.

Some were trying to use it to only have a classic file on their addon page and this wont work like that just yet. So that prompted me to work on a totally different way based on wow api version.

I have a feeling I was one of those annoying ones... sorry to cause you problems if I was.

Dolby 09-30-19 11:50 AM

I have updated the site api to now use the compatible data point to route releases for classic or retail. If you upload an update with compatible=1.13.2 the file and version will be updated for your classic release. If you leave compatible blank or provide any 8.x game version it will be applied to your retail release.

This path does still require that you have a retail release, I'm working on ironing this out for those that only have a classic release of their AddOn.

The following is now deprecated but I really have no plans on removing it so if you are already using this method its ok.
Code:

"updatefile_classic": {
"Type": "FILE",
"Required": "No",
"Description": "*Deprecated* AddOn Zip or Rar file for wow classic."
},
"version_classic": {
"Type": "STR",
"Required": "No",
"Description": "*Deprecated* Version number of your Classic AddOn. *Must change this number if new file is included."
}


MooreaTv 09-30-19 12:16 PM

is there an example addon that has the 2 zip available, what does the UI look like (for users to pick the right one)?

I haven't been able to find one randomly clicking in the newly updated addon list

Dolby 09-30-19 12:19 PM

I think StormFX is the only one using it under the deprecated format at the moment.

https://www.wowinterface.com/downloa...97-Masque.html

MooreaTv 09-30-19 01:02 PM

nice, so if what I have for instance is:
https://github.com/mooreatv/AuctionD...g.yaml#L23-L33
(where I only upload so far the -classic zip to wowi)

if I just put back -w for the non classic section, it'll show up like Masque's ?

MooreaTv 09-30-19 01:51 PM

neat! it worked
https://www.wowinterface.com/downloa...fectAlign.html

not sure if that's the legacy way or not... but it works so I am happy
if others want to use the same:
https://github.com/mooreatv/PixelPer...packaging.yaml


All times are GMT -6. The time now is 10:50 PM.

vBulletin © 2020, Jelsoft Enterprises Ltd
© 2004 - 2020 MMOUI