• 0

    posted a message on Current Addon Developers and Classic WoW Development

    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.

    Posted in: General AddOns
  • 0.942189421894219

    posted a message on So what is the possible time frame for a WoW Classic Addon section?

    I just got a stress test invite.

     

    Client Version is 1.13.2 so that is simple versioning. And so it might be fine. If the version goes up and you can select it then it might not be all bad. Just have to update the addons for the new API and it'll be good.

    Posted in: General Discussion
  • 0

    posted a message on Current Addon Developers and Classic WoW Development

    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.

    Posted in: General AddOns
  • 0.941699604743083

    posted a message on So what is the possible time frame for a WoW Classic Addon section?

    My concern is when you have to update the older addons to the current API version, and how it may be handled.

    I am sure that most of the basic level addons are going to work fine, but there are a LOT of changes that happened with party/group/raid information and such that just have to be re-written. I know there's a client version tag, but I would think there would be an API version instead. So lets do a case study here. I don't have the Beta client so I don't know what the interface version would be however:

     

     

    Bagnon

     

    Game Version 1.12.0

    API Version: 8.1.5

     

    That way you could distinguish a game version and the API Version separately. Could have a tag that references these maybe:

     

    WoW Classic

    API Version 8.1.5

    Game Version 1.12.0

     

    Not sure the best way to handle it. It would almost make more sense for the addon developers to add under a completely new umbrella for the sake of filtering the new API Updated versions of the Addons from the older retail versions.

     

    Edit: On top of this, what happens when they patch bugs in the classic client. That version will be 1.12.1 / 1.12.2 etc. So it may add confusion into the mix perhaps.

    Posted in: General Discussion
  • 0.94164193867458

    posted a message on So what is the possible time frame for a WoW Classic Addon section?

    I am seriously interested in getting into WoW Classic and Addons with the newer API they have, and potentially revitalizing old addons and/or making new ones for the new player base that is bound to show up in the coming months.

     

    Will there be a World of Warcraft: Classic section? Or will there be some kind of odd filter for the existing World of Warcraft addon's page? Like maybe a 'version' ... kind of makes more sense to have it's own fork rather than appending it to the existing one, however, then there's the point that most of the old addons are still IN the existing WoW section heh.

    Posted in: General Discussion
  • To post a comment, please or register a new account.