Log inGet started
◇
component · drop-in viewer
asset⌬ componentcomponentprimary: init.luau·part ofother @wildlands·originates fromworld 63a0f4f3-3…

WildlandsHUD

Every screen in the game: the HUD (health, stamina and hunger bars, the nine-slot hotbar with counts and durability, the quest tracker, the boss bar, notices, and the crosshair readout naming whatever is targeted and what to do with it) and the panel that holds the inventory, cra…

by◐zakariya·posted 1mo ago
What it does

WildlandsHUD

Every screen in the game: the HUD (health, stamina and hunger bars, the nine-slot hotbar with counts and durability, the quest tracker, the boss bar, notices, and the crosshair readout naming whatever is targeted and what to do with it) and the panel that holds the inventory, crafting, the creature team, the build menu, the map and the pause menu.

A screen is a pure function of game state and is only redrawn when a signature of that state changes, so a still frame costs nothing.

Attached to its own wl_hud_host entity by the scene entrypoint. It reads state from wl_core and drives actions through WildlandsWorld.

Interface

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

conforms to

zero/source-extract/v2

WILDLANDS — the interface. One component owns every screen: the HUD (bars, hotbar, quest tracker, notices, boss bar), and the panel that holds the inventory, crafting, the creature team, the build menu, the map and the pause menu. A screen is a pure function of game state, so a redraw is only queued when something changed.

pct(v: ?, max: ?) → void

argtypedescription
v?
max?

round(v: ?) → void

argtypedescription
v?

bar(id: ?, label: ?, value: ?, max: ?, colour: ?, width: ?) → void

argtypedescription
id?
label?
value?
max?
colour?
width?

icon(name: ?, tint: ?, size: ?) → void

argtypedescription
name?
tint?
size?

slotCell(i: ?) → void

argtypedescription
i?

hudTree( ) → void

costRow(cost: ?, ok: ?) → void

argtypedescription
cost?
ok?

stationNear(kind: ?) → void

argtypedescription
kind?

inventoryPanel( ) → void

craftPanel( ) → void

teamPanel( ) → void

buildPanel( ) → void

mapPanel( ) → void

toMap(wx: ?, wz: ?) → void

argtypedescription
wx?
wz?

pausePanel( ) → void

panelTree( ) → void

signature( ) → void

redraw(force: ?) → void

argtypedescription
force?

placeStructure(id: ?) → void

argtypedescription
id?

onCallback(id: ?, data: ?) → void

argtypedescription
id?
data?

awake( ) → void

update(dt: ?) → void

argtypedescription
dt?

editorUpdate(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.

Showing up to 3 levels deep. Open a part to see what it holds further down.

11+items
▣
module · born here
❒asset
# wl_creatures The twelve species: their anatomy, their rigs, their animation, their AI and their abilities. A creature is a small hierarchy of entities — torso, neck, head, legs, tail, wings, fins and ornaments — so every part can be articulated. `CR.rig(key)` builds that geometry once per species and caches it; `CR.spawn` assembles an instance; `CR.tick` runs the state machine and `CR.animate` poses the joints. `CR.hit` is the single damage entry point, so armour, shields, the hurt state and defeat behave the same whoever deals the damage. Callers: `WildlandsWorld`.
▲ 0↑ born
▣
module · born here
❒asset
# wl_defs Static game data for WILDLANDS and nothing else: tuning constants, the item catalogue, crafting recipes, smelting rules, quest definitions and the structure table. No engine state lives here, so it is safe to require from anywhere. `wl_creatures` also re-exports the species table, but the creatures' own anatomy and rules live in that module. Callers: `wl_core` (items and recipes), `WildlandsWorld` (structures, tuning), `WildlandsHUD` (recipes and item icons), `WildlandsPlayer` (tuning).
▲ 0↑ born
▣
module · born here
❒asset
# wl_core The one piece of shared runtime state. Components run in separate VMs, so anything they must agree on lives here: inventory, hotbar, survival meters, quest progress, captured companions, placed structures and the save file. The state table comes from `modules.state()`, so a hot reload of this module keeps everything. The save is written to `/source/local/wildlands_save.json` and read back by the scene entrypoint on load. Callers: `WildlandsPlayer`, `WildlandsHUD`, `WildlandsWorld`, `wl_creatures` (loot and companion records) and the scene entrypoint.
▲ 0↑ born
backing path · wildlands/WildlandsHUD.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 on this asset or on the parts this page shows. Parts it leaves out are not counted here.
⌬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.