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 Godot RichTextLabel Dialogue Text Not Clearing Between Lines

Q: What causes Godot RichTextLabel dialogue text not clearing between lines?

Each line is added with append_text or bbcode_text +=, which accumulates, and the label is never cleared before the next line, so old text piles up.

Quick answer: Clear the RichTextLabel before each new line with clear() (or assign text fresh), then append the new line so only the current line shows.

Dialogue text stacking up in a RichTextLabel means lines are appended without clearing. Resetting the label per line fixes it. Here is how.

How to fix it

1. Clear before each line

Call label.clear() at the start of each new line before appending, so the previous line's content is removed instead of accumulating below it.

2. Reset visible_characters too

After clearing and appending the new text, reset visible_characters = 0 so the typewriter reveal restarts from the beginning of the new line rather than showing it instantly.

3. Avoid mixing text and append_text

Set the line either by assigning text fresh or by clear-then-append, not both; mixing the two on the same label can leave stale parsed content behind.

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.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.