create-scene

Run the official `@dcl/sdk-commands init` scaffolding first, which generates scene.json, package.json, tsconfig.json, and src/index.ts with current templates. Then customize display fields, parcels, and entities rather than hand-writing config files that may diverge from SDK versions.

All entities present at scene load go in assets/scene/main.composite, never in src/index.ts. TypeScript is reserved for dynamically spawned entities, systems, game logic, and adding interactivity to composite entities fetched by name or tag.

No, GltfContainer only works with local files. Download approved models into the scene's assets/Models directory and reference them by local path, verifying each file begins with the glTF magic bytes.

Entities positioned outside parcel bounds are silently not rendered, with no error shown. Valid coordinates range from 0 to 16 times the parcel width or depth, and any negative X or Z value places the entity outside the scene.

Declare USE_FETCH for HTTP requests, USE_WEBSOCKET for sockets, ALLOW_TO_MOVE_PLAYER_INSIDE_SCENE for movePlayerTo, and ALLOW_TO_TRIGGER_AVATAR_EMOTE for emotes in requiredPermissions. Enforcement is uneven across clients, so declare permissions matching intent.

Scenes list parcels as coordinate strings in scene.json, with each parcel spanning 16x16 meters. The height limit grows with parcel count as log2(n+1) times 20 meters, so one parcel allows 20m and a 2x2 scene roughly 46m.