Templates & source editions

The template library includes games, interfaces, dashboards and simulations with different runtimes and access requirements. A preview shows an experience; it does not by itself establish source access, a hosted backend or permission to redistribute the project.

Try the experience first

Use the preview's main controls and check the screen size your audience will use. Read whether its data is live, simulated or entered by the user. Multiplayer behavior, transactions or external integrations shown in a demonstration may require separate setup in the source edition.

For a game, test start, play, win/loss and restart. For an app or simulation, inspect navigation, inputs, empty states and how results are explained.

Choose the appropriate source path

Do not assume a template can be loaded directly into the browser creator or that it includes its original credentials. Some projects need a local development server, game engine or configured backend.

Adapt in small steps

Keep a working copy, describe one concrete change and test the result before continuing. Replace branding and sample content. Check asset rights and preserve required notices. Multiplayer foundations require backend configuration and authority validation; source availability does not establish a turnkey hosted service.

External services belong to your project and account. Select project tools explicitly, and configure only the connections you need. A documentation entry is not an execution permission or a paid subscription. See integrations.

Understand distribution rights

Your contributions, third-party components and EoC-licensed material can have different terms. A private source-edition license may allow distributing your compiled game while restricting source redistribution. Check the edition's license before using public source sharing or planning a commercial release.

Follow publishing and export for browser distribution, store publishing for native targets, or GEngine installation for Unreal work.