What causes a cold debuff not clearing near a heat source?

Temperature only accounts for ambient cold and never adds warmth from nearby heat sources, or the debuff is applied after warmth is calculated and overrides it.

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 Cold Status Effect Not Clearing When the Player Stands by a Fire

Quick answer: Sum warmth from active heat sources within range each tick, combine it with ambient temperature, and apply or remove the debuff based on the final value.

A player huddles right next to a roaring campfire but the freezing effect keeps ticking damage. The temperature system is reading ambient cold without ever crediting the fire's heat.

How to fix it

1. Aggregate nearby heat

Each tick, find active heat sources in range and add their warmth, falling off with distance, to the player's effective temperature. Ignoring heat sources is why the debuff never lifts.

2. Compute final temperature first

Resolve ambient plus warmth into one value, then decide the status effect. Applying cold first and warmth second lets a stale debuff override the fix.

3. Require the fire to be lit

Only count heat from sources that are actually burning and fueled. An unlit or fuel-empty campfire should provide no warmth.

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.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.