What causes save loads breaking from a locale comma decimal separator?

Numbers were written or parsed using the current culture, so a save made on an en-US machine (1.5) fails or misreads on a machine where the decimal separator is a comma.

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 Save Loads Breaking on Systems That Use a Comma Decimal Separator

Quick answer: Always serialize and parse numbers with the invariant culture so a float is written and read identically regardless of the player's regional settings.

Culture-sensitive number formatting writes 1,5 on some machines and 1.5 on others. A save that crosses locales then misparses. Forcing invariant culture makes saves portable.

How to fix it

1. Use invariant culture

Write and read numbers with CultureInfo.InvariantCulture (or your language's equivalent), so the separator is always a dot regardless of the OS region.

2. Prefer a structured format

Serialize with a real JSON/binary library rather than building strings by hand. Proper serializers already use a fixed number format internally.

3. Test under a comma locale

Set the test machine's region to one that uses a comma decimal separator and verify saves still round-trip. This catches the bug before players in those regions do.

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 errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.