Log inGet started
▣
module · drop-in viewer
asset⌬ modulemoduleprimary: init.luau·originates fromworld 5164eb76-1…

screens

One-paragraph description of what this module provides and who consumes it.

by◐Cxrn·posted 1mo ago
What it does

screens

One-paragraph description of what this module provides and who consumes it.

Exports

  • M.exampleFn(arg) -> result — what it does and when to call it.
  • M.exampleValue: type — what value it carries.

Usage

Replace <identity> with the string asset.create returned — this module's source path with / written as . and each segment's type suffix dropped, the way a module at /source/lib/thing.module is lib.thing and one at /source/kit.package/thing.module is kit.thing.

local M = require("<identity>")
M.exampleFn("foo")

Notes

  • Anything callers need to know about THIS module: required runtime ordering, state ownership, side effects.

Interface

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

conforms to

zero/source-extract/v2

game.screens — the interface slice of Mario Kart OrigoZ. The screens themselves live on the Screens component, which this spawns on every scene load: a UI needs a persistent owner for its callbacks, and a component is that owner.

Screens

mount( ) → void

Slice entry: stand the screens up.

view( ) → string

Which menu page is up: title, controls or select.

show(page: string) → void

Put a page up by name (title, controls, select).

argtypedescription
pagestring

Sub-parts

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

11items
◇
component · born here
❒asset
# screens — everything the player reads Two screens, both owned by the **Screens** component (which the slice's module spawns on every scene load — a UI needs a persistent owner for its callbacks): | Screen | Shows | |---|---| | `mko_menu` | The title, the CONTROLES window, and the circuit select. | | `mko_hud` | The lap/point counter, the millisecond timer, the item slot, the countdown, and the finish card. | ## The flow ``` title --J--> controles --Comenzar/J--> select --a circuit--> countdown --> race --> finish ``` **J** advances (its own `menu.inputMap`), and every button is a real click target: `comenzar`, `pick_cheep`, `pick_mumu`, `pick_arcoiris`, `again`. Choosing a circuit calls `Core.selectCircuit(id)` + `Core.beginRace()`; the tracks lay the circuit and the kart is placed on its line. The menu screen is hidden and its scheme released while the race runs, and the HUD takes over. The menu map deliberately does **not** suppress the driving scheme: the kart already ignores the wheel unless a race is on, so a menu that is up can never be a kart that cannot move. ## Look The palette of `design/references/02-title-screen.png`: a blue title bar, white panels, chunky type, and an orange **COMENZAR** button, with the type over the live world rather than over a flat colour. ## API ```lua local S = Core.system("screens") S.show("title" | "controls" | "select") S.view() -- which page is up ```
▲ 0↑ born
▣
module · born here
❒asset
# core The shared contract of **Mario Kart OrigoZ**. Every slice reads its rules here, so no slice hard-codes a number that belongs to the game. `require("game.core")` from anywhere in this world. ## What it holds | Field | What it is | |---|---| | `TITLE`, `PROMPT`, `ART` | The game's name, the *pulsa J para jugar* prompt, and the art-direction sentence — word for word from the reference pass, reused by every prompt. | | `CIRCUITS` | The three circuits: id, name, laps, layout (`ring` / `square` / `ribbon`), racing surface, what lies beyond the edges, and half-width. | | `KART` | How a kart feels: max speed, acceleration, braking, turn rates, hop and gravity, drift multipliers, trick spin. | | `SURFACE` | What each surface does to you: `road` 100%, `water` 75%, `grass` 50%, `space` falls. | | `SPARK` | The drift charge table: blue at 1.0s (0.5s boost), orange at 2.5s (1.25s), rainbow at 4.0s (2.5s). | | `BOOST` | Trick 0.75s, mushroom 2.0s, feather 2.0s. | | `ITEMS` | Crate respawn (8s) and the mushroom / feather odds. | | `RESCUE` | How Lakitu puts you back: drop height, lift speed, lift duration. | | `PHASE`, `flow`, `race` | The flow state machine and the live race clock. | | `records` | The best time on each circuit, kept in `runtime_data.world` — shared and durable. | ## API - `M.circuits()`, `M.circuit(id)`, `M.circuitIndex(id)` - `M.register(name, api)` / `M.system(name)` — how slices reach each other - `M.on(name, fn)` / `M.emit(name, payload)` — the slices' event bus (`phase`, `circuit`, `lap`, `crate`, `boost`, `rescue`, `finish`) - `M.setPhase(p)`, `M.selectCircuit(id)`, `M.openControls()`, `M.beginRace()`, `M.startRace()`, `M.tick(dt)`, `M.reachPoint(total)`, `M.finishRace()` - `M.records.get(id)` / `M.records.set(id, ms)` / `M.records.all()` - `M.formatTime(ms)` → `"00:45.678"`, `M.countdownLabel(seconds)` - `M.clamp`, `M.lerp`, `M.approach` ## Who reads what - **kart** — `KART`, `SURFACE`, `SPARK`, `BOOST`, `RESCUE`, `race`. - **tracks** — `CIRCUITS`, `SURFACE`, `reachPoint`, `PHASE`. - **items** — `ITEMS`, `BOOST`, `FEATHER_LIFT`, `emit("crate")`. - **screens** — `flow`, `race`, `records`, `formatTime`, `PHASE`. - **audio** — `on("phase")`, `on("boost")`, `on("crate")`, `on("finish")`.
▲ 0↑ born
backing path · game/screens.module

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.