Quick answer: Switch to the TextServer Advanced module, enable BiDi/auto text direction on the label, and use a font that contains the required Arabic shaping tables.
Arabic strings in Godot can render as a string of disconnected letters running the wrong way because the basic text server cannot shape complex scripts. Enabling the advanced text server and BiDi handling fixes joining and order.
How to fix it
1. Use TextServer Advanced
Build or use a Godot export that includes the TextServer Advanced module, which provides HarfBuzz shaping and ICU BiDi needed for Arabic letter joining and reordering.
2. Enable BiDi direction
On Label and RichTextLabel set Text Direction to Auto (or Inherited) so the engine detects RTL runs and lays out the visual order correctly.
3. Use a shaping-capable font
Pick an Arabic font that includes the required GSUB/GPOS tables for contextual forms, since a font missing them shows isolated glyphs even with shaping enabled.
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.