Zygor Classic | Retail & Other Addons

Quote:

Originally Posted by 911sky Well if you think that, you have no idea what I did or what I will be doing. Just like the additions we have planned.

i hope you are true
i wish you the best of luck

Quote:

Originally Posted by PepsiMaxMango i hope you are true i wish you the best of luck

I have no reason to lie.
Myself & and a few friend spoke a lot about what we can add.
As it comes right at the time, my friend wanted something and this turned up.

Quote:

Originally Posted by 911sky Apparently? Nope as you have to import it. What I did was what I said I would do. Follow the rules. Release pulled I forgot to fix the bug in the TBC

Good to see them back.

Quote:

Originally Posted by PanPlays Good to see them back.

I saw the Meta... and Smiled :)

Quote:

Originally Posted by 911sky @[Only registered and activated users can see links. Click Here To Register...] Well if that is how you feel. Maybe I should not have wasted my time and post any more updates Guides will have to be fully rewritten every time there is an update to the official guides. Thats fine, we cannot import them anyway... So I use what I have..

Yeah that's what I meant with "what's the catch?" If it were all automated it would've been out earlier I assume. Manually doing this is crazy :D so thanks for the hard work! But Custom guides by others would be a better focus now I think.

Well yea what you said above is true.

Classic WOTLK Gold Guide V1.2 added to Gold guides

any idea why the mage aoe leveling guide is not showing up?

hi

here is how to fix the scuffed account sharing DRM

open GameLoader.lua file in a code editor or notepad
look at line 279

local base = select(2,_G[Serialize(addon.base)]())

change that to

local base = "bnetid#1337"

substitute bnetid#1337 for the bnet id tied to the string you are using, now save the file, open wow and import the corresponding string. confirmed works.

and you're done.

explanation:

local base = select(2,_G[Serialize(addon.base)]())

this is creating a variable called base which is actually calling the blizzard API (represented as _G) running the command GetBNetInfo and selecting the 2nd value from the returned array, which is the player's realid.

addon.base is instantiated and obfuscated in shared.lua line 151

addon.base = {66,78,71,101,116,73,110,102,111}

when the serialize function is run on this it converts those ascii character codes to letters and you get GetBNetInfo. this is so someone couldnt just search for where that command was being run in the code and do what i did but easier.

i've never coded in lua before nor looked in addon development so yeah this is pretty scuffed drm took about 2 hours to find.

if someone sends me their omega guide string and realid number i can post a compressed version of this for all to use.

hope this helps and hope that some paying users are able to now use the guide properly between their accounts and share the product they payed for with whomever they wish.

it's sad to see these guys went this route rather than just spending their money making a really awesome product that people will voluntarily pay for if they have the expendable income, but what's done is done.

I put my trust in @[Only registered and activated users can see links. Click Here To Register...] to fix this for all.

Quote:

Originally Posted by scuffedDRM hi here is how to fix the scuffed account sharing DRM open GameLoader.lua file in a code editor or notepad look at like 279 local base = select(2,_G[Serialize(addon.base)]()) change that to local base = "bnetid#1337" substitute bnetid#1337 for the bnet id tied to an activated account, now save the file, open wow and import the corresponding string. confirmed works. and you're done. explanation: local base = select(2,_G[Serialize(addon.base)]()) this is creating a variable called base which is actually calling the blizzard API (represented as _G) running the command GetBNetInfo and selecting the 2nd value from the returned array, which is the player's realid. addon.base is instantiated and obfuscated in shared.lua line 151 addon.base = {66,78,71,101,116,73,110,102,111} when the serialize function is run on this it converts those ascii character codes to letters and you get GetBNetInfo. this is so someone couldnt just search for where that command was being run in the code and do what i did but easier. i've never coded in lua before nor looked in addon development so yeah this is pretty scuffed drm took about 2 hours to find. if someone sends me their omega guide string and realid number i can post a compressed version of this for all to use. hope this helps and hope that some paying users are able to now use the guide properly between their accounts and share the product they payed for with whomever they wish. it's sad to see these guys went this route rather than just spending their money making a really awesome product that people will voluntarily pay for if they have the expendable income, but what's done is done.

Nice! im wondering now where the decoded guide from the import string is stored. Addons cannot directly write to disk other than the savedvariable folders. seems like it would have to store it in plain text somewhere

I still have the last rxp addon before they switched to imports and battlenet ID’s I just happened to not delete it and put it in a folder

Imagine locking the addon/guides trough BN ID and yet you end up with your product screwed/messed up badly.
Anyways, good luck with the upcoming changes @[Only registered and activated users can see links. Click Here To Register...]. Looking forward to see them.

Quote:

Originally Posted by scuffedDRM hi here is how to fix the scuffed account sharing DRM open GameLoader.lua file in a code editor or notepad look at line 279 local base = select(2,_G[Serialize(addon.base)]()) change that to local base = "bnetid#1337" substitute bnetid#1337 for the bnet id tied to an activated account, now save the file, open wow and import the corresponding string. confirmed works. and you're done. explanation: local base = select(2,_G[Serialize(addon.base)]()) this is creating a variable called base which is actually calling the blizzard API (represented as _G) running the command GetBNetInfo and selecting the 2nd value from the returned array, which is the player's realid. addon.base is instantiated and obfuscated in shared.lua line 151 addon.base = {66,78,71,101,116,73,110,102,111} when the serialize function is run on this it converts those ascii character codes to letters and you get GetBNetInfo. this is so someone couldnt just search for where that command was being run in the code and do what i did but easier. i've never coded in lua before nor looked in addon development so yeah this is pretty scuffed drm took about 2 hours to find. if someone sends me their omega guide string and realid number i can post a compressed version of this for all to use. hope this helps and hope that some paying users are able to now use the guide properly between their accounts and share the product they payed for with whomever they wish. it's sad to see these guys went this route rather than just spending their money making a really awesome product that people will voluntarily pay for if they have the expendable income, but what's done is done.

Would this not mean that an authentic Battlenet and import string would be visible and have to be sacrificed in the release? The developers could easily disable that account once they see it and the guides would stop working.

Not sure this is a great idea, I guess this is a good way if you want to share it with a friend or two privately but not for a public release on here unless both Battlenet and import information could be removed after the guides are imported.

Quote:

Originally Posted by supersimme would this not mean that an authentic bnet and import string would be visible and have to be sacrificed in the release? the developers could easily disable that account once they see it and the guides would stop working not sure this is a great idea i guess this is a good way if you want to share it with a friend or two privately but not for a public release on here unless both bnet and import information could be removed after the guides are imported

correct.

if the guide was actually usable i would make the effort to go further with the crack but there is time consuming steps ahead that would require me to think harder than i'd like to for a product that i'm not really interested in using.

Quote:

Originally Posted by supersimme would this not mean that an authentic bnet and import string would be visible and have to be sacrificed in the release? the developers could easily disable that account once they see it and the guides would stop working not sure this is a great idea i guess this is a good way if you want to share it with a friend or two privately but not for a public release on here unless both bnet and import information could be removed after the guides are imported

I mean if that really bothered you you could just take the Bnet ID of the creators of the guides to make this work :)) Their Bnet infos are displayed on their profiles too