godot-ui-rich-text

Use the visible_characters property with per-character indexing rather than modifying the text string each frame. For pause and speed event tags like [pause] and [speed], use a dedicated typewriter controller script instead of visible_ratio, which is unreliable for per-character logic.

Wrap text in [url=payload] tags and connect the meta_clicked signal to a handler. Keep heavy logic off the main thread by emitting a command from the handler, and add hover feedback so players know the text is clickable.

Extend RichTextEffect, set a bbcode identifier, and implement _process_custom_fx to modify each CharFXTransform. You must register the effect instance in the RichTextLabel custom_effects list or via install_effect() for it to render.

No, raw user input is unsafe because players can inject tags like [img] or [color=transparent] to break your UI. Always run player-typed strings through a BBCode sanitizer before assigning them to RichTextLabel.text.

Absolute pixel sizes in [img] tags fail on higher resolutions. In Godot 4.7 use width_unit and height_unit with RichTextLabel.ImageUnit, and scale images dynamically to match the runtime font line height.

Use visible_ratio with a Tween for simple whole-text fades. Use visible_characters when you need per-character control such as pause or speed event tags in dialogue, since visible_ratio cannot handle indexed character logic.