I am curious as to how many addon developer will be attempting to port their addons, if they could function anyway, to the Classic WoW version coming out.
Apparently it is currently running the retail API methods, so that means the Protected Functions are extreme compared to what was available in the 1.12.x API.
Things like TargetUnit() is not usable, so a lot of the addons will flat out not work if you try to load the 'version appropriate' one. It will have to be updated.
So I am wondering if there are developers that are looking into doing dual development forks for Classic and Retail if their addon is relevant for that version. I know there will be a large majority of the addons that just won't work, as the client itself doesn't support things however ... just curious.
So I just got my stress test. And the current client version is 1.13.2
So they are just continuing onward with the 1.xx.x number format for the classic client.
This will make it easier for Curse to manage the addons regardless of the API version.
Your version of the old clients will still be 1.12.x so, when the developers update their addons to the 1.13.x client and upwards in values, then it should be fairly simple to deal with.
does anyone know how to permanently flag an addon as both retail and classic capable?
i can edit the packaged file afterwards and add the classic supported version to (the toc is at 80200) it but i'd rather not have to do that for every upload
Does anyone know of a resource online that outlines most of the differences between retail and classic addon API? I'd love to have access to a list of changes and/or the "typical" things that need to be modified, etc.
Thanks!
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI am curious as to how many addon developer will be attempting to port their addons, if they could function anyway, to the Classic WoW version coming out.
Apparently it is currently running the retail API methods, so that means the Protected Functions are extreme compared to what was available in the 1.12.x API.
Things like TargetUnit() is not usable, so a lot of the addons will flat out not work if you try to load the 'version appropriate' one. It will have to be updated.
So I am wondering if there are developers that are looking into doing dual development forks for Classic and Retail if their addon is relevant for that version. I know there will be a large majority of the addons that just won't work, as the client itself doesn't support things however ... just curious.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSo I just got my stress test. And the current client version is 1.13.2
So they are just continuing onward with the 1.xx.x number format for the classic client.
This will make it easier for Curse to manage the addons regardless of the API version.
Your version of the old clients will still be 1.12.x so, when the developers update their addons to the 1.13.x client and upwards in values, then it should be fairly simple to deal with.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumdoes anyone know how to permanently flag an addon as both retail and classic capable?
i can edit the packaged file afterwards and add the classic supported version to (the toc is at 80200) it but i'd rather not have to do that for every upload
Does anyone know of a resource online that outlines most of the differences between retail and classic addon API? I'd love to have access to a list of changes and/or the "typical" things that need to be modified, etc.
Thanks!