BugCatcher : Discontinued & Outdated : Elder Scrolls Online AddOns

(180 Kb)

Download

Updated: 03/18/18 06:44 AM

Add Favorite

Install Help

Portal

Bugs

Features

Pictures

File Info

Compatibility:	Dragon Bones (3.3) One Tamriel (2.6)
Updated:	03/18/18 06:44 AM
Created:	05/08/15 10:45 PM
Monthly downloads:	328
Total downloads:	211,795
Favorites:	142
MD5:

BugCatcher Popular! (More than 5000 hits)

Version: 017-100022

by: Werewolf Finds Dragon [More]

Please read this.

I'm taking another break for a while. My anxiety isn't holding up well and I need to take some time for myself to recover. Frankly, modding can be a thankless job and some of the people one is forced to interact with can be... deeply unpleasant at best, to put it in the kindest way I can and not as I truly want to. For now, I feel like my mods don't need any further work done to them. They're fine as they are. See you later, folks.

I'll be back! I'm not gone for good, I just need to set this aside for now. That's all.

One thing I will say as a final note is that it'd be nice if one could turn off the comments system and only have a bug tracker in the vein of Nexus Mods. That'd be handy for people like myself who do deal with anxiety. And I deal with a lot of anxiety.

See you around, folks. My thanks to those who were kind.

Click here to check out my other addons.

Description

You're in a delve or PvP, and suddenly something breaks and you're spammed by lua error messages that you have to click through. That's no good! This mod fixes that. In the most basic terms, it suppresses addon error messages until you want to see them, and that's how it should be!

It's mostly something you can just drop in and forget. BugCatcher will suppress error messages and let you know with an unobtrusive chat window message when it catches a bug. So you can play without stress. Bug Catcher is the no-nonsense addon that deals with the bugs and lets you just play.

And when you want to see those bugs? You have a nice bug catalogue to browse through, at your leisure.

Notes

WARNING! I imagine you're getting BugCatcher because you want your bugs handled on the down-low, all quiet like. So, if you use the addon No, Thank You, it's important to ensure that the bug handling features of it are turned off. They're at the bottom, there are two dropdowns that should be set to 'dialog' and 'none' respectively. Otherwise you'll get notifications.

How to Use

The Bug Log

In your addons options menu (Escape -> Settings -> Addons), under BugCatcher, you'll find an easy to use bug log that will allow you to browse your errors. You can also click the BugSack icon to open it.

The Bug Sack

In the main menu there's now a tiny icon at the top left (which I'll call the BugSack icon). If it's faded out, you have no bugs; If it's not, you have bugs.

The BugSack icon now has a tooltip as well, it explains how this particular feature works. You can click the icon to show the bug log, alt + click it to wipe the bugs database, or just view the current count within the tooltip itself.

Only Useful Errors

There are errors in ESO that don't technically mean anything. They'll only serve to spam you and annoy addon authors if you pass them along. These useless errors are repressed, and BugCatcher's bug log contains only errors which are useful to addon authors. So rest assured that whatever errors you see are actually going to be helpful.

On a more technical level? The useless errors BugCatcher hides are XML-based. Such as XML UI and XML OnUpdate errors. All they really tell us is that the addon may need its XML elements reimplemented in lua, but not every addon developer has time for that.

View Bugs Outside of ESO

In the Utils folder, you'll find a file named 'Write Bugs to Text File.' If you double-click this file, as you would any other Windows file, it'll immediately generate a file named Bugs.txt. You can then peruse this at your disposal.

You should use this when ESO is closed, as ESO doesn't seem to write its databases to file until you've logged out. I've included this functionality for addon developers who can't be in-game all the time, and for group leaders/guild masters with less tech savvy users. In the latter case, they can just ask that the aforementioned less tech savvy users pass along their exported bugs. It's easy enough to explain to them how to do so, since it's basically just clicking a shortcut, and then uploading a text file.

If the text says 'No Errors Found,' then you've got no errors in your database. You're error free!

Disclaimer

I'm sharing this addon because I genuinely get satisfaction out of the mere possibility of helping others, even when I don't know for sure. I have no interest in being popular, cults of popularity squick me out. As such, considering my disabilities, I'm unlikely to look at the comments very much. So this addon is delivered as-is, with a hearty dose of caveat emptor. Anything that it doesn't already do is 'out of scope.' You have other choices. I just wanted to make an simple, elegant solution for a real problem I was having. And now I'm sharing it in case it helps others.

Credits

My beau, who puts up with my ADHD and autism and enables me to actually do things like this.

I looked at Horse Timers to figure out how to make a clickable icon.

This is a homage to BugSack from WoW of yore.

