Quick answer: Enable 2D pixel snapping in Project Settings, round the camera and sprite positions to whole pixels, and use the canvas_items stretch mode with an integer scale.

As the camera follows the player, pixel-art sprites twinkle and edges crawl. The sprites are landing on fractional pixels each frame.

How to fix it

1. Snap rendering to pixels

In Project Settings enable rendering/2d/snap/snap_2d_transforms_to_pixel and snap_2d_vertices_to_pixel so the renderer rounds positions to whole texels.

2. Round the camera position

Quantize the Camera2D global position to integers each frame (or set its process callback after physics) so scrolling moves in whole-pixel steps, not fractions.

3. Use a consistent stretch setup

Set the stretch mode to canvas_items with an integer scale (or use viewport stretch with an integer scale option) so the whole frame scales by a clean factor.

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.