Sport and league configuration

computePowerScore doesn’t take a config argument. It looks up two exported maps at the top of every call. sportTypeConfigMap, keyed by SportType, holds how a sport plays. leagueConfigMap, keyed by LeagueId, holds how long a league’s periods run.

SportTypeConfig

One entry per SportType, exported as sportTypeConfigs (an array) and sportTypeConfigMap (keyed by id). Field meanings are in PowerScore’s TypeScript types. This table holds the six sports’ actual values.

historyWindowMs is the span of score history each sport needs to hold onto for momentum, lead changes, and comeback to work. It is at least four times the sport’s longest half-life. That margin lets a signal fully decay before it falls out of the window, no matter how often a caller polls.

LeagueConfig

One entry per LeagueId, exported as leagueConfigs (an array) and leagueConfigMap (keyed by id), plus allLeagueIds for the bare list. espnPath is the path segment ArenaSwap appends to ESPN’s scoreboard base URL. periodFormat is display text only, and doesn’t affect scoring.

31 leagues in all, matching LeagueId’s 31 members.

How a sport’s idea of “close” is set

One tuple, closenessMargins: [t1, t2, t3], decides three separate things for a sport. It picks which closeness tier a margin lands in: tight at t1, close at t2, fringe at t3, out of reach beyond it. It also picks the ceiling late-game pressure ramps toward, and the band the football red zone boost pays out at.

Basketball’s [5, 10, 18] means a 2-point game is tight and a 9-point game is close. An 18-point game is the last one that still counts as fringe. Hockey and soccer’s [1, 2, 3] treats a 2-goal game the way basketball treats a 9-point one. Changing what “close” means for a sport is changing one tuple, not three separate thresholds.

Adding a league PowerScore doesn’t ship

LeagueId is a closed union of the 31 ids above. There’s no supported way to register a new one, and nothing in the package’s public API takes a config override.

A JavaScript caller can pass a game.league outside the 31. A TypeScript caller needs a type assertion to do the same. Either way, leagueConfigMap[game.league] misses, and computePowerScore falls back to the NBA’s period count and duration, independent of sportType. An unrecognized sportType falls back separately, to basketball’s signal tuning. Both fallbacks mean the game still scores instead of throwing, just without sport-correct timing, tested directly against a made-up league id.

sportType governs most of what a signal does, regardless of league. Setting it to one of the six shipped values applies that sport’s tuning even to an unrecognized league. Period timing then either falls back to the NBA’s shape, or matches whichever shipped league has the closest regularPeriods and periodDurationSecs.

sportTypeConfigMap and leagueConfigMap are plain exported objects. computePowerScore reads them directly on every call, rather than from a cached copy taken at import time. Mutating them at runtime does change scoring behavior. Nothing in the package’s types or exports treats that as a supported extension point. A future version is not obligated to keep it working.