SOMETHING ONLINE ARCADE — ENGINE INTEGRATION BRIEF
Attach this source kit and my existing game project. Preserve the source language:
Unity C# compiles to Web/WebAssembly; compatible Java uses TeaVM JavaScript.
Use the included adapter and prepare-export.mjs. Do not replace my game with a
JavaScript rewrite just to claim engine compatibility. Explain unsupported engine
features and size limits. No native binaries, server scripts or external CDNs.

Read README.txt. Use ArcadeClient (Unity) or Arcade (Java). Subscribe before Connect,
wait for ready, restore versioned saves, pause input/simulation/audio on pause,
resume only on resume, and acknowledge save errors without discarding progress.
Use the solo or grid-lines online example as appropriate. Online multiplayer is
limited to the reviewed grid-lines-v1 rules, with the server controlling all moves
and results; never fabricate wins, tickets or trusted stats in the client.

Return ONE upload.zip containing arcade.json; give rights/AI disclosures and actual test evidence in your reply.
Do not call a bridge unit test a successful Unity/TeaVM compile or browser test.
Each compiled build needs isolated runtime QA and administrator approval. Include
loading, keyboard/touch only where supported, save/reopen, pause/resume, and for
online: two-account legal/illegal turns, reconnect and rematch.

Commerce is disabled. Preserve commerce-contract.json as a future design reference,
not an active service. Do not add wallet prompts, blockchain RPCs, private keys,
token minting, payments or smart-contract calls to uploaded games. Future requests
will use platform catalog IDs and server-verified receipts, not arbitrary addresses.


TWO WAYS TO FINISH — ONE UPLOADABLE ZIP
COPY FOR MY AI: open https://somethingonline.com/preview/creator.html#creator-guide,
choose this kit's game type, then Copy for my AI. The AI asks a few plain questions,
uses the linked kit and returns ONE complete game ZIP, with arcade.json inside.
If it cannot download the kit, attach this exact kit. Never claim an unbuilt ZIP.
STEP BY STEP: use the same workshop's Step by step guide. Build/test the game,
keep all required runtime files and the completed arcade.json at the ZIP root,
then choose that one ZIP. The workshop reads the manifest; review its details and
complete rights/AI disclosures personally. A separate manifest upload is optional.

OPTIONAL CABINET SKIN — EXACTLY ONE NEW IMAGE
Classic upright pilot: cabinet/skin.png, one static opaque 1024 x 1024 PNG, <=4 MiB.
Read https://somethingonline.com/preview/creator-cabinet-kit/cabinet-template.json
and download https://somethingonline.com/preview/creator-cabinet-kit.zip first.
Follow its exact six named regions, shared side/back art and physical obstructions;
never guess UVs or generate separate panel images. Add cabinetSkin with templateId
classic-upright-v1 and texturePath cabinet/skin.png to the manifest. Keep the game's
existing one cover unchanged; for a new game make one cover.png at 960 x 640.
Thus required submission art is one cover plus one atlas, not extra variants.
Agree any gameplay-art filenames, dimensions and count before creating those.
Do not put the template GLB, guides, example skin, nested kits, extra covers,
mockup renders or unused image versions in the game ZIP. The platform supplies
the model. Skin availability is server-gated; use the standard cabinet if off.


CURRENT UPLOAD AND REVIEW WORKFLOW — OCTOBER 20, 2026

A compatible existing browser game does not need AI or a starter-kit rebuild. arcade.json is optional: when absent, the workshop suggests entry/cover files and stores your confirmed details alongside the unchanged ZIP. A manifest helps automatic form filling; it does not automatically add pause, saves or scores. Keep the existing SDK contracts.

For a new build prepared using this kit, include a completed arcade.json for convenience. For an update, choose My games → Upload new version and preserve the game ID, ownership and compatible save format. Never replace the original source or uploaded archive in place.

Scanning, structural checks, isolated testing and review still apply. Regular creators use the beta/final review process. The verified site owner may use the audited Publish as owner option for their own tested submissions without beta votes; other developers do not gain that permission. No kit or passing scan publishes a game automatically.

NO-AI PATH: follow Step by step in the workshop and download creator-guides/existing.txt for an existing game. Only declare AI assistance when it was actually used.

GUIDED NEW GAMES: creator-guides/25m.txt, creator-guides/1h.txt and creator-guides/4h.txt ask about style, movement, controls and progression. The matching browser starter ZIPs are creator-kit-25m.zip, creator-kit-1h.zip and creator-kit-4h.zip. These playtime targets are estimates to test, not a claim that the sample is a finished campaign.
