Quick answer: Enable autowrap on the Label, constrain it inside a safe-area margin, and cap the displayed line length so text always wraps within the visible region.
Subtitles that bleed off the edge are unreadable, and they get worse after translation. Wrapping inside a safe area fixes it. Here is how.
How to fix it
1. Turn on autowrap
Set the subtitle Label.autowrap_mode to AUTOWRAP_WORD_SMART so long lines break on word boundaries instead of running past the edge.
2. Constrain to a safe area
Wrap the label in a MarginContainer with margins of roughly 5% of the viewport on each side so text clears TV overscan and rounded display corners.
3. Cap line length and lines
Limit each cue to about two lines and 40 characters per line; split longer dialogue into sequential cues rather than one giant block.
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.