Posted April 30, 2017
adaliabooks: That is very odd... do you get any errors along side it not working?
It sounds more like an issue with Greasemonkey, Firefox or some kind of conflict rather than an issue with either script but it's hard to know.
It is very odd indeed. I'm not seeing any errors in the console log etc. but I agree that it appears as some sort of conflict or glitch in greasemonkey perhaps. I'll probably poke at it more when I have time and see if I can figure anything out, as well as testing out new releases of either script and greasemonkey itself. It sounds more like an issue with Greasemonkey, Firefox or some kind of conflict rather than an issue with either script but it's hard to know.
I just went through my installed extensions list also and culled some that I don't really use or need any more. Hopefully sometime by 2024 all of my addons will be multi-process compatible also and I can benefit from that. :P
Barefoot_Monkey: I agree with Adaliabooks - it definitely sounds like something went wrong with GreaseMonkey itself (or even a different extension) rather than with any of the scripts themselves. The strongest evidence is that Tools->Addons was breaking for you, but nothing that a user script does could cause that because they don't even run on that page. However, the GreaseMonkey extension itself does modify the Addons page.
Something that could provide some insight is the Browser Console. Press Ctrl+Shift+J to open up the Browser Console window. It might be clogged up with messages from other pages, so you can press that little rubbish bin icon in the top-left corner to clear it. Then alt-tab back to a Firefox window with a gog.com page open and refresh the page. Alt-tab back again to the console window and it may now be full of messages. Press Ctrl+A then Ctrl+C to copy everything to your clipboard and then send it to me via chat, and I'll take a look.
Yeah, nothing really shows up in there that looks unusual either. I do have an idea however that I could try, which is to make a new Firefox profile and just install Greasemonkey and the two scripts in it by themselves and see if the problem happens, then add other extensions one at a time to see if I get any conflicts. Scientific method FTW. :) That is of course always a PITA to do time-wise when one does it, but it often does find the culprit or narrow things down.Something that could provide some insight is the Browser Console. Press Ctrl+Shift+J to open up the Browser Console window. It might be clogged up with messages from other pages, so you can press that little rubbish bin icon in the top-left corner to clear it. Then alt-tab back to a Firefox window with a gog.com page open and refresh the page. Alt-tab back again to the console window and it may now be full of messages. Press Ctrl+A then Ctrl+C to copy everything to your clipboard and then send it to me via chat, and I'll take a look.
Post edited April 30, 2017 by skeletonbow