Quick answer: Assign a GradientTexture1D to the process material's Color Ramp (or Color Initial Ramp), and ensure the draw material uses vertex color and does not override it.

Godot drives per-lifetime color through a ramp texture in the process material, applied as vertex color on the draw mesh. A missing ramp or an overriding material hides it. Here is how.

How to fix it

1. Set the Color Ramp

In the ParticleProcessMaterial assign a GradientTexture1D to Color Ramp. This gradient maps to each particle's lifetime; an empty ramp leaves them their default color.

2. Use vertex color in the draw material

The ramp is passed as vertex color, so the draw mesh's material must use Vertex Color as Albedo (StandardMaterial3D has a toggle) or a shader that reads COLOR.

3. Check initial vs over-lifetime ramp

Color Initial Ramp sets the spawn color; Color Ramp animates over life. Use the over-lifetime ramp for fade-outs, and do not let a solid Albedo color multiply it to nothing.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.