it’s been about a year since this feature was released and i have to say its a great update. I find myself marking releases more than I initially realized I might due to sorting older games that had a myriad of ports (this is due to mirroring my shelving in tandem with Launchbox). often I will specifically want to mark ONE specific release/platform. On occasion with older games the database will have either a platform or a release (one or the other) so having two options to mark is good. Also, this site is great with how it is designed and I feel my shelves scales well as a large collection.
There is one bug though i did notice recently… (It’s of minor consquence but I’ll mention it)
Example: I played maybe 20 games for the Sega Genesis but hundreds for the SNES. I however have ‘skipped’ and ‘abandoned’ a lot of games for genesis. BUT since those games DO have releases on Genesis, and I have in fact ‘played’ the underlying game (but not the specific releases) Grouvee will return lots of results for Genesis on a search for Genesis Played. This happens if one simply marks the platform (for any reason) and it is on the played shelf (for any release)
A short version of it is grouvee isnt making a displayable distinction between release data a user has marked and the game page when doing a search, and it doesnt seem to matter how you go about ticking release data, because once you tick a platform its going to show up on any shelf the game has a tick for. I imagine very few people would even notice this.
The end results is that if I go to a game page’s releases page and then mark three individual releases as ‘Wishlist’, another as ‘Played’ and another as ‘Abandoned’ (custom shelf) and then do a search for anything on ‘Wishlist’ and filter results only for ONE platform, i will still see stuff from Played and Abandoned that are not supposed to show up. This is a little unfortunate because now I cannot truly tell you how many of X platform games I have actually ‘played’ in my very large collection of games.
I can’t really think of a solution or suggestion to this. I dont necessarily wish to unmark other platforms. Grouvee doesnt let me filter down results in a way to display with distinction. And even if it could that could be a bit complicated. Grouvee cant be ‘forced’ to look for releases played obviously. (since most users dont even mark them, and those that do arent going to mark every one)
Are there any conditions that need to be met for a game before releases are synced from giantbomb? I recently noticed that a couple of games don’t have any releases, even though they do on their respective giantbomb pages, like the two below
Mass Effect Andromeda
Subnautica
Edit:
Now after seeing the entries side by side I notice that the descriptions of the games are different as well. Maybe everything is working fine and the examples above are just different entries (based on their ID) for some reason like merging duplicates?
The descriptions and most of the box arts are being updated on Grouvee now and then to offer more information for the users (I, for example, changed that for Subnautica). That’s why you probably see it different in the present. There are times when the original doesn’t show a clear box art or a somewhat complex description so it has to be edited. Usually with the information from the official Steam page.
That’s good to know, thanks a lot for clearing that up! If an entry on grouvee is edited manually, I imagine there is some kind of protection in place to prevent local information being overwritten with external data the next time the data source, in this case giantbomb, changes.
Would this mean that any locally edited entry is effectively de-coupled from its related entry in the data source, or does it work fine grained per field?
The reason why I’m asking is because I’m trying to figure out if there is anything I (or any other member of the community) can do to get the missing release data copied from giantbomb to grouvee.
Well, that and plain curiosity.
Correct. There is protection in place to keep my import scripts from overwriting any locally edited data. The issue is that it’s not very granular. Once anything besides the box art has been edited, I set a flag that tells my import scripts to ignore Giant Bomb data, including release data. It’s kind of an oversight like @aqwelorr says. There’s really no need to ignore the release data ever right now. I’ll work on getting that fixed.
@GigaDeathNullGolem, I’m not ignoring this comment. I need to take the time to process what you wrote, and put some kind of plan into action. You use this site in more interesting ways than I could have imagined a lot of the time, and I want to try and make it easier for you.