BugGrabber could really use the new multiple .toc feature
b-morgan opened this issue · 13 comments
Describe the problem
BugGrabber only has one .zip file on CurseForge with a single .toc containing ## Interface: 90005 (retail). If there were three .toc files, !BugGrabber.toc, !BugGrabber-bcc.toc, and !BugGrabber-classic.toc, with the ## Interface: set appropriately in each, then BugGrabber would be up-to-date on all three versions of WoW automagically. This is a new feature from Blizzard that I don't think has been widely publicized. See https://www.wowinterface.com/forums/showthread.php?t=58747&highlight=multiple+toc+files.
In these uncertain times just after Blizzard has released Burning Crusade Classic, Blizzard wants to disable all out of date addons. Clicking Load Anyway will fix BugGrabber, but also allow any other addons that have not been updated to load potentially causing all sorts of errors.
What steps will reproduce the problem?
- Install BugSack and BugGrabber on all three flavors of WoW
- BugGrabber is out-of-date on BCC
- BugGrabber is out-of-date on Classic
- BugGrabber is completely operational on Retail
Consider attaching a screenshot below to help describe your issue (Attach directly, do not link to other websites)
What version of the addon are you using? (Stating 'latest' is not useful)
v9.0.2 dated March 27, 2021.
Do you have an error log of what happened?
N/A
Any additional information? (example: WoW language if not English)
Alternate Plan B would be to publish three versions of BugGrabber just like BugSack.
I see the multiple .toc files in the BugSack zip files but their names are NOT the names Blizzard is looking for so they probably won't work. In addition, this issue was about BugGrabber and I can't find an updated release for it.
I see the multiple .toc files in the BugSack zip files but their names are NOT the names Blizzard is looking for so they probably won't work.
I like how you state this as fact whilst at the same time not having a clue what you're talking about. BugSack is fine. If you're unsure of something, be polite and word it as "are you sure this works" instead of the attitude you used in that reply.
In addition, this issue was about BugGrabber and I can't find an updated release for it.
I was talking about BugGrabber, which was updated and is visible on the CurseForge website. But there seems to be some caching issues with the latest zip being picked up by the app.
@b-morgan Please do a few seconds of Google research before saying things like that. :P
The new filenames at https://github.com/funkydude/BugSack are correct.
@Bananaman I think you mean https://www.curseforge.com/wow/addons/bug-grabber/files as your link is BugSack not BugGrabber.
I was talking about BugGrabber, which was updated and is visible on the CurseForge website. But there seems to be some caching issues with the latest zip being picked up by the app.
Yeah. He could have just checked https://github.com/funkydude/BugSack/releases which shows a new release before his rude and stupid post.
Thanks a lot for the new release! 🙏❤️
@funkydude Ah, right. I was checking this commit in this repo:
But either way the TOC filenames you are using are correct! :D
Sorry about the TOC filename comment. I was going from memory (which is probably failing at my age). In any case, BugSack is fixed, BugGrabber is not which was my main focus.
BuggGrabber is fixed, ETA on when it becomes available is not in my control, it is a patch day after all.
EDIT: I have tried to force it by publishing a new zip.
@funkydude Thanks for fixing it. I'll just wait until the update shows up in the usual places.
agreed with the above, works fine by adding the needed .toc files (simple fix)
Second this - I came to grab the addon for BC and noticed this back in Classic as well. I came to write this issue myself but noticed you already did it, so I'm going to +1 your request.