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

WildlandsPlayer

Everything the person at the keyboard does, on top of the movement the avatar already provides: swinging a tool at what the crosshair is on, hand-gathering loose stone and fiber with E, throwing a Wildcore Orb and resolving the capture, eating, and keeping the survival meters hon…

by◐zakariya·posted 1mo ago
What it does

WildlandsPlayer

Everything the person at the keyboard does, on top of the movement the avatar already provides: swinging a tool at what the crosshair is on, hand-gathering loose stone and fiber with E, throwing a Wildcore Orb and resolving the capture, eating, and keeping the survival meters honest.

Targeting is aim-based, not proximity-based: WildlandsWorld:aimNode scores each node by how directly it lies along the camera's forward, so the tree you look at is the tree you hit.

Attached to the player's avatar body by the scene entrypoint on localPlayerReady. It activates the wildlands input map and needs WildlandsWorld to exist.

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 player. Everything the person at the keyboard does: swinging a tool at a tree or a creature, picking things up, throwing a Wildcore Orb, eating, and keeping the survival meters honest. Movement, jumping and the camera belong to the avatar and the CameraRig the scene authored; this component adds the game on top.

Model

worldComp( ) → void

The world component is re-resolved every time rather than cached. A component that hot-reloads is a NEW instance holding its own state, so a cached handle keeps answering from the old one — reading an emptied node list and silently finding no target, while everything else in this component keeps working.

camPos( ) → void

camForward( ) → void

aimHit(range: ?) → void

What the player is looking at, from the camera, through the world.

argtypedescription
range?

creatureInReach(range: ?) → void

A creature is "in reach" when it is close to the player AND under the crosshair — not merely nearby.

argtypedescription
range?

nodeInReach(range: ?) → void

The node under the crosshair. Aim decides, distance only bounds it.

argtypedescription
range?

toolMesh(kind: ?) → void

argtypedescription
kind?

showTool(kind: ?) → void

argtypedescription
kind?

findBone(e: ?, name: ?, depth: ?) → void

the rig's right shoulder is the nearest thing to a hand this avatar exposes

argtypedescription
e?
name?
depth?

wearSelected(amount: ?) → void

argtypedescription
amount?

swingAt(rec: ?, isCreature: ?) → void

argtypedescription
rec?
isCreature?

gatherHand( ) → void

Hand-gather: loose stones, berries, fiber — one press, one pickup.

throwOrb( ) → void

updateOrbs(dt: ?) → void

argtypedescription
dt?

hotbar(i: ?) → void

argtypedescription
i?

bindInputs( ) → void

on(name: ?, handler: ?) → void

argtypedescription
name?
handler?

awake( ) → void

start( ) → void

nodeInfo(rec: ?) → void

What to call a resource node on the HUD, and what the player should do with it.

argtypedescription
rec?

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.

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

51+items
·
inputmap · born here
❒asset
▲ 0↑ born
◇
component · born here
❒asset
# WildlandsWorld Owns the physical world: it generates the terrain mesh and its heightfield collider, the lake, the desert flat, the ruined colonnade, the forest, the resource nodes and every wild creature, all under one root entity so a reload reclaims the lot. It also keeps the live state of everything it spawned — each node's kind, health and drops, each creature's record — and answers the questions the player component asks: what is under the crosshair, what did that swing hit, where is the nearest creature, and what station is close enough to use. Attached to `wl_host` by the scene's `build.luau`. Fields: `seed` (change it for a different landscape), `buildInEdit` (also generate while authoring), `creatureBudget` and `tickEvery` (how many creatures are simulated and how often far ones are updated).
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
▣
module · born here
❒asset
# wl_land The landscape, as one height function. `height(x, z)` is the authority on where the ground is: the rendered terrain mesh, the physics heightfield, every tree, rock and creature placement and the player's spawn all read it, so what you see and what you stand on are the same surface by construction. Also exposes `normalAt`, `SPAWN` and `spawnY`. Callers: `WildlandsWorld` (terrain, placement), the scene entrypoint (spawn point), `WildlandsPlayer` (lake and terrain references).
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 0↑ born
·
inputbinding · born here
❒asset
▲ 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
▣
module · born here
❒asset
# wl_geo Procedural geometry. Every builder returns a `Geo` — flat `positions`, `normals`, `uvs`, `colors` and `indices` arrays in the shape `renderer.mesh.create` takes, in local space. Vertex colour multiplies the albedo of the `pbr` shader and is read as LINEAR light, so a hex palette must be decoded before it goes in (`wl_creatures` does). Builders: `sphere`, `tube`, `card`, `leaf`, `tree`, `rock`, `grassTuft`, `fern`, `bush`, `structure`, `tool`, `wildcoreOrb`, plus `append` for merging, `box`, `tpos`/`qAxis`/`qMul` for transforms and `recomputeNormals` for displaced surfaces. Callers: `WildlandsWorld`, `WildlandsPlayer`, `wl_character`, `wl_creatures`.
▲ 0↑ born
backing path · wildlands/WildlandsPlayer.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.