How to Fix a Blurry or Wrongly Stretched Border on a Construct 3 9-Patch

A panel built from a Construct 3 9-Patch shows stretched, soft corners or a smeared border when resized. The margins or edge fill mode are wrong.

How to fix it

1. Set the corner margins correctly

In the 9-Patch image editor drag the margin guides so the corners cover only the fixed art. Too-small margins let the corner stretch with the body.

2. Pick a tiling edge fill

Set the edges' fill mode to Tile (or Tile with seams) instead of Stretch so a textured border repeats crisply rather than smearing.

3. Avoid fractional scale

Keep the object at integer sizes and the layout scale at whole factors so border pixels are not interpolated and softened.

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.