Here’s a weird one I had a half-baked idea for: Tower Defense Metroidvania. The idea is that your an acolyte of a temple (or a mechanic in a space station, whatever), and there’s an armed group trying to force their way past the temple’s traps and defenses to get to the heart of the temple and steal the macguffin; that’s going on in a little horizontal track at the top of the screen, and meanwhile the rest of the screen is Metroidvania gameplay as you navigate the interior of the temple (or space station) to activate defenses, acquire magical relics, and eventually awaken the temple’s guardian spirit. You lose if the bad guys get to the heart of the temple, you win when you successfully gather everything you need to awaken the guardian. In the meantime, you have to decide when and where to spend resources (including time) shoring up the “normal” defenses (that delay the attackers) and when you need to just push onward to awaken the guardian.
I’m always keen to shit on Google, but, this is about “having search terms in the query string” and “having links that take you directly to the thing you clicked on without any redirect dance to obfuscate the Referer header”. With all the other shit to legitimately complain about from Google, this seems so silly to focus on. Google isn’t even the one that sent the Referer header, that would be your browser (which, Chrome didn’t exist yet at the time). RFC1945, from 1996, for HTTP 1.0, even explicitly stated that any application that communicates over HTTP (i.e. a web browser) should offer the user a configuration option to disable sending Referer headers.
Edit: slight clarification, Chrome did exist during part of the time period that the lawsuit covers, though it only started to pick up serious market share towards the end of the relevant time period.