LoR_DDragon VS steamdb

3. Keeping track of what games I've played and how I felt about them. I do a big writeup of "my best media of the year" and it's hard to keep track of what I play.

Data wise, I also center everything on the IGDB ID, which gives me a lot of basic metadata. I also store Steam ID if available, because that's a more common foreign key. I've got a custom React extension that handles adding and fetching data. I've got tables for Games, Purchases, and Playthroughs, plus support for replay reasons and genre selection.

I recently did a big migration to add HLTB data, which I sure __thought__ was going to be simple and ended up being a big pain. I'm going to do a writeup for it once I find the time, because it did end up being interesting.

In terms of existing data, I found https://github.com/leinstay/steamdb very useful for collating information (though I had to shrink it a bit with `jq`- those are some pretty hefty JSON documents.

Here's my completed games list: https://airtable.com/shrJvjcnh0psf3ha6/tblF5D5k2qMuzrao8

I've got similar setups for books, movies, and TV shows. They're all linked on my site: https://xavd.id/#my-media-lists

I totally agree this is overkill for most people, but I've also found it super successful for increasing my enjoyment of videogames in an odd way. A bit part of that recently was recategorizing games from a 1-4 scale of interest level to a more human scale of "Play Next", "Play Soon", "Want to Play", "Play Eventually", "Would Like to Play", and "Won't Play". This lets me functionally hide games that I really don't intend to play (especially ones I just added to accounts for free). Narrowing my "Play Next" list down to about 15 games and restricting "Now Playing" to ~ 1 / platform __greatly__ reduces the cognitive overhead of a "backlog" and turns them into "a fun buffet of things I can do".

This is the first link that came up when I simply Google'd this...