Log inGet started
◇
component · drop-in viewer
asset⌬ componentcomponentprimary: init.luau·originates fromworld f1825862-d…

ci_screens

<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this component provides and who consumes it, then delete both comment lines. -->

by◐Hijisou·posted 1mo ago
What it does

ci_screens

<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this component provides and who consumes it, then delete both comment lines. -->

TODO: describe this component.

Interface

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

conforms to

zero/source-extract/v2

Crystal Isle — what is on the glass: the shard HUD and the title screen.

makeHud( ) → void

refreshShards(n: ?) → void

argtypedescription
n?

workOutPrompt( ) → void

onEdge(control: ?, fn: ?) → void

A control's press is read through `onInput`'s active flag on its rising edge as well as through `onPressed`: a press that begins and ends inside one frame is delivered to the former every time and to the latter only sometimes, and a tap on a phone is exactly that short.

argtypedescription
control?
fn?

menuText( ) → void

refreshMenu( ) → void

makeTitle( ) → void

setTitle(up: ?) → void

argtypedescription
up?

choose( ) → void

awake( ) → void

start( ) → void

update(dt: ?) → void

argtypedescription
dt?

onDestroy( ) → void

Sub-parts

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

7items
▣
module · born here
❒asset
# crystal_isle.Core The one module every slice of Crystal Isle reads, and the one thing they agree through. ## What it holds - **`ISLAND`** — the plateau's radius, the walkable half-width, the top's height. - **`POS`** — where Crystal Haven stands and where a player arrives. - **`CRYSTALS`** — the mining rule: a cluster breaks in 2 to 5 hits, how many shards a hit and a break are worth, how far off a crystal is visible, how near one raises your staff, how long a mined cluster takes to grow back, and how many clusters the island carries. - **`PICKAXES`** — the four staffs, cheapest first: `cost`, `hits` per crystal, `shardsPerHit`, `shardsOnBreak`, the beam colour, and a line of flavour. - **`DRESSES`** — the five outfits, each with a `cost`, a blurb and the `colors` its mesh is built from. - **`PALETTE`** — the whole island's colours, so every screen and material stays in one evening. ## The live state Kept as attributes on the entity **`crystal_isle_state`** — a LOCAL entity, so every peer keeps its own shard purse and its own wardrobe while standing on the same island: | Attribute | | | |---|---|---| | `shards` | number | how many crystal shards you carry | | `pickaxe` | number | which `PICKAXES` entry you hold (1-based) | | `dress` | string | the `DRESSES` id worn | | `owned` | string | comma-separated ids of every dress owned | ## Who consumes it Every slice: `ci_mining` mines through `M.addShards`, `ci_shop` buys through `M.buyPickaxe` / `M.buyDress` / `M.equipDress`, `ci_hero` dresses the body from `M.dress()`, `ci_screens` draws the HUD from `M.shards()` and subscribes with `M.subscribe`, `ci_island` lays the island out from `M.ISLAND` and `M.POS`. ## The rule **Nothing writes those four attributes except this module.** Mining calls `M.addShards`; the shop calls `M.spend` / `M.buyPickaxe` / `M.buyDress` / `M.equipDress`. That is what keeps the two halves of the game — what you dig up and what you spend it on — agreeing with each other.
▲ 0↑ born
backing path · crystal_isle/ui/ci_screens.component

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.