It just says "Failed to load response data". There are now two entries called "item/", one of which is red. The red entry says this: I don't understand how this could be on my end. Nothing has changed on my end. I haven't installed anything except that recently Barefoot Essentials updated a couple times. I'm sure I'm not the only one who's running both scripts on Chrome, though, so it makes no sense that I'm the only one who's experiencing this issue. It also makes no sense that the issue keeps showing up, then fixing itself, then coming back, then fixing itself, etc.

I don't think those are to do with me...

I'm not sure what the issue could be then.. can you start a new Chrome profile and just install Tampermonkey and the script and see if it works at all?
I can't see anything wrong on my server end that should cause a problem...
Well something is blocking the JSON data from my server, similar to the issue I just fixed for Firefox. It's not basic Chrome as I use Chrome (as I'm sure many others do) and get everything fine.
So it must be some kind of extra security setting on your end. If I can figure out what that is I might be able to change my server's response to work around it but I can't do that until I know exactly what is going wrong (which is the problem with fixing these kinds of issues, I can't see what might be causing it on your end)

Creating a new profile and only installing Tampermonkey and AF does not change anything. At this point, I don't see how it could be on my end, but I also don't see how I could be the only one who's experiencing these issues if, indeed, it isn't on my end. Strange.

Now it's fixed. Whatever you did, thanks!

Hmmm... other than the headers I changed earlier I haven't done anything.

How very odd...

Careful. The issue has fixed itself a few times before - but so far it came back. Let's hope that it's really fixed for good now.

Admittedly some of the negativity is due to trolling from some users, but as for some of the other 'negative' comments in the forum, like recently over you-know-what, I'd say that much of it is a consequence of GOG's development of the last roughly 3-4 years.

But I understand your position, and after putting so much time into it we can have no complaints that you want to scale down a bit, or retreat. I'm not much active in here either, as there quite frankly isn't much point given most of the discussions.

And it's doing it again. The only thing that's changed this time is that I just installed the Windows 10 April Features Update, but I doubt that's relevant.

Have you got any external firewall or other program that might be interfering? Have you changed internet connection?
Literally nothing should have changed on this end, and the script itself isn't changing, so there must be some kind of outside interference causing the problem... I just have no idea what it could be.

I'm running ZoneAlarm Free Firewall, but that's been the case ever since I switched to Windows 10 x64 on this PC in September 2016. I had not run into this issue at all up until a couple of weeks ago, and nothing has changed on my end in terms of my ISP, router, security software and settings. The most recent time any of those changed was when I switched my ISP and bought a new router in late January. I doubt any of that has anything to do with this bug, seeing as how the bug only started a couple of weeks ago. Also, I'm using an ethernet cable, not Wi-Fi.

Any idea when exactly it started happening?
I think the SSL certificates renewed about a week ago... So it could be related to that like the Firefox issue was.
Have you noticed any regularly in when it does or doesn't work?
Just trying to pin down anything that might cause a problem...

The first time it happened, I posted about it right away. It appears that it was on April 14. It stopped working for a few days, then worked for a few days, then stopped working for a few days, then worked for a few days. I posted every time it stopped or started working. Thanks for trying to help. I really appreciate it.

EDIT: One more thing. Sometimes it takes 5-10 seconds before refreshing, but sometimes it refreshes immediately. Either way, when it finishes refreshing, the sort order is exactly the same as it was before it refreshes. When it's working properly, it shows the Gog sort order, then a second or two later it refreshes and sorts by last updated.

I'll have a look back through the thread and see if the times its come on and off relate to anything in anyway.

It's no problem :)

Thanks