Hosting
MDL hosts your game workspace and public play surface. Hosted games are managed through the platform workspace UI.
Hosted games today
A hosted MDL game lives on the platform as a website-managed workspace with instructions, runtime settings, releases, a custom domain, and assets. The hosted workspace is what MDL actually uses at runtime.
Platform Workspace
Create and edit hosted games directly from the platform. The workspace owns instructions, runtime UI, openings, assets, releases, a custom domain, and monitoring without leaving the website.
The hosted workspace is the source of truth for creator editing and release preparation.
Why this direction
- Creators can build games without installing local tooling.
- The hosted workspace remains visible, inspectable, and editable on the platform.
- Runtime state, validation, release controls, and monitoring stay in one place.
- MDL stays the runtime owner instead of falling back to local files.
Workspace shape
The intended creator surface is the sectioned website workspace. Each section saves the game data MDL needs before serving or publishing a hosted game.
- Instructions for runtime, generated scenes, and avatar behavior.
- Opening for optional authored starting states.
- Assets for images, audio, and presentation metadata.
- Release for visibility and publishing controls.
Workflow
- Create the game from the platform.
- Edit instructions, opening content, runtime UI, and assets in the workspace.
- Preview the hosted game from the workspace.
- Create a release when you intentionally want to update the public play surface.
One workspace per game
Each hosted game has one editable workspace. If a creator wants a separate staging target, they create a second hosted game rather than maintaining multiple hidden states inside one game.