#Submitting a world to the metaverse

A guide for creators on opting a published world into the wilds.ai metaverse economy (Phase 4).

**Heads up — launching Q3 2026:** the metaverse opens in Q3 2026. Submissions land today and staff may approve early so the queue clears before launch day, but the per-blueprint reward pool and leaderboard rewards activate together with the launch flag flip. Approval before launch just means your world is queued and ready; nothing activates until Q3 2026.Heads up — launching Q3 2026:Heads up — launching Q3 2026: the metaverse opens in Q3 2026. Submissions land today and staff may approve early so the queue clears before launch day, but the per-blueprint reward pool and leaderboard rewards activate together with the launch flag flip. Approval before launch just means your world is queued and ready; nothing activates until Q3 2026.

#What the metaverse opt-in actually does

When your world is approved into the metaverse program:

• 10% of every marketplace purchase of your world flows into a per-blueprint reward pool instead of the platform general fund. Today, with the launch flag off, that 10% routes to system_platform; on launch day it flips to your pool with no code change on either side.
• Top-of-leaderboard players in your world receive periodic in-world $WILD rewards from that pool. Rewards only happen on metaverse-approved worlds, so submitting is the gate for any leaderboard reward distribution at all.
• Your world becomes eligible for cross-world inventory, characters, and economy flows once the broader metaverse universe ships. Worlds that never opted in stay self-contained.

The submission is per-blueprint, not per-account. A creator with five published worlds picks which subset opts in. Worlds you don't submit keep their existing distribution (private / unlisted / public listing) unchanged.

#How to submit a world

1. Open the world in Studio (/app/play/[id]/edit).
2. Find the $WILD Metaverse Opt-In panel under the world section of the left tree.
3. Read the agreement that the Submit world to metaverse button opens:
   • Economy: how the 10% pool routing works (in-world $WILD only).
   • Rewards: how leaderboard rewards distribute in-world $WILD to top players.
4. Check the clauses. The submit button stays disabled until every box is checked; there's no partial agreement.
5. Optionally add creator notes (up to 1000 characters) explaining anything the staff reviewer should know — the world's tone, content rating, audience, why it's a fit, anything the description doesn't already cover.
6. Click Submit. The Studio panel now shows status submitted and the timestamp.

You can withdraw a submission anytime before it's been decided. The panel surfaces a Withdraw submission button when status is submitted or under_review. Withdrawing closes the active submission; you can re-submit later with no penalty.

#What happens after you submit

The status badge on the Studio panel updates in real time when you reload. Each terminal status carries the reviewer's reason in the history list under Past submissions ({N}).

#What staff look for

A submission gets approved when:

• The world's content rating matches what it actually generates. A standard-tier world that consistently produces mature content fails the rating check.
• The world has actually been played end-to-end. Empty drafts, half-finished prompts, or worlds with no completed sessions don't get approved — the reward pool only makes sense for a world that's getting played.
• The world doesn't violate the wilds.ai content policy (no CSAM, no non-consensual content involving minors, no real-world public-figure impersonation that crosses defamation lines, etc.). These are hard-banned at every tier, metaverse-approved or not.
• The submission notes don't contradict the world's actual contents (you said it's a strategy sim; it's actually a chat-only roleplay).

Staff DON'T review for:

• Quality of writing or design. Whether your prose is good, your mechanics are tight, or your art is striking — that's for chatters and the marketplace to vote with their feet. The metaverse approval is a content-policy + integrity gate, not a quality gate.
• Subjective theme preferences. A horror world isn't rejected for being scary; a romance world isn't rejected for being romantic. Tier-appropriate content of any theme is in scope.
• Plan tier. Free-tier creators can submit too. The reward pool routing is the same regardless of plan.

#What changes when the launch flag flips (Q3 2026)

On launch day, ops flips WILDS_METAVERSE_ENABLED to true on the production env file. The single flag toggles:

1. Pool routing. The 10% per-marketplace-purchase share on every approved blueprint stops going to system_platform and starts going to the per-blueprint reward pool. The Studio panel's Pool balance and Lifetime rewards numbers begin moving.
2. Leaderboard rewards. The per-blueprint reward tick (cron) begins draining pools and crediting top players' in-world $WILD. Today the tick refuses to drain.
3. Cross-world flows. The cross-world inventory + character + economy hooks come online. Approved worlds participate; unapproved worlds keep their self-contained behavior.

Nothing on your end changes between now and launch. If you submitted today and got approved today, your world is registered and the pool exists at zero balance. On launch day it just starts collecting.

If you submit BEFORE launch but get approved AFTER launch, the pool starts collecting from approval time forward. Marketplace purchases before approval don't retroactively route to your pool — they already settled to system_platform.

#If your submission is rejected

The Studio panel shows the reviewer's reason in the Past submissions list. Common rejection reasons:

• Content-rating mismatch. Your world is tagged standard but consistently generates mature content. Fix: either upgrade the rating to mature (requires the mature-content consent grant on your account) or rewrite the prompts to fit standard.
• No completed sessions. The blueprint has never been played end-to-end. Fix: play it yourself or hand it to a few friends and finish a session before re-submitting.
• Description mismatch. The world's marketplace description doesn't match what the world actually does. Fix: update the description from the Studio overview panel.
• Policy violation. Hard ban — these don't get fixed. The reviewer's note explains which line was crossed.

You can re-submit after fixing the issue. There's no cooldown and no cap on resubmissions; the staff queue treats every new submission as fresh.

#If your approval is revoked

A previously-approved blueprint can have its approval revoked by staff for cause. The revocation reason shows up in the Studio panel and the blueprint's metaverse_status flips from approved back to revoked. The pool stops collecting and outstanding pool balance returns to system_platform on launch day or stays at zero pre-launch.

Revocations are rare and tied to specific cause: a creator updates a previously-approved world with content that breaks policy, an admin sweep catches a long-tail issue the initial reviewer missed, or a creator's account is suspended platform-wide. The decision and reason are logged; you can appeal via email to the address on the rejection notice.

#See also

• How creator rewards work — how creators earn and spend credits.
• Creator economy guide — the broader picture of how creators earn on wilds.ai.
• Browse and play — how chatters discover your world and what the listing surfaces.
• FAQ — short answers to common questions.