Hmm... I think I know why this may be...

Alright, magog should start to fix itself now. It had been using an ID <---> Game mapping generated by the wiki, and this mapping had been lost in the great wiki upgrade. I got it back up and running.

Thanks for the two missed IDs. Added them to the list of spurious GOG IDs for MaGog to ignore.

As for not getting the wishlist. I just tried myself and had no problem. Please try again; you might have inadvertently pasted the wishlist contents incorrectly.

It should look something like this:
{"wishlist":{"1207660611":true,"1207660621":true,"1207660843":true,"1207662543":true,"1207664323":true,"120766 4853":true,"1207665533":true,"1207665773":true,"1207665893":true,"1230412827":true,"1312830628":true,"13849449 84":true,"1420803723":true,"1423214112":true,"1424167104":true,"1426256123":true,"1433927691":true,"1435138681 ":true,"1439805257":true,"1444826419":true,"1449651388":true,"1455785261":true,"1459337461":true,"1773820830": true},"checksum":"e9ef9a5bc4d2d179c83f6295b1bb47"}

^

: '(

While you're here, a few issues, which may be long-standing and may have already been mentioned, don't know that, but either way:

Even if you select not to include removed games, they, or at least some, are included. Noticed it again due to throwing off the (now further reduced after the Brazilian launch) count for [url=http://www.an-ovel.com/cgi-bin/magog.cgi?ver=751&scp=gdsp&dsp=ipgfsorc&flt=prp~0~pat~0.01~&opt=nsf]the flat-priced search[/url].

Not sure if exactly a bug, but sorting by price sorts by current price, not full. [url=http://www.an-ovel.com/cgi-bin/magog.cgi?ver=751&scp=gdsp&dsp=ipgfsorc&ord=p9&flt=tcs~oddworld~&opt=nsf]Example.[/url] With the option available below only applying to regional prices, if this is intentional maybe there could be two sorting options, full price and current price.

Also, why does removing the version parameter from the URL make it ignore scope restrictions (or at least that's what I noticed first)? That same flat-priced search with that removed also returns upcoming games for example. If it behaves differently according to it, shouldn't it default to most recent if missing?

I'm not here, but MaGog notifies me whenever someone posts in this thread.

If we take your example, the scopes requested include Premium Editions and exclude Removed Games, among others. Now, the question is what should MaGog do with a game such as Fallout Classic, which is both premium and removed. The default, which you have used, is to include any game that meets at least one included scope, e.g. premium (this is called a "Greedy" algorithm). The opposite algorithm (called "Restrained") will exclude any game that meets at least one excluded scope, e.g. removed. You can choose which algorithm to use via the "Scope Algorithm" option. Just use "Restrained" (this will add an "r" to the opts= field in the URL) and all the removed games will disappear. For more on this, see the Version 6.4.4 entry on the ChangeGog page.

As you rightly state, the Show/Sort Current/Full option, as labelled, only refers to regional prices. The base price sorting is always based on full price. The reason is quite simple: as far as I remember, nobody ever asked for the current price sort. I'll get to adding it later this week (assuming I manage to tear myself away from Etherlords).

The version field was added to the URL in version 1.3.2. Therefore, if it is missing, MaGog assumes the search was generated by a pre-1.3.2 GUI and acts accordingly (yes, there are still links on the forum from that time, and yes, they are still being clicked on, based on MaGog's logs). Since pre-1.3.2 MaGog had only three scopes: DLC (d), removed (r), and everything else (g), as soon as you have a "g" in your scope (i.e. "Regular Games"), you also get everything else (e.g. upcoming, season passes, in dev, demos).

Hint: Don't delete the version field.

Was sort of a figure of speech, the "while you're here" part.

Thanks for the info about scope (guess a simple "read the tutorial" should have sufficed, sorry) and version. The sort bit makes it sound like it actually is a bug though, since I was saying it sorts by current price, not full, and you're saying it should always sort by full. In that example link, it has New N Tasty (full price $19.99 but current price $7.99) after Stranger's Wrath ($9.99).

Sorry, typo in my answer. Should have been:
The base price sorting is always based on current price. The reason is quite simple: as far as I remember, nobody ever asked for the full price sort.

Ah, ok then. Think I stumbled into it when I wanted to confirm that there were no "classics" below $10 at anything other than the initial price points of $5.99 and $9.99, and a few that fit the release date filter were on sale then and got in between there.

Enjoy the game.

(sorry, late to the party)

This is brilliant and it has proven extremely useful to me lately as I'm writing some Python scripts that need GOG game lists as inputs, the JSON output feature of MaGOG is extremely useful :)

Just to make sure I'm a good citizen/user of MaGOG, I hope it's fine to issue MaGOG queries automatically a few times a day, the number of games returned to such queries can vary from 10 to 300.

I'd also be interested in a dump/local mirror of the database (although I guess I could get that by doing a query with no filters but didn't want to perform such a heavy query) as that may avoid having to query MaGOG as much, my scripts can live with one week old MaGOG data.

Thanks for your amazing search engine!

Don't worry. Anything below, say, a hundred queries a day is no problem. Thanks for checking.

A dump of the database is available on the MaGog home page. Look for "The current database in text format can be seen and downloaded here". It is updated every ~6 hours, so there's no point in getting it more than 4 times a day. The home page also informs you when it was last updated (e.g. " The current database was last updated about 1-2 hours ago"), or you can check the file modification time through the link.

Thanks for the kind words. MaGog will be thrilled to hear that you've enjoyed her company.

Done.

Thank you!

Hi, I apologize if this has been brought up before... I noticed that when returning the JSON data for a search the game title seems to include HTML escape sequences for special characters. For example:
[url=http://www.an-ovel.com/cgi-bin/magog.cgi?ver=760&scp=gdspi&dsp=&ord=&flt=ccs~ubisoft~&opt=nj&myf=TueSep61941212016_empty_b3OTjpPtlG9LU]http://www.an-ovel.com/cgi-bin/magog.cgi?ver=760&scp=gdspi&dsp=&ord=&flt=ccs~ubisoft~&opt=nj&myf=TueSep61941212016_empty_b3OTjpPtlG9LU[/url]

The Beyond Good & Evil title is listed as:
"title": "Beyond Good & Evil™",

The escape sequences are these described here:
https://www.w3.org/MarkUp/HTMLPlus/htmlplus_13.html

This seems incorrect. I can easily fix it on my side to replace the HTML escape sequences with the relevant UTF-8 character but I think it should be fixed on the MaGOG side becasue I don't see why MaGOG would return the game titles like that intentionally in the JSON output (in the rendered HTML output they are replaced by the browser with the right character but JSON isn't HTML).

What do you think?

The JSON output's purpose is to represent the MaGog data as closely as possible to the original. The original title in the MaGog database already contains the HTML escape sequences and therefore these are reflected in the JSON.

If you wish me to add an option to translate HTML escape sequences to JSON escape sequences, I will gladly do it, but you will have to supply me with a list of what to translate from and what to translate to. It will be optional and the default will be not to translate, so as not to disturb anyone who is already using the JSON output as is.

Do note that the list will likely be a lot longer than the few escape sequences listed in the w3.org link you supplied. See for example the title of "Devil's Dare" or the companies of "Unepic", not to mention most of the title_fr, title_de and title_ru fields, which contain tens of escape sequences.

If you need it only for a few fields (e.g. Title), the list might be significantly smaller (and more likely not to require regular updates), but I'll need to know which fields to apply it to.