Log inGet started
What it does

plasmaBolt

A slow, self-lit bolt crossing a span. A round pulsing core carries a short wake behind it, sheds motes as it goes and drags a point light along with it, so it reads as energy in flight rather than as a round.

effects.play("@builtin::systems.effects.combat.plasmaBolt", {
    params = { from = emitter.position, to = target.position, color = { 0.6, 0.3, 1.0 } },
})

Parameters

ParameterTypeDefaultRangeWhat it changes
fromvec3{0, 0, 0}world spaceWhere the bolt is fired from.
tovec3{0, 0, 25}world spaceWhere it ends.
speednumber42.01.0 – 400.0How fast it crosses the span, in metres per second. Slow enough to watch is what makes it a bolt.
sizenumber0.340.03 – 4.0Radius of the glowing core, in metres. The wake, the motes and the light's range are proportioned off it.
colorcolor{0.34, 0.82, 1.0}linear 0..1Colour of the plasma. Cold runs blue, ion runs green, antimatter runs violet.
pulseRatenumber7.00.0 – 40.0How many times a second the core swells and dims. 0 holds it steady. The rate is in hertz whatever the flight time is.
lightnumber1.00.0 – 8.0Strength of the light it carries. At 0 no light entity is spawned.

Cost

<!-- cost: quoted verbatim from effect.yaml -->
gpuMsvramBytesmeasuredOn
0.0176020see effect.yaml

The size is what the effect's own backends report they hold at a representative instant — handle:stats().bytes — read identically on every engine, in every scene and on every repeat. The emitter vertex buffers an effect draws from come out of a pool shared across the process that grows in chunks, so a renderer.gpuMemory() delta taken around one play is that pool's growth as much as the effect's; what those buffers cost at the declared slot counts is below. The span is the median of five interleaved idle/loaded windows of the frame's measured GPU pass sum, which read 0.000 ms with a spread of about 0.008 ms: the effect costs less GPU time than that instrument resolves, and 0.01 is the bound the reading supports.

76,020 bytes of emitter simulation state, plus 68,400 bytes of emitter vertex geometry — the mote emitter's 90 declared slots at 760 bytes each. Both are the same at every size and speed.

Telling it apart from the tracer

stats() reports coreRadius, pulseRate, pulse and motesAlive, none of which a tracer has, and its flightTime over the same span is roughly six times a tracer's at the declared defaults. The bolt leases an emitter and spawns a moving light; the tracer leases geometry and nothing else.

What it draws with

AssetRole
combat/materials/combat_glowthe family's one additive material — the core's bloom form and the wake's bolt form
combat/glowthe module that leases the rod and writes the lanes

See also

  • @builtin::systems.effects.combat.tracer — the ballistic round.
  • guides { path: "topics/visual-effects" }.

Interface

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

This asset doesn't declare a schema or structured payload.

Sub-parts

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

0items
This part has no composite children. See the Files segment for its leaf payloads.
This part has no leaf payloads.

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.