"Completed by an alt" setting not working in v90001.3+
Steinbaum7 opened this issue ยท 3 comments
Starting with version 90001.3 I noticed that I would get announcements on seemingly every single rare that is detected by the addon. I am not sure if it is indeed the case that every detection will trigger an output, but what I can confirm is that the "Completed by an alt" setting has no effect, as I always have it off yet I keep getting spammed, for example, as I travel around Mechagon with my alts, while my main has fully completed the related achievement (Rest in Pistons).
I also experience the exact same issue in Argus. I would expect this behaviour to replicate regardless of zone but those are some of the places where I have been the most lately and have regularly witnessed this behaviour.
I am not sure what changed from v90001.2, but the only solution I have found to this issue is to downgrade to that build. I was waiting for a new build to come out in hopes that the issue would be fixed but it is still manifesting in the newly-released v90001.4.
I saw a fellow user commenting in the Curse page about having this issue (Comment #1589, posted by domi1294 on Oct 27, 2020), right after v90001.3 was first released, but their remarks appear to not have been noticed.
I tried to do some text comparison between different versions of some of the files to try to spot what change might have caused this but I am unfortunately clueless as to the inner workings of the addon and didn't find anything.
I updated my addon up to v90001.6 (as I noticed it released a few hours ago), and I replaced the announce.lua within with the amended text from that last commit.
I just took a quick tour across mechagon and did not receive any alerts on my alt from either vignettes or mouseovers. There haven't been any chat-announced rares while I've been online testing so I can't confirm the behaviour from that source but looks like it is all working now.
Cheers and thanks for the quick fix.
Okay, looks like when I added the loot stuff I shuffled it up so that the achievement check happened after the "is there a vignette?" check, which is bad for this.