Skip to main content
Settings has three sections: Casino, Mode and Players and sessions. Each one has its own Save button and saves on its own; pressing Enter in a field saves the section it is in. Owners and admins change settings. Members see them read only, under the banner Only the casino's owners and admins can change settings.

​
Casino

Your team sees the name in the dashboard. Players never see it. Saving shows Your casino's name and website are saved. A new website also updates your allowed origins and session issuer, as the first-run steps do, but only those that still match your previous website. Origins or an issuer you set by hand stay as they are, and another page on the same site, such as luckystar.example/en, changes neither. Before you save, the hint under Website says what will change, for example Saving also updates your allowed origins and session issuer to match this site. Saving then shows Saved. Your allowed origins and session issuer now match your new website.

​
Mode

Choose one of two cards:
  • Sandbox: Players bet test credits from a wallet inside your game server. Bets are recorded on Solana devnet.
  • Live: Your game server debits and credits your own wallet, with real balances.
Under the cards, Wallet URL is the address where your game server calls your wallet’s debit, credit and balance endpoints, for example https://wallet.luckystar.example/kinematic/. It is optional in sandbox, and must be an https URL if you enter one. Live needs it. Live opens once your casino is set up. Until you finish the first-run steps the card is disabled and the section says Live mode opens once your casino is set up., with a Continue setup link. To save Live:
  • Live mode accepts only https pages, so the same save changes any allowed origin that is not https. An http origin of a public site moves to https, such as http://staging.luckystar.example to https://staging.luckystar.example. Any other origin that is not https, such as localhost, an IP address or an origin with a port, is removed. Before you save, the section shows Live mode accepts only https pages, so saving also changes these allowed origins. with each origin and what it becomes, or Removed. If no origin would be left, the dashboard refuses with Live mode needs an https origin. Add the https address of a page that shows the games under Players and sessions.
  • Wallet URL must be an https URL, without a user name, a password or a # fragment. An empty field gives Live mode needs your wallet's https URL.
Saving a new mode shows Live mode is saved. (or Sandbox mode is saved.). If the save changed your allowed origins, it goes on with Your allowed origins now use https only. Once you have a game server, the message ends with Redeploy your game server to switch it., or Redeploy each game server to switch it. when you have several. Saving only the wallet URL shows Your wallet URL is saved. Each game server switches when you redeploy it on the Game server page. Until then, the section shows a banner such as One game server still runs in sandbox mode. It switches to live mode when you redeploy it., lists the game servers still in the other mode, and offers Open game server. On Game server, select Redeploy in live mode on each one. See Sandbox and live and Go live.

​
Players and sessions

This section sets which pages can open the games, and what the game server expects in a session token. When you create your casino, the dashboard fills Allowed origins and Session issuer from your website: a bare domain such as luckystar.example gives https://luckystar.example and https://www.luckystar.example, a www. host gives itself and the bare domain, and any other host gives only itself. The issuer is https:// followed by your host. Check both against your site and your session endpoint. See Session tokens. Saving shows Saved. Your game servers take the new settings within a minute. These settings need no redeploy.