# Creator Showcase / Testing checklist

## Creator checks
- Export the exact source submitted; list all asset URLs and running service dependencies.
- Walk through the browser scene at player height; inspect footprint including animation.
- Perform the main action, completion and reset. Connect two clients to the same document if shared.
- Describe unknowns. Never translate simulated clients into tested avatar capacity.

## Organizer source preflight
- Preserve source version and SHA-256; do not execute uploads inside the submission service.
- Review MML presence, scripts, dependencies, light/emission values and declared dimensions.
- Source counts and pattern flags are heuristics. They do not prove schema compatibility, asset reachability, geometry bounds or behavior.
- Inspect assets separately. A transformed or animated GLB may extend beyond declared dimensions.
- Fetch third-party assets only in an isolated review environment with bounded resources and no privileged credentials.

## Browser rehearsal
- Open a fresh isolated test document; never overwrite a running event project.
- Load referenced assets. Inspect player-height appearance and usable interaction targets.
- Run the submitted instructions, reset and reconnect. Check shared state in two clients.
- Review update churn and rendering on a representative machine; record actual observations.

## Otherside rehearsal
Record date, venue/world, operator, exact source version/hash, asset versions, testers and conditions.
- Place at the intended transform and ground level; compare with the 100 × 100 × 20 m proposed plot.
- Test entrance/exit, collision, target reach, signs and lighting with actual avatars.
- For movement-driven mechanics, test the actual position/contact events. Motion Arena required floor-contact handling when probes were silent in Otherside; code that works in a browser alone is insufficient evidence.
- Perform a full round and reset. Check a second avatar sees the same result.
- Rehearse the host instructions and reconnect behavior.
- Record observed player count and hardware/network conditions; small tests do not certify a crowd.

## Selection and show
- Choose three and at least one usable alternate, based on taste AND observed readiness.
- Lock the exact rehearsed source and stabilize asset/service hosting. A source hash alone does not pin mutable asset URLs.
- Confirm creator credits and attendance/remote introduction plan.
- Before the show: check service uptime, asset loading, placement and reset.
- If a game fails, stop it, remove/disable it through the authorized operator and switch to an alternate. Do not live-edit unknown source in front of the crowd.