Quick answer: Add fallback fonts to the FontFile or a FontVariation that cover the missing scripts, and ensure the base font actually contains the glyphs you expect.

Accented European or Cyrillic characters can render as empty boxes when the chosen font does not include them. Adding fallback fonts that cover those scripts replaces the tofu with real glyphs.

How to fix it

1. Add fallback fonts

On the FontFile (or a FontVariation wrapping it) populate the Fallbacks array with fonts that cover the missing scripts, so Godot tries them when the base font lacks a glyph.

2. Verify base font coverage

Confirm the primary font actually contains the characters you need; many display fonts ship Latin-only, so a broader font may be required for the base rather than just fallbacks.

3. Match fallbacks to your locales

Include script-specific fonts for every language you ship (Cyrillic, Greek, CJK, etc.) so no supported translation falls back to tofu at runtime.

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.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.