Quick answer: Fire a locale-changed event when the language changes and have every text widget subscribe to it, re-resolving its key and rebuilding layout on the spot.

Players expect the menu they are looking at to switch language instantly, not on the next screen open. The fix is an event that tells live widgets to refresh. Here is how.

How to fix it

1. Emit a global locale-changed signal

When the user picks a new language, set the active locale then broadcast a single event such as OnLocaleChanged rather than assuming menus will rebuild themselves.

2. Subscribe each localized widget

Have every label and button that holds a translation key listen for the event and re-resolve its string from the table, so on-screen text updates without closing the menu.

3. Re-run layout after the text changes

Because translated lengths differ, call your layout/auto-size pass after refreshing text so widths and wrapping recompute instead of clipping the new strings.

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.