:: 017-100022

o Bugfixes and performance updates.
o Updated interface version.

:: 016-100017

o What I did in the last patch was a very stopgap measure. I wanted time to come up with some way to deal with bugs that occurred before BugCatcher loaded. I took a page from the original BugSack and created a temp database which would pass errors along when BugCatcher has been fully initialised. BugCatcher should no longer ignore bugs that occur before it loads properly. Nor should tehy any longer cause issues.

:: 015-100017

o Made sure BugCatcher wouldn't try to handle bugs before it was fully initialised.

:: 014-100017

o Moved some checks around to try and further avoid any erroneous happenings, just to make BugCatcher even more robust. That'll sort everything out, I hope.

:: 013-100017

o Despite initialising the database as early as possible, some errors are still slipping in before BugCatcher's database has properly initialised. Grump, grump, grump. As such, I've brought back in a couple of checks to stop that from happening. This and the prior update should mean no more XML-caused weirdness slipping through. Sorry about that.

:: 012-100017

o I see what's happening. Some virulent XML errors are firing before BugCatcher has a chance to initialise its database. I've switched some things around so that that can no longer happen. Hooray. Bloody XML errors. No one likes you, pointless XML errors, go home.

:: 011-100017

o Put in a couple of extra checks to help deal with an odd error string issue that would make BugCatcher behave improperly. I think I have that fixed, now. Seems to be, at least.

:: 010-100017

o Bit the bullet and did something I've been thinking about for a while. No one uses the developer functions anyway (I've done some looking around), so I've just removed them. It's a little bit of unnecessary bloat if no one's actually using them. And BugCatcher is a consumer-focused addon, anyway.

:: 009-100017

o More cleaning up after the switch over to BugCatcher's shiny, new hotness. With the new way BugCatcher works, I believe that the 'display' component of the developer-focused function handleErrorString was detrimental to the everyday user. So I've removed it.

:: 008-100017

o A vestigial check was accidentally left in that would stop BugCatcher from going past collecting thirty bugs. After the redesign, this limitation is no longer necessary, so the check has now been removed and the only limit on bugs rests with the system rather than BugCatcher itself. Sorry about missing that.

:: 007-100017

o The bug page now saves across sessions, so if you want to keep track of a bug whilst reloading your UI (without the page automatically resetting to 1), you can do that. If it's more desirable that it stay on 1, let me know. I may provide some kind of option, there.
o Did a lot of work on the new UI, have a look at the screenshot. The duplicates indicator has been moved out of the error itself (a vestigial factor of how BugCatcher used to work) and into its own description above the bug. And alongside that the duplicate count, we now have the latest timestamp of when that error was seen.
o Other little touch-ups.

:: 006-100017

o Fixed a minor cosmetic issue with the BugSack module where the icon wasn't lit up if you had bugs after a UI reload.
o Colourised the Bug Log title, because why not?

:: 005-100017

