Quick answer: Use GPUParticles2D with Trail Enabled and a sufficient Trail Length and sections, or fake a CPU trail with a Line2D fed by particle positions.

Trails in Godot are a GPUParticles feature; CPUParticles does not draw them the same way. Switching node type and enabling trail length produces a visible trail. Here is how.

How to fix it

1. Use GPUParticles2D for trails

Switch to GPUParticles2D, which exposes a Trails section. Enable Trails, set a Trail Length (seconds) and section count so each particle leaves a connected strip.

2. Assign a trail-capable material

Set a ParticleProcessMaterial and a draw mesh/texture; the trail uses the particle texture stretched along the path, so a blank material shows nothing even with trails on.

3. Or fake it with Line2D

If you must stay on CPU, push recent particle positions into a Line2D each frame and fade its alpha, which approximates a trail without GPU trail support.

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.

A crash you can name from its stack trace is a crash you can usually fix in minutes.