What causes a Construct 3 System Compare Two Values condition never passing?

The two expressions never satisfy the chosen comparison, often due to a type mismatch (text vs number), a floating-point exact-equality test, or referencing the wrong variable.

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 a Construct 3 System Compare That Is Never True

Quick answer: Use the right comparison operator, compare numbers as numbers (not strings), avoid exact equality on floats, and watch the actual values with the debugger.

A Compare Two Values that never fires usually has a type or precision problem, or points at the wrong value. Inspecting the operands fixes it. Here is how.

How to fix it

1. Check value types

Comparing a number to a text version of it (for example 5 vs "5") can fail. Convert with int() or str() so both sides are the same type before comparing.

2. Avoid exact float equality

Testing = on a value that accumulated from additions rarely lands exactly. Compare with a small tolerance (for example abs(a-b) < 0.01) or use <= / >= instead.

3. Watch the operands

Use the Construct 3 debugger to inspect the live values of both expressions. Often the condition is correct but one operand is not the variable you assumed.

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.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.