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

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.

by◐zakariya·posted 1mo ago
What it does

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).

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 world: terrain, water, forest, resource nodes, creatures. One component owns the whole physical world. It builds everything under a single root entity (so a reload reclaims it), keeps the live state of every resource node and creature, and answers the questions the player component asks: what can I reach, what did I just hit, where is the nearest creature.

ModelHeightfieldColliderCapsuleColliderSphereColliderBoxColliderLight

materials( ) → void

meshOf(g: ?) → void

argtypedescription
g?

buildTerrain( ) → void

buildWater( ) → void

buildVariants( ) → void

Meshes are built once per variant and shared by every placement, so a forest of a hundred trees costs eight meshes and not a hundred.

spawnTree(i: ?, x: ?, z: ?) → void

argtypedescription
i?
x?
z?

spawnRock(i: ?, x: ?, z: ?, big: ?, kind: ?) → void

argtypedescription
i?
x?
z?
big?
kind?

spawnPlant(i: ?, x: ?, z: ?, kind: ?) → void

argtypedescription
i?
x?
z?
kind?

buildGroundCover( ) → void

Grass and flowers are not harvestable, so the whole scattering of them is one merged mesh per chunk: three draw calls for a meadow instead of thousands.

freeSpot(x: ?, z: ?, minDist: ?) → void

argtypedescription
x?
z?
minDist?

scatter( ) → void

height(x: ?, z: ?) → void

argtypedescription
x?
z?

notice(text: ?, kind: ?) → void

argtypedescription
text?
kind?

hurtPlayer(dmg: ?, effect: ?, rec: ?) → void

argtypedescription
dmg?
effect?
rec?

damageCreature(target: ?, dmg: ?) → void

argtypedescription
target?
dmg?

produce(rec: ?) → void

argtypedescription
rec?

onDefeat(rec: ?) → void

argtypedescription
rec?

spawnMob(key: ?, x: ?, z: ?, level: ?) → void

argtypedescription
key?
x?
z?
level?

meadow(x: ?, z: ?, y: ?) → void

argtypedescription
x?
z?
y?

plains(x: ?, z: ?, y: ?) → void

argtypedescription
x?
z?
y?

forest(x: ?, z: ?, y: ?) → void

argtypedescription
x?
z?
y?

mountain(x: ?, z: ?, y: ?) → void

argtypedescription
x?
z?
y?

ridge(x: ?, z: ?, y: ?) → void

argtypedescription
x?
z?
y?

water(x: ?, z: ?) → void

argtypedescription
x?
z?

desert(x: ?, z: ?) → void

argtypedescription
x?
z?

night(x: ?, z: ?, y: ?) → void

argtypedescription
x?
z?
y?

sky(x: ?, z: ?, y: ?) → void

argtypedescription
x?
z?
y?

ruins(x: ?, z: ?) → void

argtypedescription
x?
z?

inZone(habitat: ?, x: ?, z: ?, y: ?) → void

argtypedescription
habitat?
x?
z?
y?

pickSpot(habitat: ?, minFromSpawn: ?, minFromMob: ?) → void

argtypedescription
habitat?
minFromSpawn?
minFromMob?

spawnInHabitat(habitat: ?, key: ?) → void

argtypedescription
habitat?
key?

spawnWildlife( ) → void

buildLandmarks( ) → void

clearWorld( ) → void

build( ) → void

awake( ) → void

update(dt: ?) → void

argtypedescription
dt?

onDestroy( ) → void

bindSky(sky: ?, sun: ?, amb: ?) → void

argtypedescription
sky?
sun?
amb?

bindPlayer(p: ?) → void

argtypedescription
p?

worldRoot( ) → void

nearestNode(pos: ?, range: ?) → void

argtypedescription
pos?
range?

aimNode(pos: ?, fwd: ?, range: ?) → void

What the player is AIMING at, which is not the same as what is nearest: a tree behind you is nearer than the one the crosshair is on. Each node is scored by how directly it lies along the camera's forward within range, so the thing you are looking at is the thing you hit.

argtypedescription
pos?
fwd?
range?

aimCreature(pos: ?, fwd: ?, range: ?) → void

The creature the crosshair is on, with the same cone test.

argtypedescription
pos?
fwd?
range?

nearestCreature(pos: ?, range: ?, wildOnly: ?) → void

argtypedescription
pos?
range?
wildOnly?

creatureNear(pos: ?, range: ?) → void

argtypedescription
pos?
range?

creatures( ) → void

boss( ) → void

nodes( ) → void

strike(rec: ?, toolKind: ?, power: ?) → void

argtypedescription
rec?
toolKind?
power?

hitCreature(rec: ?, dmg: ?) → void

Melee against a creature.

argtypedescription
rec?
dmg?

capture(rec: ?, orbPower: ?) → void

Capture: probability from health, difficulty and the orb's quality.

argtypedescription
rec?
orbPower?

spawnCompanion(uid: ?, x: ?, z: ?) → void

argtypedescription
uid?
x?
z?

despawnCompanion(uid: ?) → void

argtypedescription
uid?

orderCompanion(uid: ?, order: ?) → void

argtypedescription
uid?
order?

companionRecord(uid: ?) → void

argtypedescription
uid?

structureMesh(kind: ?) → void

A placed piece is a real entity with a collider, recorded in the save so it comes back on load. Positions are snapped to a half-metre grid so walls line up with each other.

argtypedescription
kind?

placeStructure(id: ?, x: ?, z: ?, yaw: ?) → void

argtypedescription
id?
x?
z?
yaw?

restoreStructures( ) → void

stationNear(pos: ?, kind: ?, range: ?) → void

What station, if any, is close enough to the player to use.

argtypedescription
pos?
kind?
range?

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.

67+items
◐
material · born here
❒asset
▲ 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
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 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_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
◐
material · born here
❒asset
▲ 0↑ born
▣
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
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◐
material · 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
backing path · wildlands/WildlandsWorld.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.