Quick answer: Run Arabic through a complex-text shaping engine (HarfBuzz or your engine's RTL text server) so contextual forms and ligatures are selected before rasterization.

Arabic is cursive: each letter changes shape by position. Without shaping you get isolated forms in the wrong order. Enabling a shaper fixes connection and direction. Here is how.

How to fix it

1. Enable a complex-text shaper

Route Arabic strings through HarfBuzz or your engine's advanced text server so contextual substitution picks initial, medial, final and isolated forms instead of a single glyph per code point.

2. Use a font with Arabic shaping tables

Pick a font that ships the GSUB/GPOS OpenType tables for Arabic; a font without joining rules cannot connect letters even with a shaper present.

3. Apply the bidi algorithm for direction

Reorder the visual run with the Unicode bidi algorithm so the shaped Arabic flows right-to-left and any embedded numbers or Latin keep their own direction.

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 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.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.