o Wow, big changes. I rewrote so much of how BugCatcher works, let's see...
o I removed the slash commands, bindings, and the localisation just to make this new version easier to handle (sorry to whom this inconveniences, but they don't seem like popular features).
o This new version handles errors more elegantly through a brand new error log.
o There's better modularity with the one module I did keep separate (the bug sack).

:: 004-100017

o Updated LibOmniMessage.
o Further improvements to LibOmniMessage implementation.

:: 003-100017

o Cleaned up LibOmniMessage implementation more to remove redundancy.

:: 002-100017

o Fixed LibOmniMessage implementation.

:: 001-100017

o Added 'AddonName_Update:[Number]:Blah' type errors to the ignore list. It's this season's version of the number-spam bugs. These come from addons using XML OnUpdates when they really, really shouldn't. They should be using RegisterForUpdate or zo_callLater instead. The XML OnUpdate system is buggy and doesn't return anything valuable in the way of debug info. You won't actually get anything useful from seeing these bugs. They'll just make you want to pester the mod authors in question to change their stuff over from XML-based OnUpdates.
o Fixed up some other random stuff.

[Data prior to this version has been cleared.]

Optional Files (0)

Comment Options

Page 2 of 4

12/17/16, 01:37 AM

Martan

Forum posts: 4

File comments: 76

Uploads: 0

Originally Posted by joshmiller83

user:/AddOns/BugCatcher/Components/Core/Core.lua:185: attempt to index a nil value
stack traceback:
user:/AddOns/BugCatcher/Components/Core/Core.lua:185: in function 'bugCatcherAddon.errorHandler'

Got this one as well recently.

11/26/16, 10:10 AM

QuadroTony

Banned

Forum posts: 828

File comments: 3866

Uploads: 3

Originally Posted by WfD Temp Account

Sorry. My prior account was banned under mysterious circumstances, most likely due to a very minor altercation between sirinsidiator and myself. I have asked the MMOUI network to pull my addons, since I can no longer maintain them. I had removed myself from active development (I wouldn't be making new features), but I was willing to still do bug fixing on my work. As it is, I can't even do that, now. Sorry.

As you can imagine, this is out of my hands. You might be able to rely on kind users providing patches for issues, but I can no longer do so myself. And I don't want to push my luck by trying to upload on this account. Again, sorry.

im curious what is really happened...

11/26/16, 10:08 AM
WfD Temp Account Forum posts: 0 File comments: 34 Uploads: 0	Sorry. My prior account was banned under mysterious circumstances, most likely due to a very minor altercation between sirinsidiator and myself. I have asked the MMOUI network to pull my addons, since I can no longer maintain them. I had removed myself from active development (I wouldn't be making new features), but I was willing to still do bug fixing on my work. As it is, I can't even do that, now. Sorry. As you can imagine, this is out of my hands. You might be able to rely on kind users providing patches for issues, but I can no longer do so myself. And I don't want to push my luck by trying to upload on this account. Again, sorry.

11/23/16, 05:08 PM
joshmiller83 AddOn Super User Forum posts: 70 File comments: 243 Uploads: 0	user:/AddOns/BugCatcher/Components/Core/Core.lua:185: attempt to index a nil value stack traceback: user:/AddOns/BugCatcher/Components/Core/Core.lua:185: in function 'bugCatcherAddon.errorHandler'

10/23/16, 07:35 AM
Wastelcat Forum posts: 0 File comments: 56 Uploads: 0	Problem solved :) Hi Werewolf, thx for the help - that solved it - i had 1 turned of but the other was not at dialog. Cheers Wastelcat

10/22/16, 07:14 PM
Werewolf Finds Dragon Forum posts: 17 File comments: 105 Uploads: 15	@Wastel Oh, no worries. It's completely okay. I wish I'd known to tell you. Sorry! Yeah, so 'No, Thank You!' has its own extremely basic bug handling functionality. If it's enabled, it messes with BugCatcher's ability to do anything. You have to turn it off. I'm using 'No, thank you!' and with those features turned off the two co-exist just fine. There's a note about it on my addon's front page. Glad it's sorted!

10/22/16, 06:39 AM
Wastelcat Forum posts: 0 File comments: 56 Uploads: 0	@werewolf Hi again, had tie to test with the addons today. dis/enabled all 1 by one. Seems the errors only pop up if i have NoThankYou addon loaded. So with it bugcatcher cant fetch it - without it nothing is to fetch Hope this can be helpful. Thx again Wastelcat

10/21/16, 08:34 AM
Wastelcat Forum posts: 0 File comments: 56 Uploads: 0	@werewolf The result i get from /showbugs is nothing in the chatwindow but onscrenn: invalid command The other i can test tommorw as today its to much work in RL - just could hopp in game 30 secs and out again Cheers Wastelcat

10/21/16, 04:34 AM
Werewolf Finds Dragon Forum posts: 17 File comments: 105 Uploads: 15	@Wastel The plot thickens. This is bizarre. I really am wondering if you're getting errors before BugCatcher even has a chance to load in. Those are some virulent errors. I've never heard or seen anything of the like, but I do want to help. Okay, try typing... Type: /showbugs What do you get (and in the chat window, too)? And did you try to see if you get the error with only BugCatcher loaded?

10/21/16, 02:27 AM
Wastelcat Forum posts: 0 File comments: 56 Uploads: 0	@werewolf Hi mate, i treid the: /script this.is.a.nonsense.function() No error shows up, which means - as far i understand - that Bugcatcher works fine on these. And yes i dont have any others than the Worldmap ones atm. The other thing i can recall is the error you get if the group leader ass if you are ready and they will count up hundred untill you press confirm. But hadent those in a while because i hardly have time for grouping these days. About me demanding anything - i cant remember i pay you or that you are my husband - so nothing i could demand . Thx for your kind help. Wastelcat

10/20/16, 02:31 PM
Werewolf Finds Dragon Forum posts: 17 File comments: 105 Uploads: 15	@Wastel No worries. So long as you're not demanding new features it would be stressful for me to code in, generally I'm going to want to help. I think that's the thing that breaks me the most. And I really do want to help. Okay, so let's scientific method this, okay? What we're going to try and do is figure out whether it's just these WorldMap errors that aren't being caught, or whether something is messing with BugCatcher's entire ability to handle errors. I have some unique ideas about how to deal with this, even going as far as running a grep (which looks inside files) for functions in your addon folder that could mess with BugCatcher. But let's take it one step at a time. First of all, try this: /script this.is.a.nonsense.function() That'll generate an error because this.is.a.nonsense.function() doesn't exist. If BugCatcher gets that one, it means that something is just up regarding WorldMap errors. If it doesn't get that one, then it means that something is up with the entire bug handling system. If it's just WorldMap, it could be to do with the WorldMap, or more likely... it's quite possible that the bug could be appearing a matter of milliseconds before BugCatcher loads. This would be a tiny, tiny window and the chance of it happening should, in all rights, be infinitesimal but I'm not going to discount it. I have a scenario to test for and deal with that as well. But yes, scientific method. Try: /script this.is.a.nonsense.function() And get back to me. Thanks. Edit: And just so you don't have to wait forever for me to try and figure this out? You could also try this if you want. Backup your SavedVariables from <Documents>\Elder Scrolls Online\live\SavedVariables (or the EU variant if you're playing on the EU server) into a zip, just to be safe. Disable all your addons except for BugCatcher. Don't worry, this won't hurt anything because your SavedVariables won't go away, and even in a worst case scenario we have a backup. With your addons disabled, try this again: /script this.is.a.nonsense.function() I hope I can actually help with this. Last edited by Werewolf Finds Dragon : 10/20/16 at 02:37 PM.

10/20/16, 09:45 AM
Wastelcat Forum posts: 0 File comments: 56 Uploads: 0	Here is one sample Lua Error Hi again. same thing with freshly downloaded file. Here is one typical LUA error i get: EsoUI/Ingame/Map/WorldMap.lua:3075: attempt to index a nil value stack traceback: EsoUI/Ingame/Map/WorldMap.lua:3075: in function 'ZO_MapPin:SetLocation' EsoUI/Ingame/Map/WorldMap.lua:3279: in function 'ZO_WorldMapPins:CreatePin' (tail call): ? user:/AddOns/MiniMap/MiniMap.lua:5427: in function 'CreatePin' EsoUI/Ingame/Map/WorldMap.lua:3206: in function 'ZO_WorldMapPins:AddQuestPin' EsoUI/Ingame/Map/WorldMap.lua:3168: in function 'ZO_WorldMapPins:OnQuestAvailable' EsoUI/Ingame/Map/WorldMap.lua:3161: in function 'callback' EsoUI/Libraries/Utility/ZO_CallbackObject.lua:111: in function 'ZO_CallbackObject:FireCallbacks' EsoUI/Ingame/Map/WorldMapQuestBreadcrumbs.lua:177: in function 'ZO_WorldMapQuestBreadcrumbs:OnQuestPositionRequestComplete' EsoUI/Ingame/Map/WorldMapQuestBreadcrumbs.lua:13: in function '(anonymous)' Hope this is helpful in any way. Cheers Wastelcat

10/20/16, 08:21 AM
Wastelcat Forum posts: 0 File comments: 56 Uploads: 0	Thanks for quick reply Hi mate, just to make clear my post was NO complain in any way. I am pretty sure you have nothing to fix - i just wondered if i had to set up anything and missed that. Zip checked and reloaded, will test as soon i find time to play . Yes i do have a fat list of other addons which may cause this - ~ 40 or so and i am using the german client. The Luas i get are here since one tamriel and seem to pop up every time a quest is marked into the map or removed after quest completition. I will try to catch one and clip it for you later. Thank you Wastelcat

10/20/16, 05:41 AM
Werewolf Finds Dragon Forum posts: 17 File comments: 105 Uploads: 15	@Wastel I'm really not sure, it's working for me right now. I suppose it could be an unzip error. Try unzipping it with a different program and see if that helps? Other than that, I don't know? Hmmm... Okay, with unzip-related issues ruled out, what other addons are you running? Perhaps you have an addon that's screwing with the error management system in a way that BugCatcher doesn't know how to deal with? Incompatible addons, basically. Could you give me a list of what you're using? And could you show me some of the errors you're getting? Just to be sure, I logged in and fired a fake error. I used this: /script flibble.dongler() And here was my result: As you can see, it's working perfectly for me. So I really don't know what's up. I can't fix what I can't reproduce. If you can give me more info, though, I'll see what I can do?

10/20/16, 01:45 AM
Wastelcat Forum posts: 0 File comments: 56 Uploads: 0	Help please First, thx a lot for sharing this nice one, i would like to ask if i miss anything i have to do. I installed this addon and its loaded. But it does not seem to catch the LUAs as i hoped, they just pop up llike before. As i cant find any settings - i just wanted to ask what i am missing TiA Wastelcat

Page 2 of 4

Report this File