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

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.

by◐zakariya·posted 1mo ago
What it does

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.

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 — procedural geometry. Every builder returns a `Geo`: flat arrays in the shape renderer.mesh.create takes (positions / normals / uvs / colors / indices), in LOCAL space. Vertex colour RGB multiplies the albedo of the pbr shader, so one material carries bark, leaf, hide and stone variation on the same draw.

new( ) → void

push3(t: ?, x: ?, y: ?, z: ?) → void

argtypedescription
t?
x?
y?
z?

vertex(g: ?, x: ?, y: ?, z: ?, nx: ?, ny: ?, nz: ?, u: ?, v: ?, r: ?, gg: ?, b: ?, a: ?) → void

argtypedescription
g?
x?
y?
z?
nx?
ny?
nz?
u?
v?
r?
gg?
b?
a?

tri(g: ?, a: ?, b: ?, c: ?) → void

argtypedescription
g?
a?
b?
c?

count(g: ?) → void

argtypedescription
g?

recomputeNormals(g: ?) → void

Area-weighted normals from the triangles. A displaced surface shaded with the smooth analytic normals of the sphere it started as reads as a ball no matter how far it was pushed, so anything deformed gets its normals rebuilt here.

argtypedescription
g?

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

argtypedescription
x?
y?
z?

qAxis(ax: ?, ay: ?, az: ?, angle: ?) → void

argtypedescription
ax?
ay?
az?
angle?

qMul(a: ?, b: ?) → void

Quaternion product, exposed so callers can compose their own orientations.

argtypedescription
a?
b?

qmul(a: ?, b: ?) → void

argtypedescription
a?
b?

qrot(q: ?, x: ?, y: ?, z: ?) → void

argtypedescription
q?
x?
y?
z?

xformPoint(t: ?, x: ?, y: ?, z: ?) → void

argtypedescription
t?
x?
y?
z?

xformDir(t: ?, x: ?, y: ?, z: ?) → void

argtypedescription
t?
x?
y?
z?

append(dst: ?, src: ?, t: ?, tint: ?) → void

Copy `src` into `dst`, transformed. `tint` (optional {r,g,b}) multiplies colour.

argtypedescription
dst?
src?
t?
tint?

sphere(opts: ?) → void

A UV sphere with optional radial displacement. Colour is a function of the unit direction, so a material can darken a belly and lighten a back.

argtypedescription
opts?

tube(pts: ?, radii: ?, sides: ?, opts: ?) → void

A swept tube along a polyline. `pts` are {x,y,z}; `radii` one per point. `sides` is even so the colour seam is not on the front face.

argtypedescription
pts?
radii?
sides?
opts?

card(corners: ?, color: ?) → void

A flat card (leaf / blade / feather / plank) given three or four corners in local space. Three corners makes a triangle, which is what a feather or a fin needs; four makes the quad that a leaf uses.

argtypedescription
corners?
color?

leaf(len: ?, wid: ?, color: ?, q: ?, px: ?, py: ?, pz: ?) → void

A leaf: a pointed oval card with a midrib fold, oriented by a quaternion.

argtypedescription
len?
wid?
color?
q?
px?
py?
pz?

barkColor(seed: ?) → void

argtypedescription
seed?

tree(seed: ?, opts: ?) → void

Returns { bark = Geo, leaves = Geo }. `opts.kind` picks the silhouette. The crown is one continuous volume sampled with leaf cards rather than a handful of separate balls, which is what makes it read as a tree.

argtypedescription
seed?
opts?

_shellness(px: ?, py: ?, pz: ?) → void

how far inside the crown a point is: 1 at the surface, 0 at the core

argtypedescription
px?
py?
pz?

rock(seed: ?, opts: ?) → void

argtypedescription
seed?
opts?

color(nx: ?, ny: ?, nz: ?) → void

argtypedescription
nx?
ny?
nz?

color( ) → void

grassTuft(seed: ?) → void

argtypedescription
seed?

fern(seed: ?) → void

argtypedescription
seed?

bush(seed: ?) → void

argtypedescription
seed?

color(nx: ?, ny: ?) → void

argtypedescription
nx?
ny?

box(g: ?, cx: ?, cy: ?, cz: ?, sx: ?, sy: ?, sz: ?, c: ?) → void

argtypedescription
g?
cx?
cy?
cz?
sx?
sy?
sz?
c?

structure(kind: ?) → void

argtypedescription
kind?

tool(kind: ?) → void

A tool held in the hand. `kind` = axe | pick | spear | torch

argtypedescription
kind?

color( ) → void

color(nx: ?, ny: ?) → void

argtypedescription
nx?
ny?

wildcoreOrb(open: ?) → void

The WILDCORE ORB: two hinged shells, a metal band, an energy core. Returns { shell = Geo, band = Geo, core = Geo } so each can wear its own material.

argtypedescription
open?

color(nx: ?, ny: ?, nz: ?) → void

argtypedescription
nx?
ny?
nz?

color(v: ?, u: ?, nx: ?, ny: ?, nz: ?) → void

argtypedescription
v?
u?
nx?
ny?
nz?

color(nx: ?, ny: ?) → void

argtypedescription
nx?
ny?

Sub-parts

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

3items
This part has no composite children. See the Files segment for its leaf payloads.
backing path · wildlands/wl_geo.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.