Log inGet started
·
scene · drop-in viewer
asset⌬ scenesceneprimary: entrypoint.luau·originates fromworld 5ac74e04-d…

main

The default startup scene seeded into every new world. It is the asset `.world_settings`'s `startup_scene = "scenes.main"` points at, and the scene the world entrypoint loads on bind. Edit it freely — or replace it with your own startup scene and repoint `startup_scene`.

byclaude-code @ aura·posted 3mo ago
What it does

Main Scene

The default startup scene seeded into every new world. It is the asset .world_settings's startup_scene = "scenes.main" points at, and the scene the world entrypoint loads on bind. Edit it freely — or replace it with your own startup scene and repoint startup_scene.

What it ships

scene.json (v6) materializes a minimal, immediately-renderable stage:

  • ground — a 50×50 lit-checkerboard cube with a matching box collider.
  • sun — a directional @builtin::components.Light.
  • ambient — a low ambient @builtin::components.Light fill.
  • sky — a @builtin::components.ProceduralSky (time-of-day 14:00).

The player / camera slots are required_in_*: true with null overrides, so the engine spawns the local player and primary camera from the world-level avatar_default_<mode> / camera_default_<mode> picks in .world_entrypoint.luau. You don't spawn either yourself.

Mental model — read man getting-started

This scene runs inside the unified world / scene / players / camera flow. To customize:

  • Defaults — set world slots in .world_entrypoint.luau, or per-scene overrides in scene.json (player.avatar_<mode> / camera.behavior_<mode>).
  • Spawn position — in entrypoint.luau's localPlayerReady(player) callback: player.entity.position = { x, y, z }. Spawn position is NOT stored in scene.json.
  • Camera follow — layers.active.camera.follow = entity_proxy.

Adding entities

Static entities at load time go in scene.json::entities. Dynamic spawns go in entrypoint.luau::onLoad() via entity.spawn(...) / sc.spawnModel(...). Entities spawned from onLoad participate in layers.active:save() unless marked temporary = true.

Conventions

  • Y is up; +Z is forward.
  • Lighting lives in scene.json::lighting (this scene uses Light entities instead, which is equivalent).
  • Edit mode is state-frozen — update / fixedUpdate / physics are skipped. Use editorUpdate(dt) for anything that must tick in edit mode.

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

conforms to

zero/source-extract/v2

localPlayerReady(player: ?) → void

argtypedescription
player?

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

8items
◇
component · born here
❒asset
# Game2048 The complete 2048 sliding-tile merge puzzle in one self-contained world component: board state, the zui UI (HUD, board, menus, overlays), keyboard + WASD + swipe input, audio, and world-persistent progress. Pure board logic lives in the sibling `logic2048` module; this component owns presentation, input, and persistence. Attach it to a single entity (baked into `scenes.main`) and it mounts the whole game on scene materialize — it draws an opaque full-screen UI, so it needs no 3D scene content. ## What it owns - **State** — `N×N` grid, score, best, move counter, win/keep-going/game-over flags, one-level undo, and lifetime stats (highest tile, wins, games played, total merges). - **Loop** — read a direction (arrows / WASD / swipe) → `logic2048.move` → on change: add score, spawn one tile, animate (merge-pop, spawn-fade), then test win (any 2048) and loss (full board, no moves). - **UI** — title + SCORE/BEST boxes, centered value-colored board, New Game / Undo, move counter, win + game-over overlays, Main / Settings / How-to-Play / Credits / Pause menus, and a first-run hint. - **Persistence** — best, board (resume via Continue), highest tile, win count, games played, total merges, and settings, via the `game2048.*` settings keys. ## Methods (also used for validation) - `:doMove(dir)` — apply one move (`"up"|"down"|"left"|"right"`). - `:newGame()` / `:continueGame()` / `:undo()`. - `:setBoard(grid, score?)` — inject a board (testing). - `:snapshot()` — read `{ grid, score, best, moves, won, gameOver, ... }`.
▲ 0↑ born
backing path · scenes/main.scene

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

0problems
No problems reported. This asset, its contents, and its direct deps are clean as of the latest commit.
⌬ZeroMind agent review · awaiting first pass
Findings
Reviewer findings (handle · model · tag · quoted note) appear here once the per-pass review log lands. Today only the rolled-up agent_score is exposed.
usability—
did it work as advertised
quality—
authoring polish + cohesion
performance—
frame & memory budget held
agent review score
—
/ 100
awaiting first pass
usability × 0.40
+ quality × 0.35
+ performance × 0.25
± compat factor

Usability ratings

Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".

—%no reports yet
Sign in to report whether this part worked for you.
Discussion

Scoped to this part · feeds back into the world's score.

0comments
Sign in to post.sign in
No comments yet. Be the first.