Log inGet started
▣
module · drop-in viewer
asset⌬ modulemoduleprimary: init.luau·originates fromworld 2d73066b-0…

hawkmesh

One-paragraph description of what this module provides and who consumes it.

by◐noraellis24·posted 1mo ago
What it does

hawkmesh

One-paragraph description of what this module provides and who consumes it.

Exports

  • M.exampleFn(arg) -> result — what it does and when to call it.
  • M.exampleValue: type — what value it carries.

Usage

Replace <identity> with the string asset.create returned — this module's source path with / written as . and each segment's type suffix dropped, the way a module at /source/lib/thing.module is lib.thing and one at /source/kit.package/thing.module is kit.thing.

local M = require("<identity>")
M.exampleFn("foo")

Notes

  • Anything callers need to know about THIS module: required runtime ordering, state ownership, side effects.

Interface

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

conforms to

zero/source-extract/v2

nonstrict

acc( ) → void

add(a: ?, geom: ?, o: ?, ex: ?, ey: ?, ez: ?, colorFn: ?) → void

Place one part into the accumulator: X→ex, Y→ey, Z→ez, then translate by `o`. `colorFn(localX, localY, localZ, vertexIndex)` decides the colour in the part's OWN frame, where the part's layout is known — that is how the top of a wing is brown and the underside cream without a texture.

argtypedescription
a?
geom?
o?
ex?
ey?
ez?
colorFn?

mirrored(a: ?) → void

The same buffer reflected across X, winding reversed so the reflected copy still faces outward: the left wing is the right wing seen this way.

argtypedescription
a?

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

Concatenate one buffer onto another, offsetting the indices.

argtypedescription
dst?
src?

normalsFor(px: ?, idx: ?) → void

Normals accumulated from the faces of the finished buffer.

argtypedescription
px?
idx?

mix(a: ?, b: ?, t: ?) → void

argtypedescription
a?
b?
t?

ringCos(segments: ?, localIndex: ?) → void

which way a loft ring's vertex faces: 1 across the back, -1 along the belly

argtypedescription
segments?
localIndex?

wingSide(rot: ?) → void

argtypedescription
rot?

onWing(v: ?) → void

argtypedescription
v?

wingOrigin(v: ?) → void

argtypedescription
v?

hawk(opts: ?, opts.flap: ?) →

The whole bird as one geometry, in the flat-array shape `asset.create("mesh", …)` takes — positions, indices, normals, uvs and per-vertex colours. level glide. Omit for the glide.

argtypedescription
opts?
opts.flap?Wings about the shoulder: +1 full up, -1 full down, 0 the

examples

asset.create("mesh", "hawk_flap_1", require("hawkmesh").hawk({ flap = 1 }))

rot(v: ?) → void

rotate a point about the X axis through the shoulder line

argtypedescription
v?

tailRot(v: ?) → void

argtypedescription
v?

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 · pulled in
❒asset
# eaglemesh The harpy eagle's geometry, written as numbers. Three builders make the whole bird and hand back the flat-array `Geom` shape `renderer.mesh.create` and `asset.create("mesh", …)` both take: | Builder | Shape | Used for | |---|---|---| | `loft` | ellipse rings threaded along a spine | body, head, bill, thighs | | `plate` | a surface stated by its leading and trailing edges | wings, tail | | `blade` | a tapered feather, swept and curled | crest, primaries, toes | `M.eagle()` returns every part at once; `M.mirrorX` reflects one across X with its winding reversed, which is how the left wing is the right wing. `M.ANCHOR` says where each part hangs, so the geometry and the rig cannot drift apart. The bird faces its own -Z, spans X, and is about 2.4 m across the wings — a harpy eagle at life size.
▲ 1↓ import
backing path · hawkmesh.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.