gogtrial34987: I'm swamped the next few days, so it might take me until Thursday before I can correctly handle these.
I managed to find a spot of time today, and made quite some progress toward this. I'm reasonably pleased with the way I've set up most of the relevant code here, as for the most part, adding this new type was a breeze. (Though preemptively handling future repacking shenanigans remains complex.) If I manage to scrounge together some more time tomorrow as well, and no troublesome edgecases pop up, I should be able to release it ahead of schedule.
mrkgnao: P.S. The name mod is very confusing. These are NOT mods, but rather modded standalone games.
FWIW, I'm (probably) using the phrase "modded game" for the filters, but sadly had to opt for "mod" for the grouped view, as "modded game" wouldn't fit on one line there.
Cavalary: It seems fair to me to treat them as expansions as long as they require owning the game to get. Even more so when gogtrial34987 said gamesieve isn't meant as a GOG database explorer but a tool for those looking for GOG games to buy, so it looks at things from the perspective of making a purchase.
And total conversions are mods, after all.
You can get Soul Harvest on its own. You can't get Archolos on its own.
mrkgnao: Fair enough. The buying restriction makes sense, even though gamesieve --- understandably --- does not adhere to it religiously (e.g. Obduction Soundtrack).
Indeed. If it's buyable standalone, it'll mostly be a game, but can be a demo/expansion/goodie/bundle depending on circumstances. If it
isn't buyable standalone, it'll
always be a "dependent product".
mrkgnao: P.S. Would appreciate a cookie treatment (i.e. remember setting across sessions) for group=false, especially now that one can have owned game colouring.
Heh, I'd
just removed that idea from the roadmap, as I didn't expect anyone to want it anymore now that I have the grouped product filter. I'll add it back on, but this won't be as trivial / swift to implement as the nsfw tag. I'm trying to avoid managing state/having a session, so I'll treat each URL as standalone. If you have a preference for group=false, I can auto-apply it when it's missing (and remove the preference when you click on the group: yes toggle) - but what should happen if the URL you request has a filter which doesn't work when grouping is toggled off? And is this auto-applying behaviour actually what you want in all cases? E.g. if you follow a link from here, which will mostly assume the grouped view? (I'm facing the same issue with the country preference and price filters.)
I might have to explicitly add the default state for these preferences to the URL as well, but I worked really hard for clean URLs with good defaults, so that's not a step I'm willing to take lightly.
It might be more effective to update the userscript to separately highlight owned grouped products (they each have an id listed in the HTML as well, so doing so should be semi-trivial).