Zygor Classic | Retail & Other Addons | Updated

Quote:

Originally Posted by Undómiel99 The addon should still work, it just doesn't have any updated stuff for the recent expansions/patches. But if I open a guide like from Legion it should still work

It will throw a heck lot of errors up, seeing it is not compatible.

Quote:

Originally Posted by Undómiel99 The addon should still work, it just doesn't have any updated stuff for the recent expansions/patches. But if I open a guide like from Legion it should still work

So you want any Dugi adonn
Then that changed to no era, or classic to Retail only
But has to be from 2023-2025 to work on 12 patch.
That would throw up a heck lot of errors and would not even work.
Just to do old achievements ect

Quote:

Originally Posted by Descentralizado It will throw a heck lot of errors up, seeing it is not compatible. So you want any Dugi adonn Then that changed to no era, or classic to Retail only But has to be from 2023-2025 to work on 12 patch. That would throw up a heck lot of errors and would not even work. Just to do old achievements ect

Yeah and loremaster, dailies, etc.

Why would it throw error?

Quote:

Originally Posted by Undómiel99 Yeah and loremaster, dailies, etc. Why would it throw error?

Well you are expecting to use a old addon on a new patch, with a new API and updated code.

These are the changes.

Midnight (12.0.x) introduced major addon API/security changes, not just a normal patch update. Blizzard explicitly says addons that haven't been updated for Midnight will not be allowed to load.

Lua errors such as "attempt to call a nil value".
This usually means the addon is trying to use a WoW function/API that was removed or changed.

"Secret value" errors.
This is one of the biggest changes in 12.x. Combat-related information can now be returned as secret values. An addon can sometimes display the information but isn't allowed to inspect/calculate with it in the old way.
Combat addons can lose major functionality.
Addons that calculate things like enemy abilities, combat-log information, cooldowns, interrupts, or encounter mechanics are particularly vulnerable. For example, COMBAT_LOG_EVENT and COMBAT_LOG_EVENT_UNFILTERED were changed so that registering them can produce an error in 12.0.0.

Taint/secure-action errors.
An addon might appear to work until you enter combat, then produce errors because it is attempting something the new secure UI system doesn't permit.

UI elements may partially work.
A purely cosmetic addon that changes fonts, positions, textures, frames, etc. has a much better chance of being updated successfully. Blizzard specifically intends to preserve a lot of this sort of UI customization.

So you really think a 1-3 year old addon would work up and updated patch with no errors?

Quote:

Originally Posted by Descentralizado Well you are expecting to use a old addon on a new patch, with a new API and updated code. These are the changes. Midnight (12.0.x) introduced major addon API/security changes, not just a normal patch update. Blizzard explicitly says addons that haven't been updated for Midnight will not be allowed to load. Lua errors such as "attempt to call a nil value". This usually means the addon is trying to use a WoW function/API that was removed or changed. "Secret value" errors. This is one of the biggest changes in 12.x. Combat-related information can now be returned as secret values. An addon can sometimes display the information but isn't allowed to inspect/calculate with it in the old way. Combat addons can lose major functionality. Addons that calculate things like enemy abilities, combat-log information, cooldowns, interrupts, or encounter mechanics are particularly vulnerable. For example, COMBAT_LOG_EVENT and COMBAT_LOG_EVENT_UNFILTERED were changed so that registering them can produce an error in 12.0.0. Taint/secure-action errors. An addon might appear to work until you enter combat, then produce errors because it is attempting something the new secure UI system doesn't permit. UI elements may partially work. A purely cosmetic addon that changes fonts, positions, textures, frames, etc. has a much better chance of being updated successfully. Blizzard specifically intends to preserve a lot of this sort of UI customization. So you really think a 1-3 year old addon would work up and updated patch with no errors?

I dont know, it's worth a shot I guess if there's no Dugi Guides from patch 12.1

Quote:

Originally Posted by Undómiel99 I dont know, it's worth a shot I guess if there's no Dugi Guides from patch 12.1

Hundreds of changes, the addon would not even load.
But you want to me to search and do multiple searches because it is worth a shot?

When you do not want to use a trial addon or the essentials and then convert the guides from another addon to what you need.

I had a beta addon that loaded like Joana addon. Used Zygor and RXP guides and when I asked for testers, no one wanted to test it. It was like No! RXP only.

So my addon got abandoned, so I do not waste my time on it now

Sorry to be a bother but I noticed there does not seem to be a link for the ZG wow retail version or any other versions. It appears to be a link but its not seemingly going anywhere there is nothing to click.

Quote:

Originally Posted by lowchin Sorry to be a bother but I noticed there does not seem to be a link for the ZG wow retail version or any other versions. It appears to be a link but its not seemingly going anywhere there is nothing to click.

You say the link, but do not say what link it is. So I ask, how am I supposed to know if you do not say?

The links are clear, and people click something they know they do not want. For some reason and wonders why it is not what they wanted.

ty 4 this

Hello, Im missing something? I don't see the link to download Zygo guides for retail

Quote:

Originally Posted by crossk Hello, Im missing something? I don't see the link to download Zygo guides for retail

If people read the post it is there.
It does say downloads.
You want it from a file host, it does say that

ZygorGuidesViewerClassicTBC / 2.1.37127, ingame reports its for wrath and wont load in TBC client

i might be an idiot, as release 8.1.37127 is ZygorguidesViewerClassicTBCAnniv
the download list as a QoL might have the proper names. but figured it out. Sorry about the post.

Quote:

Originally Posted by xstai ZygorGuidesViewerClassicTBC / 2.1.37127, ingame reports its for wrath and wont load in TBC client i might be an idiot, as release 8.1.37127 is ZygorguidesViewerClassicTBCAnniv the download list as a QoL might have the proper names. but figured it out. Sorry about the post.

It would definitely be a quality-of-life improvement if people downloaded the correct file.

A recurring issue is that people download the RXP version intended for China even when they are not playing in China, or they are playing in China but download the wrong version, and then wonder why it doesn’t work.

I’m planning to update the files with the next release to make this clearer. That said, I had assumed people would know which version they were playing.

Hey descentralizado, i cant click the zygor retail link, its like there is no link behind, could you check this out ?
thx a lote

Quote:

Originally Posted by Groovytje Hey descentralizado, i cant click the zygor retail link, its like there is no link behind, could you check this out ? thx a lote

So you do not want to say what link. After asking youu multiple times.
Seeing you claimed to click a link, that is not even there and avoid 2 links that says link.

Quote:

Originally Posted by Descentralizado The issue is that the instructions refer to “the link” without specifying which link is being discussed. Since there are two links, this can create unnecessary confusion. Users are aware that there are two links and, in some cases, they intentionally select the link they are not supposed to use instead of the one they actually need. They then return and report that the link does not work. If a user intentionally chooses the link they cannot use while avoiding the link intended for them, the problem is not with the link itself. The instructions need to clearly identify which link the user should select to prevent this confusion.

Hey, i send you a private message, usings your links for a long time so dont want to give you bad rep