[BUG] Version 3.0.30-TBCC produces faulty behavior, appears not to work

Question

[BUG] Version 3.0.30-TBCC produces faulty behavior, appears not to work

jallstein opened this issue 3 years ago · 16 comments

jallstein commented 3 years ago

No error messages produced, simply put the latest version of GSE appears broken.

Existing macros ceased to work.
Unable to create new macros.
When I press the close button within the sequence editor it does not return to the list of current macros which is the expected behavior.

Reverting to 3.0.24-tbcc resolved the issue. All versions available on curseforge newer than .24 either yielded errors or malfunctioned without error as described above.

jallstein · Answer 1 · 2021-07-17T17:04:53.000Z

After a lot of head scratching I was able to find out why I was experiencing issues. I recently ran a custom compression algorithm on the drive where my game client is installed. Although I whitelisted the WoW directory, I didn't whitelist the directory where I store newly downloaded addons.

Because I'm somewhat of a data hoarder I keep backups of recent addons in case I break something while tinkering with the code or if for some other reason, I need to revert back to an old version. Compressing the files on that drive meant that the file compression was applied to the full range of GSE addons that I'd downloaded - starting with version .25. Because this process is automated, each time I downloaded a fresh copy from curseforge it was subsequently compressed.

It wasn't until I saved the addon to another directory, which is what I'd done with v.24, that I was able to escape the automatic file compression and the root cause of the issue. I'm surprised the addon even worked at all under those circumstances, but here we are. You can close my ticket.

TimothyLuke · Answer 2 · 2021-07-17T19:50:04.000Z

WoW there is no way I would have ever thought of that.

TimothyLuke · Answer 3 · 2021-07-15T22:03:35.000Z

Mate there is not a single GSE macro in that file. If any macro works on any version with that file I am impressed. TimothyLuke

…

On 16 Jul 2021, at 7:21 am, jallstein ***@***.***> wrote: https://pastebin.com/51W8htMy — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

jallstein · Answer 4 · 2021-07-15T22:05:47.000Z

I finally managed to get it to spit out an error message.
Edit: This is from version 3.0.30-tbcc:

Message: Interface\AddOns\GSE\API\Translator.lua:71: bad argument #1 to 'gsub' (string expected, got table)
Time: Fri Jul 16 00:05:01 2021
Count: 1
Stack: Interface\AddOns\GSE\API\Translator.lua:71: bad argument #1 to 'gsub' (string expected, got table)
[string "=[C]"]: in function gsub' [string "@Interface\AddOns\GSE\API\Translator.lua"]:71: in function ProcessVariables'
[string "@interface\AddOns\GSE\API\Storage.lua"]:1521: in function CompileTemplate' [string "@Interface\AddOns\GSE\API\Storage.lua"]:512: in function OOCUpdateSequence'
[string "@interface\AddOns\GSE\API\Events.lua"]:454: in function `?'
[string "@interface\AddOns\GSE\Lib\AceTimer-3.0\AceTimer-3.0.lua"]:55: in function <...terface\AddOns\GSE\Lib\AceTimer-3.0\AceTimer-3.0.lua:50>

Locals: (*temporary) =

{
Action = "/use shield slam"
Interval = 1
}
(*temporary) = "~~GCD~~"
(*temporary) = 1.500000
(*temporary) = "string expected, got table"

TimothyLuke · Answer 5 · 2021-07-15T22:14:33.000Z

If I use your file I get … nothing. No errors. No Macros. I can create new stuff , import existing stuff, save stuff. I can’t tell you about existing stuff … as there’s nothing in the file you have sent me. If you have something loaded you may need to exit the game for the GSE.lua file to update to disk. WoW writes this file as part of shutting down WoW. TimothyLuke

…

On 16 Jul 2021, at 7:35 am, jallstein ***@***.***> wrote: I finally managed to get it to spit out an error message: Message: Interface\AddOns\GSE\API\Translator.lua:71: bad argument #1 to 'gsub' (string expected, got table) Time: Fri Jul 16 00:05:01 2021 Count: 1 Stack: Interface\AddOns\GSE\API\Translator.lua:71: bad argument #1 to 'gsub' (string expected, got table) [string "=[C]"]: in function gsub' [string ***@***.***\AddOns\GSE\API\Translator.lua"]:71: in function ProcessVariables' [string ***@***.***\AddOns\GSE\API\Storage.lua"]:1521: in function CompileTemplate' [string ***@***.***\AddOns\GSE\API\Storage.lua"]:512: in function OOCUpdateSequence' [string ***@***.***\AddOns\GSE\API\Events.lua"]:454: in function `?' [string ***@***.***\AddOns\GSE\Lib\AceTimer-3.0\AceTimer-3.0.lua"]:55: in function <...terface\AddOns\GSE\Lib\AceTimer-3.0\AceTimer-3.0.lua:50> Locals: (*temporary) = { Action = "/use shield slam" Interval = 1 } (*temporary) = "GCD" (*temporary) = 1.500000 (*temporary) = "string expected, got table" — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

jallstein · Answer 6 · 2021-07-15T22:17:08.000Z

I wouldn't look too closely at my GSE.lua file anyway because I nuke it every time I install a new version of GSE since the release of 3.0 anyway.

jallstein · Answer 7 · 2021-07-15T22:20:56.000Z

