<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: iGaming Tools</title>
    <description>The latest articles on DEV Community by iGaming Tools (@igamingtools).</description>
    <link>https://dev.to/igamingtools</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4251797%2F83b87965-92c1-428a-9391-4027ba98bea1.png</url>
      <title>DEV Community: iGaming Tools</title>
      <link>https://dev.to/igamingtools</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/igamingtools"/>
    <language>en</language>
    <item>
      <title>Almost half of 1,333 online slots ship more than one RTP. Here's the open dataset</title>
      <dc:creator>iGaming Tools</dc:creator>
      <pubDate>Wed, 18 Nov 2026 11:46:34 +0000</pubDate>
      <link>https://dev.to/igamingtools/almost-half-of-1333-online-slots-ship-more-than-one-rtp-heres-the-open-dataset-24a6</link>
      <guid>https://dev.to/igamingtools/almost-half-of-1333-online-slots-ship-more-than-one-rtp-heres-the-open-dataset-24a6</guid>
      <description>&lt;p&gt;Ask "what's the RTP of this slot?" and you usually get one number, copied from a press release.&lt;br&gt;
We capture every game from its official demo, and the paytable tells a different story: &lt;strong&gt;618 of&lt;br&gt;
1,333 games (46%) ship with more than one RTP configuration.&lt;/strong&gt; Each one has a condition attached,&lt;br&gt;
and the condition is printed right there in the game's own rules screen.&lt;/p&gt;

&lt;p&gt;We just published the whole thing as an open dataset (CC BY 4.0): 1,333 games from 9 studios,&lt;br&gt;
with RTP variants, bonus buy prices, themes and features as taxonomies, provider licences and&lt;br&gt;
about 8,600 accessibility notes. This post is about what's in it and how it's captured.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the data is captured
&lt;/h2&gt;

&lt;p&gt;A slot demo is a canvas application: there's no DOM to parse, the paytable is drawn inside a&lt;br&gt;
WebGL or Canvas2D context, and &lt;code&gt;page.content()&lt;/code&gt; gives you an empty shell. So every game is opened&lt;br&gt;
in its official provider demo in a headless browser, the rules, paytable and settings screens are&lt;br&gt;
captured, and the values are read and verified with OCR.&lt;/p&gt;

&lt;p&gt;Every record says how and when it was captured (&lt;code&gt;capture_method&lt;/code&gt;, &lt;code&gt;captured_at&lt;/code&gt;). And every record&lt;br&gt;
says what we could &lt;strong&gt;not&lt;/strong&gt; capture: the &lt;code&gt;coverage_gaps&lt;/code&gt; table has a row per missing item. In this&lt;br&gt;
release that's 5,762 gaps next to 2,502 explicitly confirmed items. A blank is a blank, not a guess.&lt;br&gt;
That distinction ("this game has no bonus buy" vs "we failed to read whether it does") is the part&lt;br&gt;
most datasets skip, and the part that makes this one usable.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's interesting in the numbers
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Most extra RTPs are per feature, not per operator.&lt;/strong&gt; Across all 2,656 RTP rows: 1,353 are a game's&lt;br&gt;
default, 824 belong to a bonus buy, 286 to an ante bet, 98 are operator configurations, 50 depend on&lt;br&gt;
the player's own settings, and 45 on a feature. So when a game "has several RTPs", it's usually&lt;br&gt;
because buying the bonus or switching on the ante bet plays at a different return, not because the&lt;br&gt;
casino picked a worse version.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;One game, thirteen rows.&lt;/strong&gt; &lt;em&gt;The Big Dog House&lt;/em&gt; lists 13 RTP rows: 96.43% for one bonus buy,&lt;br&gt;
96.51% for an ante bet, 96.53% default, and so on. Small differences, but they're different numbers&lt;br&gt;
and each one is real.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Rounding can cost more than the configuration.&lt;/strong&gt; Some crash games are fine at a normal bet and not&lt;br&gt;
at the minimum one. &lt;em&gt;Crash X&lt;/em&gt; plays at 95.99% at a bet of 1.0 and "drops to 88.07% when betting 0.1:&lt;br&gt;
wins are rounded down", to quote its own rules. That's 8 points, from rounding alone.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Accessibility is mostly about colour.&lt;/strong&gt; The ~8,600 accessibility notes split into colour-blind&lt;br&gt;
(3,674), motor (1,347), screen reader (1,250), hearing (1,226) and low vision (1,163). A typical&lt;br&gt;
note: "No gameplay-critical information is conveyed by sound alone; all wins, triggers and jackpot&lt;br&gt;
hits are also shown as on-screen text and numbers." I haven't found this kind of per-game review&lt;br&gt;
anywhere else.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's in the dataset
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;table&lt;/th&gt;
&lt;th&gt;one row per&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;slots&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;game: maths, grid, mechanics, themes, features, bonus economics, capture date&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;rtp_variants&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;RTP configuration, with its condition&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;bonus_buys&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;bonus buy option and its cost in bets&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;accessibility&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;accessibility note per game and group&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;coverage_gaps&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;captured / not captured item&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;providers&lt;/code&gt;, &lt;code&gt;licences&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;studio profile; licences with regulator and number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;themes&lt;/code&gt;, &lt;code&gt;features&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;taxonomy with aliases (&lt;code&gt;aztec&lt;/code&gt; also catches maya, inca)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;CSV and Parquet, refreshed monthly. Honest limits: 9 studios is not many. If you need RTP and&lt;br&gt;
volatility for thousands of games, there are bigger open slot databases; this one is narrower&lt;br&gt;
and deeper. Not included: screenshots, symbol art and game texts, which belong to the providers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Getting it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;GitHub: &lt;a href="https://github.com/igamingtools/igaming-slot-specs" rel="noopener noreferrer"&gt;https://github.com/igamingtools/igaming-slot-specs&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Hugging Face: &lt;code&gt;load_dataset("iGaming/igaming-slot-specs", "slots")&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Kaggle, and Zenodo with a DOI: &lt;a href="https://doi.org/10.5281/zenodo.24331735" rel="noopener noreferrer"&gt;10.5281/zenodo.24331735&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The data comes out of &lt;a href="https://i-gaming.tools/" rel="noopener noreferrer"&gt;iGaming Tools&lt;/a&gt;, a data API about the industry. It&lt;br&gt;
does not run games or take bets. If you'd rather query it live, there's a free MCP server at&lt;br&gt;
&lt;code&gt;https://mcp.i-gaming.tools/mcp&lt;/code&gt; (no key, no sign-up) and a REST API with a free tier.&lt;/p&gt;

&lt;p&gt;If you work with capture-and-verify data in another field, I'd like to hear how you handle coverage&lt;br&gt;
accounting, i.e. telling "absent" apart from "not captured". That's the part I've seen the fewest&lt;br&gt;
good answers to.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;This article was written with the help of AI and checked by a person against the dataset before&lt;br&gt;
publishing: every number above comes from the published CSVs.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>opendata</category>
      <category>dataset</category>
      <category>ocr</category>
      <category>mcp</category>
    </item>
  </channel>
</rss>
