Quick answer: Use a localization library that applies CLDR plural rules via ICU MessageFormat, providing a string for each plural category instead of a binary singular/plural toggle.

Hardcoding plural as count == 1 produces 1 items in English and entirely wrong forms in Russian, Polish, or Arabic. Using ICU MessageFormat with CLDR plural categories selects the right form for every language.

How to fix it

1. Adopt ICU plural rules

Use a localizer that supports ICU MessageFormat plurals, where each language supplies forms for the categories it needs (zero, one, two, few, many, other).

2. Author per-category strings

Give translators a message like {n, plural, one {# item} other {# items}} so they can add the extra forms their language requires instead of a single English-shaped pair.

3. Never hardcode count == 1

Remove direct singular/plural branches in code; route every countable phrase through the plural formatter so the rules live in the translation data, not the source.

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.

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