But my problem still persists though. All of the aforementioned version beyond 3.0.24 don't work for me.
In addition to cleaning the WTF folder, I've now disabled every other addon and still experience issues.

TimothyLuke · Answer 8 · 2021-07-15T22:52:58.000Z

Without that file with your content I cannot replicate your problem. If I can’t replicate it I can’t fix it. All I have to go on is “I think somethings not working and here is a random error message”. Your error could be caused by 1000 different things. The most common cause is GIGO - Garbage in, Garbage Out. But without context I have no idea which of those 1000 it actually is. TimothyLuke

…

On 16 Jul 2021, at 7:47 am, jallstein ***@***.***> wrote: I wouldn't look too closely at my GSE.lua file anyway because I nuke it every time I install a new version of GSE since the release of 3.0 anyway. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

jallstein · Answer 9 · 2021-07-15T22:57:27.000Z

I literally use GSE for one singular macro comprised of two action blocks.

Action block #1: /use devastate
Action block #2: /use shield block

The macro is so simple that I've just been wiping all of the relevant files in the WTF folder and recreating the macro each time I download a new version of GSE.
If my macro is garbage in, then how can I take the necessary steps to ensure that I'm using the addon correctly?

TimothyLuke · Answer 10 · 2021-07-15T22:58:41.000Z

The only way I can get close to your error is if I go into Raw Edit and completely ignore the block specification and put random stuff there. (Again this is a GIGO type error.) TimothyLuke

…

On 16 Jul 2021, at 7:51 am, jallstein ***@***.***> wrote: But my problem still persists though. All of the aforementioned version beyond 3.0.24 don't work for me. In addition to cleaning the WTF folder, I've now disabled every other addon and still experience issues. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

TimothyLuke · Answer 11 · 2021-07-15T23:06:19.000Z

Apologies for the spam and I appreciate I'm only level 60:

I don't have Devastate and it just skips for me to Shield Block.

The export of that is:
dCtecaGEuv1RfPMPIA2Q4MkKFja3wO6FIYoPYEj7MQ2ps8tbQHbLFJyGOkmyOQHlHdIshtkhwvlePSuuvzXivlxLEOO6PGLjrpxstuinvitwOmDkxuexvG8mOY1rXSuKTks2Sc12fK(OG4ROkACcQ(oQk2gQkDAPA0cXJrLtQGVHQuxtq58iPvkGwlQsUSsRMqY1eei78mGsgCOeajxPqcq)z9wvq2u2u2u2u2u2uMawglc5kiiFApHpEk4zzSiKRGqGKu7T2jE5WHHdtqIFm5YT5K4fV907NUrv0em)vlOIyVTXeuIv2W4DJVyHJdxRuak4C5kXcdRjy0ZDjvHKRjKGu)T)0pBvizcy5SoXxfsUMqY1eeatDPGp2g6xT3wbiQfRawoRt8YKRui5AccGPUuWdr67jgf80oeU0cqulwbSCwN4LjtWGNot)yP(B)PF2QqYKjtauSCdrLRjGN7NML5(vHKjy0AF03EHeG(Z6TQaA5uWNpZcWqUawglc5kGxeIrL)eIXd(TXzoKQGqGKu7T2jE5WHHfUGrVN5pdEBVHUERt8IMGO74N5yY1eK4htUCBojEXBp9(PBufnbqXYnevUMauW5YvIfgwtG7JVccKDEgqjdoucGKjtMea

TimothyLuke · Answer 12 · 2021-07-15T23:23:39.000Z

WIth no UI on the same version 3.0.30

jallstein · Answer 13 · 2021-07-15T23:55:24.000Z

Huh. That's odd. I just attempted to import the code that you pasted and the addon broke in a similar fashion to what I've experienced previously. No error message, the addon seemingly fails to save the macro and no newly created macro (or any macro for that matter) appears in the list.

At this point any reasonable individual should assume either one of two things: That the PEBKAC or that an unknown variable local to my system is causing problems. As far as I'm able to tell given the low degree of complexity involved with copy/pasting the string of text that you posted, and after double and triple checking that I did in fact do it properly I have a growing suspicion that something else is going on that's unrelated to your addon.

It's currently 2 AM where I live and way past my bedtime. I'll report back in the morning once I've had a chance to take a look at my system.

TimothyLuke · Answer 14 · 2021-07-15T23:58:52.000Z

Mate sleep well. There is ALWAYS a reason - we just have to figure out what that is.

TimothyLuke · Answer 15 · 2021-07-15T21:48:49.000Z

Any chance you could upload your GsE.lua file as all these versions work for me so there is something different at your end. Without that file I have no way of replicating what you are experiencing. TimothyLuke

…

On 15 Jul 2021, at 11:18 pm, jallstein ***@***.***> wrote: No error messages produced, simply put the latest version of GSE appears broken. Existing macros ceased to work. Unable to create new macros. When I press the close button within the sequence editor it does not return to the list of current macros which is the expected behavior. Reverting to 3.0.24-tbcc resolved the issue. All versions available on curseforge newer than .24 either yielded errors or malfunctioned without error as described above. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

jallstein · Answer 16 · 2021-07-15T21:51:06.000Z

Edit: apologies, posted the wrong file fixed now
https://pastebin.com/acYKmRQZ

Share to