Good job! Since MaGog is in legacy mode now hope you consider adding its features to GOG Database.

Oh, hadn't noticed this until now. Definitely handy, and needed, with MaGOG in legacy mode. Far from a replacement though (not at all now in what matters to me most, regional pricing, but I see that will be implemented), unless MaGOG's complex search will also be added, but definitely welcome!
(At the same time, considering why mrkgnao left and the reasoning behind putting MaGOG in legacy mode, maybe not?)

I may have asked you this before, but have you by any chance found a way to detect product entries which are part of a bundle, like for example "The Humans Bundle" released today, which I assume has 3 separate product "game" type entries it links to?

We had a bit of a discussion about it, but I think the best we can come up with relies on API links that require you to be logged in (and own the game).
If you can get the right response it's just a matter of comparing the store links for games and any with matching links must be a bundle, but that data is only available for owned games...

Yeah, true, that's one way we know of... and there's also my suicidal way of exhaustively scanning (almost) the entire product id range to detect anything you've missed. Both of them are a lot less than ideal. Somehow I was hoping for a breakthrough from Yepoleb now that he's got the GOG Database wizardry going in full swing :).

Well, that would find the IDs presumably but wouldn't tell you that they were part of a bundle (or which bundle)

... and I'm ok with that. To be honest I'm only looking for a way of getting the product ids which are hidden behind bundles (discarding any relationship between the two) which doesn't involve an authenticated session and owning the games/bundle, doing any obscure shopping cart validation tricks or having to scan the entire product id range again (for the 4th time in my case).

*Sigh* Yeah, guess I'll have to prepare myself for a 4th voyage on the product API oceans. Who knows what other things have shown up behind our backs anyway - might as well have another look. I bet Johny will be happy :).

Someone drew my attention to this.

Here is how I did it:
1) My primary source was this: [url=http://www.gogwiki.com/wiki/User:Barry_Woodward]http://www.gogwiki.com/wiki/User:Barry_Woodward[/url]
This is the GOG wiki page for Barry_Woodward's library (i.e. unbundled). If you look at the source of the page, each box has an ID (courtesy of Barefoot_Monkey), the unbundled library ID, which is what you're looking for. Barry_Woodward buys practically all GOG games upon release, so his library is as close as it comes to the entire GOG library. The only drawback is that he updates his wiki page only about once a month or so. If you're in a hurry, you can PM him to ask him to update it (I never did, as I'm the shy type).

2) An alternative source was this: [url=http://www.gogwiki.com/wiki/Special:GogExtensionData]http://www.gogwiki.com/wiki/Special:GogExtensionData[/url]
This is a page that Barefoot_Monkey set up primarily for MaGog, I believe, in which he collects all the IDs ever seen by Barefoot Essentials (when people use it to upload their library or wishlist to the wiki). It's a mix of catalogue and library ids in no particular order, so one just searches through it to see what's available. However, since it depends on people uploading to the wiki, which --- excepting Barry_Woodward --- less and less people do (and even if they do, they don't necessarily have the newest games), it's not much more useful that the first option.

Hope this helps.

It does indeed. Thanks a lot mrkgnao!

I'm generally in no hurry, so writing an id scraper for Barry_Woodward's library is still a lot better than having to go through weeks worth of exhaustive id scans.

you could put a json file containing all unresolved pack ids on a github account ( or Yepoleb's server).
Then add some code to Barefoot Essentials/Adalia Fundamentals to fetch that file and compare against the list of owned ids. If a match is found, display a notice to the user that their help is required and direct them to this thread :)

If finding the matching bundle ids with that method you mention works easy enough in js, that could be added to the script as well. Otherwise you'd just need an easy way for the user to retrieve the id from a game on his account shelf and figure out the rest manually.
Comparing the store links wouldn't work when part of the bundle is available separately in the store (ie all those "Deluxe Editions").

The only problem with that is that we don't know the IDs, and would need to compare against game titles or something (which we wouldn't know exactly either).

I could scan everyone who uses the scripts libraries against the total database of known IDs and report the new ones which could then be retrieved from the API to get info, but it would put a lot of extra strain on the users end for very little gain.. particularly as I do basically already do that for the Legacy covers, though not quite in that way.

preparing that json file with all the unresolved IDs shouldn't be too hard. Just get all store ids, filter out the 'game packs' and cross referense with magog to get the ones without information.
i'll try and see if I can get this done

would this help: unresolved.json ?