Game Management

Overview

The Games section lets you create and manage game configurations. A configuration is a per-operator instance of a game (Dice, Plinko, Slots, or Crash) with its own:

Basic info — name, slug, description
Game parameters — bet limits, RTP / house edge, and game-specific mechanics
Layout — the on-screen arrangement of game elements
Visual design — backgrounds, symbols, logo, fonts, colors, sounds (Dice has its own AI / manual design step)

Games List

Open Games in the sidebar. At the top, pick an operator from the Select Operator dropdown to see that operator’s configurations.

Column	Description
Game Name	Display name of the configuration
Operator	Which operator owns this configuration
Slug	Game slug used in the launch API
Type	Game type: Slots, Dice, Plinko, Crash
Status	`Draft`, `Active`, or `Archived`
Version	Configuration version (`vN`)
Created	Creation date

Use the status tabs (All / Draft / Active / Archived) to filter.

Row Actions

Action	Description
Edit	Open the game editor wizard
Preview	Launch a demo preview in an iframe (see Game Preview)
Version history	View previous versions and roll back
Global / Private toggle	(Platform admin only) make a game available to all operators or just the owner

The header Create Game button starts a new configuration.

Creating a Game

Create Game opens a multi-step wizard. The steps adapt to the game type. The footer always has Back, Save Draft, and Next (or Publish Game / Update Game on the last step).

Operator — choose which operator owns this configuration. (Skipped when editing.)
Basic Info — Game Name, URL Slug (auto-generated from the name), and an optional Description.
Configuration — first pick the Game Type (Slots / Dice / Plinko / Crash). After creation the type is locked (shown as a read-only badge) because changing it would invalidate the saved design and history. Then set the game-specific parameters — see Game Parameters.
Layout — choose how game elements are arranged on screen. Crash auto-selects its fixed Aviator-style layout (bets left, game center, chat right).
Visual Editor (Slots, Plinko, Crash) — upload assets and tune colors with a live preview. Dice replaces this with a dedicated Design step (AI Design Studio + manual token editor).
Preview & Publish — review everything, then Publish Game (or Update Game when editing).

Game Parameters

Dice

Dice is configured around a single RTP value (the roll range and bet-window limits are derived from it — see the Dice game page).

Setting	Description	Default
Game Mode	Classic (single target, over/under) or Range (two handles, inside/outside)	Range
RTP	Return-to-player, slider 80%–99%	96%
Bet Limits	Min / Max bet	Configurable

The configurator shows the Theoretical RTP, the derived House Edge, and a Derived limits panel (max/min multiplier, widest player bet, chance range) computed from maxWindow = floor(RTP × 10000) − 100. The backend re-validates this exact formula on every bet.

Plinko

Plinko currently uses the platform default configuration — there are no editable parameters in the configurator. (Rows and risk levels are chosen by the player in-game; see the Plinko game page.)

Slots

You can start from a preset (Preset Selector) and then adjust manually:

Setting	Description
Grid Size	Reels (3–7) and Rows (1–5)
Paylines	Active paylines (1–50)
Bet Limits	Min / Max bet
Free Spins	Enable + Trigger Count (2–5), Spins Awarded, Multiplier, optional retrigger + Max Retriggers
Cascade Wins	Enable + Start / Increment / Max multiplier, Reset on no win
Bonus Game	Enable + type (Pick Game / Wheel), Trigger Count, prize values + weights
Symbols	Per-symbol editor (high1–3, low1–3, wild, scatter): payouts and weights

An RTP Calculator continuously shows the theoretical RTP from your symbol weights, paylines, and features.

Crash

Setting	Description	Default
House Edge	Slider 1%–10% (RTP = 100% − house edge)	3%
Bet Limits	Min / Max bet	Configurable

Visual Editor & Assets

The Visual Editor step has a tabbed asset panel on the left and a live preview on the right. Drag an image onto the preview to set it.

Slots tabs

Tab	What you set
Background	Game background (1920×1080 recommended)
Symbols	high1–3, low1–3, wild, scatter
Buttons	spin, bet up, bet down, autoplay, menu
Logo	Game logo (PNG with transparency)
Fonts	Built-in, uploaded, or Google fonts

Crash tabs

Tab	What you set
Background	Game background
Game Object	Rocket / plane sprite (PNG with transparency)
Colors	Color scheme (Primary / Secondary / Accent / Background / Text), Multiplier Display (font size + glow color), Chat Panel (background / text / border)
Sounds	Takeoff, crash, cashout, background music
Logo	Game logo
Fonts	Built-in, uploaded, or Google fonts

Uploaded assets are stored per operator and served to players from the Beexar CDN (cdn.beexar.com).

Versioning

Each publish creates a new version. From the games list you can open Version history to review previous versions and roll back to one. The editor shows a “Version N → N+1” indicator when you edit a published configuration.

Game Visibility

Type	Visibility	Set by
Global	Available to all operators	Platform admin
Operator-specific	Only the owning operator	Organization admin

Global games appear for every operator; operator-specific games only for their owner.

Games List API

Operators can retrieve their available games via the public Gateway endpoint (no auth):

GET {GATEWAY_URL}/api/v1/operator/games?operator={slug}

The response lists each game with title, identifier (slug), category (dice/plinko/slots/crash), payout (RTP %), volatility_rating, currencies, thumbnail, and demo_available.