01Build your game
Build your game
Start with a browser game and keep all its scripts inside your upload. Then describe the game in game.json: its name, the features it uses, and its token.
{
"schema": "uniplays/game-manifest/1",
"name": "Comet Courier",
"version": "1.0.0",
"entry": "index.html",
"icon": "art/icon.png",
"engine": "vanilla",
"orientation": "landscape",
"inputs": ["keyboard", "mouse", "touch"],
"capabilities": ["storage", "leaderboard"],
"contentRating": "everyone",
"token": { "name": "Comet Courier", "symbol": "COMET" }
}All game.json fields
- schema
- Always the exact text "uniplays/game-manifest/1". Copy it as is.
- id
- Added when you first publish. Keep it in game.json when you update, so UniPlays knows which game you mean.
- name
- Your game’s name. Up to 48 characters, with no spaces at the start or end and no hidden or invisible characters.
- genre
- Optional. Pick one of Arcade, Racing, Roguelike, Puzzle, Strategy, Adventure, Simulation, RPG, Shooter, Platformer, Card, Sports, Party, Chance, MMO, Other.
- tags
- Optional. 1 to 5 different tags from singleplayer, multiplayer, co-op, pvp, casual, competitive, idle, turn-based, real-time, pixel-art, 3d, retro, fantasy, sci-fi, horror, story-rich, physics, crafting, collectibles, mobile-friendly, in addition to genre. Players filter the catalog by genre and by tags, and a game must carry every tag they pick.
- version
- A version number such as 1.3.0. Raise it with every update.
- entry
- The .html file that starts your game, such as index.html. Use a plain path inside the upload: no leading slash, no .., no web address, no ? or #, at most 255 characters.
- orientation
- One of any, portrait, landscape, default any: the layout the game needs. On a phone held the other way the player sees a rotate hint; nothing depends on a screen lock.
- inputs
- At least one of keyboard, mouse, touch, gamepad, motion. Declare touch only when the whole game plays by touch alone, with no hover-only or keyboard-only action. Without touch or motion, phone players are told what the game needs: a controller if it declares gamepad, otherwise a keyboard or mouse.
- icon
- Required. The game icon and token logo, as a file path inside the upload. A square PNG or WebP of 512 px or more is best.
- screenshots
- Optional. Up to 8 file paths, no repeats.
- engine
- What you built the game with: one of phaser, pixi, three, godot, unity, playcanvas, construct, vanilla, other. Choose the real one; a wrong value can fail validation.
- engineVersion, plugin
- Written by the UniPlays Unity and Godot plugins when they build. Leave both as the build wrote them. plugin names the engine and plugin release, such as godot@0.1.0, and must match engine.
- changelog
- Optional. Notes about what changed in this version, up to 2000 characters.
- capabilities
- The platform features your game uses, such as storage or leaderboard. Anything not listed here is blocked while the game runs. Empty by default.
- network.allow
- Outside web addresses your game may contact, such as your own API. HTTPS only, up to 8. Each one also allows its wss:// twin: a WebSocket to the same host and port.
- token
- Required. Your token’s name (up to 31 bytes: one per plain letter, digit or space, more for accents and emoji) and its symbol, 2 to 11 characters of A-Z and 0-9. Both are permanent after launch. Optional holder rules (needs capability token.gate) can unlock features for token holders.
- store
- Optional. The items your game sells, priced in dollars or in whole tokens. Needs capability store.
- leaderboard
- Optional. The highest score that counts, written as a decimal string of at most 38 digits. Needs capability leaderboard.
- leaderboards
- Optional, and exclusive with leaderboard (use one or the other): 1 to 32 boards, each with an id, a name of at most 40 characters and an order: desc (highest score wins) or asc (lowest score wins). A desc board keeps each player's highest score and may set maxScore. An asc board keeps the lowest score and needs minScore, the floor below which no score counts. A call that names no board uses the first, and every board has its own seasons. Needs capability leaderboard.
- assets
- Optional. The item types your game can create, and the royalty you earn when items resell on the marketplace. The first version that declares the royalty makes it permanent. Needs capability assets.
- rewards
- Optional. The most reward tokens one player can earn per day. Needs capability rewards.
- economy
- Optional. Your game's reward pool: the game fee that fills it, how shop purchases are split into it, and the limits on what it pays out. The maximums are fixed for good at launch. Needs capability economy.
- drops
- Optional. Your game's loot tables and drop seasons, which players see as drop periods. They change only when you publish a new game version; no page or tool edits them. Needs capability drops.
- draws
- Optional. Up to four paid prize draws. Each has an id, a name, a price in dollars or whole tokens, a win chance, a per-wallet limit, the share of each entry that is burned, and a prize pool whose counts equal each prize type's supply cap. Needs capabilities draws and assets.
- contentRating
- One of everyone, teen, mature. The default is everyone.
- sdkBuildHash, bundleHash
- Added by UniPlays. Leave these out of your game.json.
02Test it before launch
Test it before launch
Pack your game as a ZIP, TAR or TAR.GZ file of up to 3,000 files, with game.json at the top level, and upload it. Full validation runs on the launch page and includes a test in a real browser. Fix errors, read warnings, then try the controls and saves in a preview link that is not listed publicly.
Full validation opens your game in a real browser. The first screen must appear within 20 seconds, and the game must follow the code rules in What your game can run. A preview link expires after 24 hours.
With an AI agent, it runs validate with mode: "full" and then preview.
03Launch your game and token
Launch your game and token
On the launch page you check your name, ticker, description, artwork, social links and an optional first buy. Then your wallet signs the launch. The token name, ticker, description and social links are permanent after launch.
- Name & ticker
- Your token’s name (up to 31 bytes: one per plain letter, digit or space, more for accents and emoji) and its ticker (2 to 11 letters A-Z or digits 0-9). Both are permanent after launch.
- Where the tokens go
- Of the 1 billion tokens: about 71.43% on the bonding curve, up to 20.41% into the pool at graduation, and 8.16% into a permanently locked reserve.
- Bonding curve
- The launch price. It rises as players buy.
- Graduation
- When the curve sells out, the money raised and the set-aside tokens move into a trading pool, and the pool’s liquidity is locked.
- You earn
- Every trade pays a 1% fee, split equally between you and UniPlays, so you earn 50% of it.
- First minute
- In the first minute after your game opens, a buy pays a fee that starts at 90% and falls to 1%. You earn half of the normal 1% of it, and the part above 1% goes to UniPlays. Your own first buy pays 1%.
- Launch fee
- A fixed 0.0004 ETH, plus network gas (the fee your wallet pays the network).
- First buy
- Optional. Buy some of your own token as you launch, up to 20% of the graduation target (the amount the curve raises, 4.2 ETH by default, so 0.84 ETH). There is no free creator allocation.
04Update or roll back
Update or roll back
To update, raise version in game.json (for example 1.0.0 to 1.1.0) and keep the game id. Add developer notes, test the new build, then confirm in your wallet. To roll back, select an earlier published version and confirm that in your wallet too.
An update can change code, capabilities, artwork, item prices and allowed network addresses. Manage versions from your game’s workspace.
Manage games in your profile05Sell and trade items
Sell and trade items
Declare item types, shop prices and trading permissions in game.json. Items resell on a marketplace that settles in your game token. You set a royalty from 0% to 10% of each resale price; it comes out of the seller’s proceeds and is paid to you. For example, a resale for 1,000 tokens with a 5% royalty pays you 50 tokens.
Changing a shop price needs a new published version. Handle the named error so gameplay can continue when an economy feature refuses a call.
Selling on OpenSea and other marketplaces
- Your collection is also listed on marketplaces outside UniPlays. Its owner is the developer wallet registered for the game, so you claim and edit the collection page on OpenSea with that wallet.
- Your royalty setting and the 10% royalty cap apply in the UniPlays shop and on marketplaces that read the ERC-2981 royalty setting, and nowhere else.
- As owner you can also set fees on other venues and royalty registries. UniPlays neither sets nor caps those. A creator fee set on a venue comes out of the selling holder’s proceeds.
- If you hand the game to another developer wallet, re-point or clear any royalty registry override you set.
06Add a backend (optional)
Add a backend (optional)
Most games need no server. Choose what fits your game.
- Browser only
- Everything runs in the player’s browser.
- Your own server
- Connect your own HTTPS backend.
- UniPlays hosting
- UniPlays runs short server functions for you. It starts with $25 of prepaid credit. Review the payment details at launch; top-ups are paid in USDG.
To host server code, upload your bundled JavaScript backend separately. Call uniplays.backend.call with a unique ID for each action, and reuse that same ID when you retry so the action never runs twice. Hosting runs short request functions, not continuous game servers.
07What your game can run
What your game can run
Web exports from Phaser, Pixi, Three.js, Godot, Unity, PlayCanvas, Construct and plain JavaScript work, as long as they do not use multiple threads.
- Keep all JavaScript and WebAssembly inside your upload.
- Remove inline scripts, scripts loaded from other sites, eval, service workers, and multi-threaded WebAssembly.
- List each outside API by its HTTPS address in
network.allow. - Call
uniplays.ready()before other UniPlays methods.