Skip to content
SloticaRequest access
STAKE ENGINE EXPORT / SDK OUTPUT

Built for Stake Engine
from the first line.

Stake Engine games are two things: a front end that renders the outcome and a math package that decides it. Slotica generates both with the Stake Engine SDK toolchain: the front end builds inside the web SDK, and the math package comes out of the math SDK’s own simulations and optimizer.

AI-assisted creation. Your creative control.
A cat creative director packs a glowing miniature game world into an engineered shipping crate on a workbench
Original Slotica concept artwork · AI-generated illustration
SvelteKit + PixiJSThe Stake Engine web SDK stack
Math SDK toolchainPython sims + Rust optimizer
Publish setBooks, lookup table, index, config
INSIDE / STAKE ENGINE EXPORT

The same shape as the Stake Engine reference games.

Stake Engine ships reference games (lines, cluster, scatter) as the target specification. Slotica’s generated code follows those patterns instead of inventing its own, which is what makes an export possible at all.

01

Front end in the web SDK stack

Slotica generates the TypeScript types, book-event and emitter-event definitions, the game context, the Svelte components, and the asset manifests in the structure the Stake Engine web SDK uses.

02

Math that Stake Engine can run

Your game is turned into a real Stake math SDK game folder, simulated with the SDK’s Python framework, and tuned to your target RTP by its Rust optimizer. The output is the publish set Stake’s admin panel accepts: compressed books, the weighted lookup table, index and config files with their hashes.

03

Books and events, not screenshots

Every spin is an outcome book with the events the front end replays: reveals, wins, feature triggers, bonus rounds. That is how Stake Engine separates fairness from presentation, and it is how Slotica structures a game from the start.

Actual studio capture · Feature Builder logic exported as code

Actual studio capture · Feature Builder logic exported as code

Slotica Feature Builder: visual game logic that compiles to Stake Engine style TypeScript and Python
FROM IDEA TO ITERATION

A workflow you can make your own.

  1. 01

    Design

    Create the game with Pit Boss or by hand: art, mechanics, bonuses, UI, sound.

  2. 02

    Tune

    Set target RTP and volatility, generate reel strips and the paytable, simulate up to a million spins, auto-balance toward the target.

  3. 03

    Export

    Download the front end from the Export workspace and generate the math package with the certify step. Both are in the Stake Engine SDK format; bundling them into one submission is next.

MADE WITH SLOTICA

What the Export workspace produces today.

The Export page downloads a complete SvelteKit game: the app shell, the generated config, event handlers, Svelte components and asset manifests, plus Storybook stories and mock books. It builds inside the Stake Engine web SDK workspace to a single-file game. The Code viewer shows every generated file before you download.

Actual studio capture · the game that the export packages

Actual studio capture · the game that the export packages

A Slotica game running in the Testing workspace before export
GOOD QUESTIONS

A closer look at
Stake Engine export.

What is Stake Engine?

Stake Engine is Stake’s platform and SDK for third-party game studios. A game is delivered as a web front end built on its web SDK and a math package that produces outcome books; Stake Engine runs the math and serves the outcomes to the front end.

Does Slotica export a finished Stake Engine game today?

In two parts. The Export workspace downloads a SvelteKit game that builds inside the Stake Engine web SDK, and the certify step produces the math publish set (books, lookup table, index and config). Combining them into one submission is the next step.

Which game types follow the Stake Engine patterns?

Line, ways, cluster, and scatter games follow the Stake Engine reference implementations. Free spins, sticky wilds, multipliers, and Hold & Spin are expressed as book events the front end replays.

Do I need to know the SDK to use this?

No. You design the game; Slotica generates the code in the SDK’s structure. Developers who want to read or extend the output can open every file in the Code viewer.

Will Slotica submit my game to Stake?

No. Listing on Stake Engine is between you and Stake, including their review and certification. Slotica prepares the package.

YOUR NEXT WORLD STARTS HERE

What will you make possible?

Bring an idea, a creative team, or a whole portfolio. Let’s find the right starting point.

For creators, studios, and operators · Access is by request