What causes a Godot RichTextLabel rendering BBCode literally?

BBCode is disabled on the RichTextLabel or the text was assigned to the plain text property, so tags like [b] and [color] print as literal characters instead of formatting the text.

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 Showing BBCode Tags as Plain Text

Quick answer: Enable BBCode Enabled on the RichTextLabel and assign the markup through the text property (or append_text) so the tags are parsed and applied.

Markup such as [color=red] can appear as raw text in a Godot RichTextLabel when BBCode parsing is off. Turning on BBCode and assigning text through the correct property makes the formatting render.

How to fix it

1. Enable BBCode

On the RichTextLabel, turn on BBCode Enabled (or set bbcode_enabled = true in script) so the node parses tags instead of treating them as literal characters.

2. Assign via the right property

Set the markup through the text property or call append_text; with BBCode enabled these parse tags, whereas appending raw segments without parsing shows them literally.

3. Close and balance tags

Make sure every tag like [b] has a matching [/b]; unbalanced or misspelled tags can break parsing and cause the rest of the string to render as plain text.

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.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.