We're porting Retail add-ons to Beta, Come Get 'Em

WoW Classic WoW Classic General Discussion
429

KTM was a big QoL, I can’t even imagine having to raid without it.

430

would like to know about this also.
If you get it working let me know when and how you got it done.
I would try to figure it out but I’m not cool enough to get into beta.

431

Under the WoW folder there should be a folder for each version of the game
_ptr_ for PTR
_retail_ for retail
_Classic_Beta_ or something like that for these addons.

Under these folders will be Interface\AddOns folders for that version.

432

There were some additional instances of correctSpec(entry) and some additional code that was deleted which you missed. But then, deletions are hard to find unless you do a file comparison.

Also, it should be --[[ and ]]-- not [[-- or --]] from what the game was throwing back at me. :slight_smile:

433

A copy of this in the OP could be also very useful (the instructions, not the other bits) .

It seems everyone including the official host sites were caught off guard by addons being in place with the initial beta.

434

Gotcha. Thanks for the info! I don’t know how it all works. Does that mean that the existing 1.12 addons, all the way from vanilla, won’t work with classic because of the client?

435

Addons from vanilla or private servers will not work in Classic.

Classic is using a modified version the current (8.x) API.

436

Ah, I just googled a program to do diffs (meld) and first compared my clique retail directory to the beta clique folder to see which files were changed then opened a comparison of each file and just went to the blue parts that showed differences.

I’m not sure why the commenting would be wrong since I just copy and pasted from the files I had and I don’t get errors. I do see some green area marked in the program I think I missed before in clique.lua also:

local function correctSpec(entry)
    --[[
    -- Check to ensure we're on the right spec for this binding
    local currentSpec = GetSpecialization()
    if currentSpec and entry.sets["spec" .. tostring(currentSpec)] then
        return true
    end

    -- Need to check the other spec sets to ensure this shouldn't be
    -- deactivated
    for i = 1, GetNumSpecializations() do
        if entry.sets["spec" .. tostring(i)] then
            return false
        end
    end
    --]]

edit: and the version from retail I was comparing it to was v80000-1.0.0

437

Lightheaded: https://drive.google.com/open?id=1sgRWX94zAn6D8czIwv8yud8rCG5NJT8Q (A hackjob… some of the automatic map features don’t work [eg, sending coordinates to different zones] and it’s using the “live” data [so xp/rep is probably wrong but all the comments are there]… if the quest id exists in live data. there’s missing ones, but the real author or someone with the ability to dump classic wowhead data is required)

Clique: https://drive.google.com/open?id=1J_hKkRlIxZGdD31UXALhZX9Ni1UhrAb3 my edit, hopefully someone does a real job.

Blizzard Interface code dump from beta client: https://drive.google.com/open?id=1WMyAT9MV08NfKDf3k6aOo8Vz1h_iBqmZ

1 Like
438

Would it be possible to get GW2 UI and Immersion for classic? I love those addons.

1 Like
439

Maybe the ultimate display of why authors might get annoyed at having their addons ripped apart and re-published by the clueless.

Not even Leeroy could come up with a spectacular fail like this. Thank you.

In short, the addon has no value for Classic whatsoever.

440

i found lightheadeds value more from the in game viewing of the wowhead comments a lot of times.

I m sure lots of people would love the Peggle addon, though that probably has legal stuff with it.

441

Pretty much all the quests have changed since vanilla but this is using the current non-Classic versions and comments.

That and the LightHeaded author obtained permission from WowHead to DL and incorporate the information. I’m not sure Rp did the same.

442

Then all they have to do is fix it themselves, properly… or designate someone else to do so.

The comments don’t change between versions, they’re just appended. The whole reason I, personally, use Lightheaded (the comments) is mostly functional on the beta, which is why I, personally, hacked it to work.

I’m eagerly waiting until these addons are officially fixed to work with Classic… until then I’ll modify the ones I want so that they work in the meantime.

As an aside, Fizzlemizz, I really find your armchair lawyering silly and annoying (maybe I’m from India), and contributing nothing of worthwhile value to this thread.

443

That actually depends, Most addons wont, some basic ones might. Porting questie from 1.12 to 1.13 hasn’t been too difficult so far, it’s not as far off as it might seem despite being based on 8.x

444

And I find your butchering of other peoples hard work offensive. Neither of us are in raptures no matter where we’re from.

445

Slight over simplification on my part but in general, still holds. My bad.

1 Like
446

I’m not sure what you mean here, maybe “righteous”?

Either way, that’s a philosophical question (one that I would disagree with you on).

I guess I should thank you though, without your comments I would have never been motivated to share my hackjobs.

447

I have to agree with him. He isn’t butchering anything, and he isn’t taking anything away from the addon authors.

He’s showing that he appreciated their work so much he’s trying to find a bandaid fix so he can continue to use them until they have an official version rolled out.

So far in this thread you done nothing except demean others and offered nothing in return except criticism. I understand that you are an addon author and that you are interpreting things the way you would if someone had modified your addons. However that does not give you the right to speak on behalf of all addon authors.

1 Like
448

https://en.wikipedia.org/wiki/All_rights_reserved

With that I bid you a fond fairwell. Have fun all.