Backloggery interop

Backloggery integration with game library websites

< Feedback on Backloggery interop

Review: Good - script works

§
Posted: 2025-03-12

I am loving the script, however, It doesn't look to be operating properly on GOG. I did get the script to load on the gog website, as TamperMonkey was reporting that it was not at first, but the import functions don't seem to be firing off properly. For example, when I added "*://www.gog.com/u/*", it was loading on my profile, but there is a lot more that I don't know where or what to edit to get it to activate properly.

§
Posted: 2025-03-13

…Have you actually read the usage instructions? Or at least looked at the attached image guide?

It works on GOG exactly as it's supposed to. Just click the Sync button in your library.

§
Posted: 2025-03-13

I *thought* I did. It wasn't loading on the site still, though? Re-installed, reloaded the page, all good.

§
Posted: 2025-03-13
Edited: 2025-03-13

If it wasn't working at first but worked after reinstall+refresh… Then my best guess is "browser error" (…or maybe a website bug happened) 😅

Regarding diagnostics and what you were trying to do: the script does different things on different pages, so obviously the first thing it has to do is detecting which page it's loaded on and therefore what should be done next. When this script starts working, it logs [BL] loaded on Verbose level of Browser Console (which you can open by pressing F12); and when it determines which page it's loaded on, it logs [BL] activated! on Warnings level (in yellow, to make it stand out visually). If at any point you're suspecting that this script misbehaves, you can inspect the console to check what actions were reported by it – e.g. to see if it failed to recognize the current page, or to find out what was updated during sync.

Also, if any errors happen during its execution, they'll be logged as well (on Errors level, in red), along with a link to the code line where the error happened; that might help with figuring out the problem if it happens. (Note that the website errors are logged there as well… You can tell if the error happened within a userscript by the link text – it matches equivalent links for logged lines marked with [BL]; in Chrome it starts with userscript.html?, while in Firefox it contains script name with extension .user.js.)

Post reply

Sign in to post a reply.