Quick answer: Set the patch_margin values to the artwork's border thickness, choose the right axis stretch mode, and size the rect larger than the combined margins.
A dialog box built from a NinePatchRect can warp its rounded corners or clip its content when the margins are wrong. Matching the patch margins to the source art and picking the right stretch mode keeps the frame clean.
How to fix it
1. Match the patch margins
Set patch_margin_left/top/right/bottom to the pixel thickness of your border so the corners are excluded from stretching and only the center scales.
2. Pick axis stretch modes
Set axis_stretch_horizontal and axis_stretch_vertical to Stretch or Tile depending on whether the edge art should smear or repeat across the span.
3. Keep the rect bigger than the margins
Ensure the rect's size exceeds left+right and top+bottom margins; otherwise the corners overlap and the center collapses, producing a crushed-looking frame.
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.