Built to bechecked.
Bassline Mars is submitted, with BAAL and Strings of Fortune in production behind it on the same engine and the same maths pipeline. What an integration team and a commercial team each need is below: the numbers as they were submitted, the client specification, what we supply at launch and what we ask for in return.
One build, one contract, nothing bespoke.
Integration is where a studio relationship quietly becomes expensive, and most of that cost is not difficulty — it is bespoke work. A native wrapper. A wallet nobody asked for. An adapter built for one platform and maintained for a decade. We do not have those parts, so there is nothing for you to absorb.
- 01
One build, every screen
The game is a single WebGL build. It runs portrait and landscape out of that one build, on desktop and mobile browsers, with no native app, no store submission and no second binary drifting out of sync with the first. What you sign off on a laptop is what a player gets on a phone.
- 02
A server contract you already have
Integration is RGS-agnostic and speaks a standard remote game server exchange: session, wager, outcome, settlement. We do not ship a wallet of our own, a session service of our own, or an adapter written against one operator and maintained forever. Where your platform differs, the difference belongs in configuration.
- 03
Outcome first, presentation second
The round is resolved before a single frame of it plays. The presentation layer reads that outcome; it cannot produce one. That decoupling is why a replay is the round rather than a re-run of it, and why a disputed spin ends in a record instead of an argument.
- 04
Demo mode as standard
Every title ships with a fun-play mode on the same build and the same weights as the real-money client, for lobby previews, affiliate placements and markets that require a play-for-free route. It is the game, not a lookalike of it.
Every figure here is a figure we submitted.
The model was simulated across hundreds of millions of rounds and optimised against the constraints a test house actually measures: return, volatility, hit rate, and whether the maximum win is reachable at all in each mode. Where something is not settled, the table prints an em dash rather than a promise.
Restricted-word routing, jurisdictional copy variants and social-casino labelling are compiled into the client rather than bolted on at submission. So are the rules: per-mode return, maximum win and buy cost are printed in the game itself, where a player can read them without leaving the round.
- Return to player
- 96.50%
- Variance between modes
- Within 0.5%
- Maximum win
- 25,000×
- Max win reachable
- Every mode
- Round model
- Stateless, independent
- Gamble feature
- None
- Bonus continuation
- None
- Early cashout
- None
- Restricted-word routing
- Built in
- Social-casino labelling
- Built in
- In-game rules
- Per-mode RTP, max win, cost
- Independent test house
- —
- Certified markets
- —
Figures as submitted for Bassline Mars. Every title in the catalogue is built against the same constraints; each one is certified on its own.
The client, in one page.
These values describe the shipping client, not a target we intend to reach. Anything not yet measured on the delivered build is left blank — an estimate dressed as a specification is the kind of thing an operator finds out about in week three.
Client
- Renderer
- WebGL
- Frame target
- 60 fps
- Browsers
- Desktop and mobile
- Native app
- Not required
- Orientation
- Portrait and landscape
- Aspect handling
- Reflowed, never letterboxed
- Audio
- Streamed, unlocked on first input
- Animation
- Skeletal · Spine
Delivery
- Server contract
- RGS-agnostic
- Demo mode
- Included
- Round replay
- Exact, from the record
- Localisation
- External string tables
- Languages at launch
- —
- Asset delivery
- Pre-encoded WebP
- Delivered bundle size
- —
Short windows, written down.
- 01
Exclusivity
Defined windows only: a named period, a named territory, agreed before launch and expiring on the date it says. We do not write open-ended lockups, and we do not quietly extend one because a title performed.
- 02
Launch support
A launch is a date, a build and a set of assets. We stay on the integration through certification, launch week and the first full reporting cycle after it — long enough to fix what a live lobby finds, short enough that the next title still gets built.
- 03
Marketing assets
Key art, wordmark, monogram, a feature card for each bonus round, and cut-downs sized for lobby tiles, promotional pages and social. Delivered at master resolution with the transparent cut-outs intact, so your team can re-crop without asking us for anything.
The art in the Vault is the art you receive. There is no reduced partner pack: those 25 pieces run to 235.1 MB as original renders, and the originals are what arrive — not the compressed tiers this website serves.
The six we are asked first.
Answered here so the first call can start further in. Where the answer is no, it says no.
01How long does integration take?
We will not quote a number that depends on your platform rather than ours. What we can tell you is what we do not add to it: no native build, no wallet of our own, no adapter written per operator. The client is a URL and a session. The rest is work your team has already done for another studio, in the same order.
02Can we run a lower RTP variant?
No. There is one model per title, at 96.50%, with every mode inside half a point of it. A catalogue carrying four return variants is four maths models and, in practice, one that was properly tested. If a market you need requires a different return, that is a fresh submission, and we will tell you what it costs in time before you ask for it.
03Can bonus buys be switched off per market?
Yes, from configuration — the build does not change when a mode is disabled, so nothing about the certified client is invalidated by turning one off. Cost, return and maximum win for every purchasable mode are printed in the game’s own rules screen, which means a player sees the same figures the regulator was given.
04What happens when a player disputes a round?
The round is replayed from its record rather than re-simulated. Because presentation is decoupled from outcome, that replay is the round — same result, same order of events — instead of a convincing approximation of it. Audit is the reason the decoupling exists; the animation quality is a side effect.
05Which markets are you live in?
None. Bassline Mars is submitted and waiting on a lobby date, and a lobby date is an operator’s decision rather than ours. Until a title is live somewhere we will not print a market or a test house on a website — which is why those two rows of the compliance table above are blank. Ask, and you get the position on the day you ask, including the parts still outstanding.
06What do you need from us to start?
A technical contact, your remote game server documentation, and the markets you intend to launch in. That is enough for both sides to establish whether this is a fit before either spends a fortnight finding out the slow way.
Two addresses. No form.
Mail is answered in the order it arrives. Name the title, the market and the platform in the first message and the second one can be about terms.
Business · Integration and commercials
partners@royalacegroup.comIntegration, certification questions, exclusivity, launch dates. Answered at the same level of detail as the tables above.
Press · Assets and interviews
press@royalacegroup.comKey art at full resolution, wordmarks, feature cards and copy that has been checked. Deadlines are treated as deadlines.
Include
The title, the markets, the launch window and the platform you run on.
You get back
The submission pack, the integration specification and the asset manifest.
You do not get
A deck. One exists on request. It says less than this page does.