# Publish and earn

## Publish a saved draft

In the world builder, choose **Publish** to save your changes and queue that exact revision. You can also select a world under **Your worlds**, choose **Reload saved changes** and then **Publish world**.

The server revalidates the document, asset ownership and every budget. At least one supported game station is required. If the revision is stale, reload before retrying.

Players see **Update incoming** and new bets in that world are blocked. Existing hands and rounds continue; players can finish their actions, draw or cash out. Waiting PvP coinflips can be cancelled by their creator or expire after ten minutes. After at least five seconds of notice, the queued layout is applied when all accepted bets have settled. Other worlds continue normally.

Connected players automatically load the new 3D world without reloading the page. The queued revision is a snapshot: later draft edits do not change it. A queued update survives a server restart. Use **World → Cancel pending update** in the builder to reopen betting without applying it.

Publish and cancellation use your authenticated owner session. AI credentials can save drafts and upload models. Use **Play world** to enter the published version yourself.

## What players receive

The world browser shows the published world. On join, players fetch the published document and download its required assets with a loading-progress screen. They enter after construction finishes. The public lobby's board ranks active worlds by player count. 

Cloudflare checks the current approved revision with Betworld's server, then delivers its layout and referenced models, textures and audio from R2. Published layouts are immutable snapshots; drafts remain private on the server. WebSocket notifications tell connected players when a new revision is ready. The server continues to authorize every game and settle every bet independently of the downloaded layout.

An unpublished draft is not joinable by other players. Further draft edits do not change the published version until the next successful publication.

## Earnings calculation

The owner receives **10% of user edge (the theoretical house edge) on settled wagers** placed in their world. For a $100 wager with a 1% theoretical edge:

```text
$100 × 0.01 × 0.10 = $0.10 owner earnings
```

The result does not depend on whether that individual player wins or loses. Earnings use the edge recorded by the game settlement, not a client-supplied edge or creator setting.

The 10% rate applies to settlements after the rate-change migration. Earlier accruals keep their recorded 5% rate, including their unpaid fractional carry.

Earnings are credited automatically in increments of **$0.0001** after settlement processing. Smaller fractions carry forward until they reach that amount. For example, two settlements earning $0.00005 each produce a spendable $0.0001. Each settled wager contributes once.

Betworld uses 10,000 integer accounting units per dollar. API fields named `paidCents`, `earnedCents` or `availableCents` are expressed in cents and can include two decimal places: `0.01` cents is $0.0001. Crypto amounts remain in each network's native atomic units.

## Ownership and active bets

A world's owner is fixed. Tokens cannot transfer ownership or redirect the beneficiary. Players must actually join the creator world before attributing a bet to it. Game availability is checked against that world's published station list.

Disconnecting the final player unloads ephemeral room state; durable wager and accounting records remain. Accepted bets still settle or recover according to the game's rules. Publication does not erase history or change past earnings.