What causes Unity numbers using the wrong locale separators?

Numbers are formatted with ToString or string concatenation under the invariant or system culture, so the decimal and thousands separators do not match the player's language.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Unity Numbers Showing the Wrong Decimal Separator per Locale

Quick answer: Format numbers with the active locale's CultureInfo using ToString with a format and the culture, and drive the culture from the localization system, not the OS.

A score of 1,000.5 can appear as 1.000,5 or stay English in a German build because the formatting ignores the player's locale. Passing the active CultureInfo to ToString produces the correct separators everywhere.

How to fix it

1. Format with the active culture

Call value.ToString("N1", culture) passing a CultureInfo for the current language instead of relying on the implicit current culture, which may differ from the player's chosen locale.

2. Drive culture from localization

Map your localization system's selected locale to a CultureInfo so number, date, and currency formatting follow the in-game language rather than the device's region settings.

3. Avoid manual concatenation

Never build numbers by inserting commas or periods yourself; that hardcodes one locale's convention and breaks for every other language's separator rules.

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

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.