In years past I was part of Remyrhe Gaming, an organisation that used to run some pretty swell tournaments for League of Legends and Hearthstone. Unfortunately RG shuttered in 20161 not long after its crowning achievement in the OCC/OUC, the largest student-focused League of Legends tournament ever run in Oceania (we held the grand final in Riot’s OPL studio!). At some point I’ll dig up the overlays and stuff I made for that and publish them here for posterity.
Newer and less popular — but nonetheless ever-growing — was our creatively named Hearthstone Cup, which our partner Logitech graciously also sponsored following our success with the OCC/OUC (hence the branding elements!). I was tasked with finding or making some stream overlays for our broadcaster(s) to use, and being dissatisfied with the overlays I was finding online, I whipped together my own.
Over the years I’ve spent a bit of time during various projects matching music tracks to onscreen events. Emotional tone is generally easy enough – putting sad music during a sad scene isn’t exactly a revelation.
What’s more difficult to get right is matching specific elements of a particular backing track with specific things happening on screen. A gunshot, an explosion, a dramatic stand off. A pause, a look, a glance, a reaction or joy, or a reaction of sorrow. Trying to match that to a beat, a strum, or chord progression – that’s where things get particularly interesting to me.
This concept is applicable near universally: games, economics, computer parts, whatever. If the category exists, the things within it are almost certain to be roughly balanced.
For “quick and dirty” comparisons between two things, this concept is incredibly valuable to understand. When you just need to know roughly whether something’s worthwhile, you can save a lot of time by keeping the deep analysis for later.
For some reason I can’t find an up-to-date command list from a single source online other than the source code itself, so I’ve patched the information together into one place, checked it against said source code, and put it here instead.