Authors CurseForge

I was definitely wrong with my guess to the cause of this bug in the original post; it has nothing to do with time between commits as far as I can tell. I literally cannot get this project to build correctly now regardless of timing - all new Alpha, Beta, and Release versions display this bug, which obviously makes the files unreadable by Wow.exe.

 

Link Removed: http://www.mediafire.com/file/gd3or20t679f7zv/SimpleObjectiveProgress-r21-alpha.zip here is an alternate download link to the file I linked in the OP, for users without access to that file who are curious.

 

Since there aren't tons of others in here complaining about the same issue yet, I assume this issue is exclusive to Mercurial.

Code of 'damaged' file: https://www.curseforge.com/paste/00f16a23

 

The 'working copy' and 'destination' tags on each end make me think this is some kind of bizarre bug, possibly related to my repo type (Mercurial).

 

Here's the library build (does not display this issue): https://wow.curseforge.com/projects/libobjectiveprogress-1-0/files/2476407

Here's the build of the addon that packaged it: https://wow.curseforge.com/projects/simpleobjectiveprogress/files/2476409 (Note: I had to archive this because it would break all of my Alpha users' installs otherwise - hopefully you can still access it even as archived.)

 

Edit: By the way, it was a clean, straightforward commit/push in the repo. Neither update had anything weird going on. The only thing that could be related is that they were updated fairly close together (~5 minutes apart), but that's very often the case with these sort of things (when a primary consumer of the library is the same author who created it).

+1 for a resolution to this issue - it breaks my addon completely in-game when embedded.

 

i.e. 1x ...ctiveProgress\Libs\LibObjectiveProgress-1.0\LibObjectiveProgress-1.0.lua:7: unexpected symbol near '@'

 

I could work around it by trying to detect if the resolved symbol is a number and providing an alternative, but that is pretty crazy.

Quote from nickstaroba

(Yes, globals bad. I'm still trying to figure out how to set variables in an if statement without using globals... I'm used to dabbling in PHP.)

It's actually a lot easier than you'd think

local outside
if pancakes = 5 then
	outside = 12
end

print(outside) --> 12

Basically, just declare a local right before the if statement (outside it). If you want the variable available at the function level, just declare it outside any functions (still with local).