Same Slot, New Name: How We Link Reskinned Games So the Stats Carry Over
Published 2026-09-27 · Tags: data, slots
Studios rename and reskin games constantly. We fingerprint published outcome tables and link byte-identical math, so history follows the game, not the title.
Made-up example, real pattern: a slot called "Dragon's Hoard" lands on Stake Engine in spring. In June it becomes "Dragon's Hoard Deluxe" with new art and the same math. In August the studio renames it again. Three catalog entries, one game. If you don't handle that, the tracker shows three slots with a third of the history each and the Slot Cruncher page for the current name says "no data" for the months before it existed.
This is a small post about an unglamorous problem that we quietly fixed a while ago and get asked about every few weeks.
Why it happens
Stake Engine studios can republish a game under a new name or a new skin. Sometimes it's a rebrand. Sometimes it's a "2" that's really a 1.1. Sometimes a game gets pulled and relaunched to reset its position in the lobby. From the catalog's point of view each of those is a new game with a new slug and a new ID.
From a player's point of view it's the same reels, and the stats should follow it.
How we link them
Every Stake Engine mode has a published outcome table, and that table is a fingerprint. Two "different" games whose modes have byte-identical tables (same outcomes, same weights, same RTP to the last decimal) are the same math wearing different clothes. We hash the tables and when a new catalog entry's modes match an existing game's modes exactly, we link them.
Linked games share history in the Engine Tracker: turnover, bet counts and player counts carry over, with the rename visible as a marker on the chart. In Slot Cruncher the current name is canonical and the old names appear as "also known as", so searching either finds it.
What doesn't get linked
Same name, different math. A real sequel with a changed table is a new game and gets a fresh history, even if it's called "Thing 2". Linking by name would be wrong here and we don't do it.
Partial matches. If a studio ships a sequel that reuses three of five modes unchanged, the game is new; the three shared modes are noted but the histories stay separate. Merging would misattribute the new modes' performance to the old game.
Non-Engine slots. Pragmatic, Hacksaw and the rest don't publish tables, so we can't fingerprint them. For those, renames are handled by hand when someone tells us, and the casino tracker treats a rename as a new game until then.
Why bother
Because the tracker's value is history. A game's 30-day turnover trend, its peak-player curve, whether its live RTP has drifted from the published number: all of that needs continuity, and a rename shouldn't reset it to zero. Stats that quietly restart every time a studio changes a title would be stats you couldn't trust.
If you see two entries that you're sure are the same game and we haven't linked them, send both names. It usually means a mode changed slightly and we'd like to know which.