A route from independent studio to platform.
Engine is a development and publishing route for teams creating games for Stake. A developer builds a game, provides its frontend and mathematical game data, and submits the finished work for review. The platform's documentation describes technical and presentation requirements that must be met before publication.
For a player, the visible result is a title in a game catalogue. For a studio, the work behind that title includes the interface, assets, rules, outcome data, and testing. Bringing those pieces into agreement is an important part of development.
See the official approval guidelines.
A game has two closely connected parts.
The frontend
The frontend is the visible experience: graphics, animation, sound, controls, and game information. Engine's requirements cover matters such as mobile display, legible results, access to rules, and clear communication of game information. Visual polish needs to work together with usable controls and understandable feedback.
The maths and outcome data
The mathematical part defines and represents the outcomes the game can produce. Engine's Math SDK documentation describes generated game books and associated files used by its remote game server. These records also help developers test how the interface presents game events. The animation and the recorded result need to describe the same outcome.
A working screen is one milestone. A release-ready game also needs consistent rules and data, completed assets, and the required platform checks.
Read the official frontend requirements and Math SDK output documentation.
Review comes before release.
Engine reviews a submitted frontend and maths version for suitability. Its guidelines include originality, intellectual property, game behaviour, quality, and communication. A studio should finish and validate its submission before asking for approval; a successful local build is not a publication decision.
Distribution is also a separate choice. Current Engine documentation describes a Stake-only option and a Stake-plus-network option. The choice is made at first submission and locked at launch. Individual network operators decide which games to accept, so an offered game may not appear on every operator.
Those decisions are part of releasing a specific game. A studio website can introduce a project earlier, provided that the stage of development is clear.
Official references: approval and distribution.
Our first project: Oni Dojo.
EveGames is developing Oni Dojo, a slot with a martial-arts fantasy theme and an adult oni warrior concept. We have established a local pipeline using the official example software. The original art, final game data, and platform integration are still being developed and checked.
We will share selected milestones here as the game becomes its own finished experience. Our Oni Dojo page is the place for its current status; our journal follows the creative work behind it.
About this guide
Written by EveGames using the linked Engine documentation, checked October 9, 2026. Requirements and distribution options can change; refer to current platform documentation when preparing a submission.