Answers for your first build, your next launch, and everything after.
29 questions
UniPlays is where browser games and their tokens live together. Players find a game, play it, and trade its token on the same game page.
You build the game, add features with the SDK, test it, and launch it. Start from a template, your own browser game, or an AI coding agent.
No. The SDK covers saves, scores, player identity and token features, so you write no smart contracts. Start with a template, bring your own code, or work with an AI coding agent.
An agent can build and check your game. You still test the gameplay and review the result before launch.
No. Your game runs in the browser, so movement, controls and other gameplay need no transaction. The blockchain is used for your token launch, token trades and supported item transactions.
Use it where it adds something to your game. If a result must be trustworthy, such as a competitive score, use a backend that checks the player and the action.
No. Players can start as guests without signing in. A game can require a token for particular features, but basic guest play never needs a wallet.
Guest saves belong to that guest and expire after 30 days. Signed-in accounts keep their saves across devices.
You need a wallet to launch a game or trade tokens. Players need one for actions that use it, such as sharing their wallet address or checking their token balance.
Token checks such as token.gate return false without a wallet. Keep guest gameplay working wherever a feature does not need one.
Yes. Bring a browser game or a web export that does not use multiple threads. Phaser, Pixi, Three.js, Godot, Unity, PlayCanvas, Construct, and vanilla JavaScript are supported.
Set the matching engine in game.json, keep all game code inside your upload, and start the game from an external JavaScript file. The build guide lists the packaging rules.
Yes. Add storage to your game’s capabilities and use the SDK to read and save progress. Signed-in players keep saves across devices. Guest saves stay with that guest and expire after 30 days.
Your game decides what to save and how to handle changes between versions. The storage methods in the SDK reference show how.
Connect your agent to UniPlays through MCP, the standard way coding agents plug into outside tools. It gets the SDK docs, templates and tools to upload, test, preview and manage your game. Ask it to build a game, fix validation errors, or prepare an update.
The publish tool prepares a launch or update. You review it and sign in your wallet. The agent never signs for you.
All game code must ship inside your upload: JavaScript and WebAssembly files. UniPlays blocks inline scripts, scripts loaded from other sites, eval, the Function constructor, service workers, and multi-threaded WebAssembly.
If your game calls an outside API, list its HTTPS address in network.allow. These rules keep every game inside the platform’s safety limits.
Up to 90 MB zipped and 200 MiB unpacked, with up to 3,000 files. One file can be up to 64 MiB.
Put game.json at the top level of the archive. The upload can unpack to at most 20 times its zipped size, and folders can be at most 16 levels deep.
Add each feature your game uses to capabilities in game.json, and check it with can() before you call it. The SDK reference lists every method and the capability it needs.
A call can still be refused, for example for an item that is not in your catalog. Handle not_available and the other named errors so the rest of your game keeps working.
Upload your bundle, run full validation, and play the preview. Fix errors, read warnings, and check controls, saves and the player experience before you launch.
Static validation checks the archive, manifest, scripts and WebAssembly. Full validation adds a real browser test. The launch page always runs full validation; with MCP, set mode: "full" when calling validate.
The launch fee is a fixed 0.0004 ETH, plus network gas (the fee your wallet pays the network) and any optional first token purchase. Games that run in the browser, or use your own backend, need no UniPlays hosting credit.
Optional UniPlays backend hosting starts with $25 of prepaid credit. You see the payment details in the launch flow. Hosting payments are not refundable, unused credit carries forward, and there is no monthly subscription.
No. There is no reserved token allocation for the creator or UniPlays. Creators can buy tokens, including an optional first purchase in the launch transaction.
Your fee earnings do not depend on holding tokens. You earn your share of the trading fee either way.
You earn from your game token’s trading fee. When the token trades, the standard fee is 1% of the trade. That fee is split equally: 50% to the creator and 50% to UniPlays. This applies on the bonding curve and in the graduated pool. In the first minute after your game opens, a buy pays a higher fee that falls to 1%. You earn half of the normal 1% part of it, and the rest goes to UniPlays.
You withdraw your share from your profile, paid in ETH. Earnings depend on trading activity and are not guaranteed. You also earn a royalty when players resell your items.
Each game launches its own token (an ERC-20) with a fixed supply of 1 billion and 18 decimals. Players can explore and trade it from the game page.
The current launch contracts split the supply like this:
The reserved liquidity tokens the graduation fee frees are burned. The creator and platform receive no free allocation.
When the bonding curve sells out on Robinhood Chain, the token graduates, and a graduation fee of 0.3 ETH goes to UniPlays from the raised funds, never more than half of the ETH that would seed the pool. The rest of the raise, with the matching share of the reserved liquidity tokens, opens a trading pool at the curve’s final price, give or take rounding. Any reserved tokens left over are burned.
The pool’s liquidity and the permanent token reserve are locked, with no way to withdraw them. The 1% fee on each trade continues in the pool, split equally between the creator and UniPlays. A graduated token trades in its pool.
No. After launch, the game token cannot create more tokens, charge a transfer tax, block wallets, or pause trading. Its supply is fixed.
Suspending a game on UniPlays does not pause the underlying token contract.
Yes. Declare item types in game.json, and players own them as NFTs (ERC-1155). Players can trade them in a marketplace priced in your game token. The assets.* methods cover inventory and item data; market.* covers listings, quotes, and trades. One manifest version declares at most 256 item types, and a game’s collection holds at most 4,096 over its whole life; a declared type is never removed.
These refuse with not_available: an item that is not in your published catalog, and a listing the market service cannot read. Keep the rest of your game working when one does.
You earn a royalty each time a player resells one of your items in the marketplace. Set it with assets.royaltyBps, a number from 0 to 1000: 500 means 5% of the sale price, and 1000 means 10%, the most allowed. The royalty is taken from the seller’s proceeds.
Example: an item resells for 1,000 tokens with a 5% royalty (500). You earn 50 tokens, taken from the seller’s proceeds.
The royalty is set once, in your first item declaration, and cannot change later. It is separate from the game token’s trading fee.
List each item with an ID, a name and a positive price in store.items. Set store.pricing to usd for dollar prices, or token for a fixed amount of your game token. To change a price, publish a new game.json.
store.purchase opens the UniPlays confirmation window. It takes the price from your published game.json and charges through this network’s checkout. If a network has no checkout, the purchase is refused and the player is not charged.
Dollar prices. A $2.00 item costs $2.00 worth of your token, converted on the blockchain at the token’s 30-minute average price. A game’s market must first pass a minimum liquidity check (the depth floor) before dollar prices work.
A risk to know. While a market is thin, a player who holds most of the tokens in circulation can spend them on dollar-priced items or draws for several times what selling them would return (about 4.3 times at the default floor), because no per-player cap applies. After graduation, players selling into the pool can also shrink its depth to about 57% of what the floor measured. Keep a dollar-priced catalog small while the market is young, or price in tokens.
Holder rewards send all or part of your game fee to the people who hold its earning NFTs. Each earning NFT type has a weight, and rewards are shared by weight. You set the split and the weights at launch, and they cannot change later.
New NFTs. A serial earns from its mint (a serial is one numbered copy of an NFT). Its share from before the mint is taken from holders when it is minted: the token is burned and the ETH goes to UniPlays. Shares of serials never minted stay locked for good.
Claiming. Income is claimable only once it is collected. A claim made before a collection pays less than one made after it, and whoever holds the NFT later gets its share of what is collected then.
What earns. Only serials within both the collection cap and the table cap earn, and a type declared stackable earns nothing. Every permission UniPlays prepared for its own key excluded every weighted type and every draw type when it was prepared. A permission the developer signs for that address by other means is outside that rule.
Your game’s reward pool (the game treasury) cannot be withdrawn from. It pays out in only three ways: awards signed by the key you appoint (to any address, or only to addresses you allow if that key is hosted), item buybacks (the pool’s standing offers to buy items from players) and chance prizes. Each has its own daily limit, counted from midnight to midnight UTC.
Current limits can be lower, and older awards and buybacks with a guaranteed price keep the limits that applied when they were made. Appointing a different signing key cancels every award not yet paid.
Declare the draw in draws and its prize types in assets, then publish. Open your game under My games, go to Draws & chance and pick Prize draws. Each draw shows its steps.
game.json, and you confirm it in your wallet. Creation fixes the price, odds, per-wallet limit, burn and prize pool for good, and a game can create at most 4,096 draws over its life.Rules to know
Each play is decided by a public random number (from drand) published after the play. The play dialog says before you pay when a draw’s results are yours to reveal. If a result has not arrived 30 seconds after its random number is due, the game page offers a Reveal button, which costs a network fee and reveals every earlier waiting play too.
Plays settle in order, so a play further back waits for the plays ahead of it.
Refunds
Prizes
UniPlays sends each win to its winner for the draws it reveals. A win still waiting shows in the draw panel with Claim prize, which can send it to another address if your wallet cannot receive it.
Upload a bundle with a higher version number, validate it, and sign the update with your wallet. Add developer notes to tell players what changed. The new version appears once the update transaction is confirmed and processed.
Updates can change game code, artwork, capabilities, token checks, shop prices, and allowed network addresses. The token’s name and symbol, its description and links, and the one-liner shown under your game’s name are set at launch and never change. To roll back, select a previously published version and sign the rollback in your wallet.
Your hosted backend stops answering new requests once the credit cannot cover them. Parts of your game that work on their own in the browser keep working, and protected saves are kept under the retention policy shown when you set up hosting.
A confirmed manual top-up restores eligible hosting. It does not lift a security suspension. NFT rewards you already signed for players can still be claimed; network fees are paid separately.
A key can only do what you allow. uniplays:read is required for tools such as scaffold, stats, token, versions, and list_items.
Add uniplays:publish for uploads, validation, previews, publishing, catalog updates, and leaderboard seasons. Create and manage access keys in your profile.
The hosted game and its platform calls are blocked. SDK calls return game_suspended until the suspension is resolved.
Suspension does not pause the underlying token contracts. Stop retrying blocked calls and contact UniPlays support to resolve the game’s status.