Open UGC local quick-start
Local Beta. Public launch pending. NanoRes services: 21+. This is a platform policy, not a claim that eligibility enforcement or worldwide legal availability is qualified.
English walkthrough · Guía en inglés · دليل باللغة الإنجليزية · अंग्रेज़ी गाइड
The visual guide has English, Spanish, Arabic and Hindi steps. This detailed walkthrough remains English. Choose Create, Buy or resume, or Build there to keep the first step short.
Create a package
- Open My assets and select registered work linked to your account. Use Add work for a new private upload and registration.
- Choose Create package. Set purchase or paid-usage prices and owner shares. Review each explicit transaction.
- Choose Prepare release, match the private files and request operator review. Preparation does not publish a storefront or make new payments available.
What linking and payments mean
Linking an existing OGAL reference does not mint or upload it again. Account association, current ownership, owner consent, access and licensing are separate. An OPP purchase does not transfer OGAL ownership or create licensing terms.
OPP charges a fixed 1% of settlement revenue. Owner splits apply after that fee. Package creation has a separate configured fee; SOL pays network fees and account rent. These are distinct from Arcade's 10% entry fee. Local demonstrations use DBONK TEST, not the mainnet DBONK token.
Buy or resume
- In the operator's catalog, inspect the release contents, exact token price and deployment identity. Open the selected buyer pilot only after its configuration check matches.
- Use the purchasing wallet. Review the total, recipients and SOL costs before explicitly signing. Stop if the wallet presents a safety warning; a local simulation is not a wallet safety guarantee.
- Wait for the verified receipt and access result. Open the purchased content or paid-usage result. If interrupted, return to Activity and check the original order first.
Interrupted, unavailable or recovery-only?
- Unknown does not mean failed. Do not replace an uncertain payment with a new order. An explicit retry must reuse the original order; duplicate attempts can still incur network fees.
- Closing a dialog does not cancel a chain transaction. If a receipt is unavailable or unfinalized, access must wait.
- Access belongs to the purchasing wallet and sealed release. A different wallet, release or deployment is not the same purchase.
- Paid usage records a particular operation and purchased quantity. It does not create spendable credits.
- Open recovery restores retained access up to the approved cutoff. Recovery-only listings allow no new payments.
Run the existing local previews
For developers or an operator helping a creator: use the existing OGAL-Dashboard checkout with its dependencies already installed and Node 24. Do not put signing keys, sessions or private content into Docs. If a listed port is occupied, preserve the existing service and arrange a separate preview.
From the Dashboard repository, build and start the synthetic creator preview:
node --version
npm run build
npm run preview
Open http://127.0.0.1:8800. Choose Open my workspace, then Test creator. Select an asset and choose Create package. Connect Test publisher for the isolated creator walkthrough. These test profiles are absent from the normal host.
To explore publication and buying with the existing prepared test releases, use the separate publishing preview from that same checkout:
npm run preview:publishing
Open http://127.0.0.1:8863 and choose Enter test operator. Approve the supplied releases, then open Storefront, select them and choose Review publishing. Review and select Publish and open, then Visit storefront. The catalog is on port 8864 after publication; follow its verified handoff to the intended buyer pilot. Review a DBONK TEST purchase, complete it using the supplied test wallet and return through Activity to inspect the same order.
The publishing preview uses its own prepared fixtures; it does not automatically publish a package from the separate creator preview. Both use synthetic chain responses. They prove neither real settlement nor external-wallet compatibility. Stop only the preview you started with Ctrl+C. Restarting a synthetic preview creates a fresh demonstration; use the documented persistent host for retained work, not these fixtures.
Commands and labels above come from Dashboard README, its publishing preview and publication walkthrough. These are existing executable local commands; this Docs change does not qualify a new chain run.
Unity setup status
An executable Unity quick-start is not yet qualified. Inspect the pinned Solana Toolbelt package before relying on a setup example:
| Declared package fact | Qualification limit |
|---|---|
| Toolbelt 1.0.3; Unity 2021.3 | A manifest declaration is not a fresh editor compatibility test. |
| TextMesh Pro 3.0.6; Newtonsoft Json 3.2.1 | Dependency declarations do not establish a reviewed integration or license clearance. |
| Two OGAL samples | Both sample paths are empty. No Samples~ directory exists in the inspected source tree. |
The README describes a Solana Wallet sample that the manifest does not supply. A usable read-only sample, actual editor/import/build evidence and dependency/license disposition are still needed. Do not guess sample paths, C# APIs or installation credentials. Existing Unity references and other-platform references retain their separate status.
Independent builders do not need MMO participation, Digital Nation membership or DBONK ownership merely to explore neutral tools. Application-specific paid services can have their own requirements.
What remains before public release
The local Dashboard and OPP implementation is reusable. Public hosting and production Account enrollment are not activated by this guide. Deployed OGAL/source assurance, independent review, supported external-wallet purchase/usage/recovery, exact production program and authority settings, creation pricing, funding and release approval remain open. Source availability is not security certification or permission to deploy.
This guide adds no runtime, wallet, token, vendor or mainnet change. Read the current Dashboard readiness and the OPP integration source for the dated implementation boundary. Historical reference pages describe their own reconciliation snapshots; they do not erase the later accepted local workflows summarized here.