How we review games

Sources, uncertainty and the difference between a published claim and a tested result.

Start with the developer

The first source for a game’s name, provider, product features and published specifications is the developer’s product page or rules. Each review includes the sources used and a research date. If a range of settings is published, we keep the range and tell you to check the version you actually open.

Search results, affiliate landing pages and downloaded competitor sites can reveal useful questions and page structures. They do not establish an RTP, a licence, a release date or a withdrawal guarantee. Those claims need a source that can support the specific statement.

Three different kinds of information

  • Published fact: the developer or a named primary source states it. A source link appears alongside the reference material.
  • Editorial explanation: we explain a rule or a practical distinction in our own words. An illustrative calculation is not a prediction of your result.
  • Unverified: an interactive session, regional availability or operator condition has not been checked. An external link alone does not count as a gameplay test.

Why there are no invented scores

We do not assign a star rating merely because a page needs one. A meaningful score needs stated criteria and observed evidence. This edition uses mechanics, published specifications, demo status and clear limitations so you can compare the things that are actually known.

How an update is handled

When a provider changes its rules, the game record and the related guides need to be reviewed together. A research date means that the sources were checked on that date; it does not mean that every possible operator version was tested. A material correction should identify the changed claim and the new source.