What causes Construct 3 particles showing square edges?

The particle object's effect/blend mode is Normal with a texture that has no soft alpha, so each particle draws as a hard opaque quad instead of blending additively.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Construct 3 Particles Showing Square Edges or Wrong Blending

Quick answer: Use a particle image with a soft alpha falloff and set an Additive blend (or an effect like Additive) so overlapping particles blend instead of showing square borders.

Construct 3 particles draw the assigned image with the object's blend mode. A hard-edged image on Normal blend shows squares; a soft alpha image with additive blending looks like proper VFX. Here is how.

How to fix it

1. Use a soft alpha image

Replace the particle image with one that fades to transparent at the edges. A fully opaque square texture always renders as a visible quad no matter the blend.

2. Set additive blending

Add an Additive effect to the Particles object (or set the appropriate blend mode) so overlapping particles brighten and blend, eliminating visible square boundaries for fire/sparks.

3. Enable premultiplied alpha correctly

Ensure the image is imported with proper alpha; a non-premultiplied image with fringing shows dark or square halos even with the right blend mode.

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 Construct 3 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 errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.