How we test

The register

The register of 54 knights is built from the data each workshop published: title, studio, release date, RTP and volatility. It is not built from storefront lists, because a storefront tells you what one site carries today, not what exists. When a figure was never published, the entry carries «—» and stays that way until the workshop publishes one.

Slots

1. A session, not a glanceLong enough to reach the feature at least once. A page about a slot whose bonus we have not seen is not finished, and we would rather publish late than pretend.
2. Figures from the workshopPublished RTP and volatility, checked against the game's own info panel, because many titles ship in several certified settings.
3. Our own screensScreenshots come from our session. Where a paytable or a bonus round has not been captured yet, the page says so plainly instead of borrowing one.
4. Notes lastWritten after the session, with the volatility said out loud.

RTP settings

1. The default figureWe print the RTP the workshop published as the default for the title.
2. Lower settingsWhere the workshop lists more than one certified setting, the page says so, because the version you load may not run the default.
3. Check before you playThe game's own info panel shows the setting in force. That number beats anything printed here.

What we do about gaps

We leave them visible. An empty field, a «—», a sentence saying the round has not been reached yet: all of these are better than a plausible invention, because a plausible invention is the one thing a reader cannot check.

Money

Partner links earn a commission on sign-ups. They are marked rel="nofollow sponsored" and they are the only way this site earns. Nothing in the register is for sale — not a position, not a score, not a sentence.

Who does what

Callum Rees runs the sessions and writes the slot pages. Marnie Coulthard writes the chronicles and the guides. Separating the two keeps the data pages and the dated chronicles in different hands.