Take your game live with visibility controls, versioned releases, and optional custom domains.
| Setting | Who can play | Discoverable? |
|---|---|---|
| Private | Only you (the owner) | No |
| Unlisted | Anyone with the direct link | No |
| Public | Anyone | Yes — listed publicly |
Change visibility from the Release section in your workspace. New games default to Private.
Workspace visibility is separate from player visibility:
| Setting | What it means |
|---|---|
| Closed source | Players can play, but the workspace stays private to the owner. |
| Open source | Players can inspect non-sensitive hosted workspace sections on MDL in read-only mode. |
Public workspace access is read-only and intentionally excludes owner-only development controls. Schema and package assets can remain inspectable, while production instruction files are protected by replacing public prompt-file views and downloads with generic functional instructions.
Open-source style hosted games can offer a source-package download from the public workspace. Non-owner downloads include real manifests, schema, openings, and assets, with generic public instruction files in place of production prompt IP.
A release is a versioned snapshot of your game — instructions and configuration captured at a point in time.
You can publish and iterate without formal releases. They're most useful when you want to track changes or communicate updates to players.
Local package push for hosted games is meant for the hosted dev container, not for immediate live publication.
The intended model is: iterate locally, push into the hosted dev workspace, inspect and validate there, and then use release controls separately when you intentionally want to affect the live experience.
This keeps day-to-day development fast without turning every file push into a publish action.
By default, your game is accessible at the MDL platform URL. You can add a custom domain so players reach your game at your own URL.
Player sign-in on custom domains is handled by the MDL auth hub at mdl.continualmi.com. Your game domain redirects there for login, then returns with an MDL session for that host. You do not need to add every game domain to Firebase Authorized Domains.
Use Monitoring to see generations, players, universes, and purchase traces.
Instruction changes take effect immediately for new game sessions. Be thoughtful about major changes while players have active saves — renaming a background can break old universes that reference it.
When players access your game via custom domain, they see your title screen, not the MDL platform. Make sure these are set:
