Is this the log?
Yes! Thank you!
I wish I could give you a dozen more upvotes for being the first person to post a complete bug report. I can't, so I'll just fix your bug instead.
For the curious:
The problem is that the browser loads up the extension scripts at the same time that the Goko scripts are loading. This means the extension code can never be sure that the required Goko objects exist and are ready for it to modify. Analogous issues are responsible for a lot of goko's fragility.
I wrote the "depWait" function to address this. It checks for the required objects then goes to sleep for a bit if goko hasn't created them yet. Only when those objects exist does it run the meat of the script. It's an ugly solution for an ugly programming environment. If any real coder out there knows the "right way" to address this issue, I'd definitely appreciate some advice.
Ironically, Awaculus' error happened because the depWait function itself hadn't been created yet. Just as the extension can't know which goko code will get run before it, it also can't know which of its own scripts will be run first. I have depWait defined in a separate file that
almost always runs before logviewer.js does. I'll have to change that.