We localized multiplayer text and made rule sources mandatory at the same time

Situation

When digitizing a board game, a developer can easily 'rationalize' a rule, especially when an edge case is not immediately at hand. Localization adds another layer because the same rule must be explained clearly in several languages. Without a recorded source, code, UI and copy can gradually become three different versions of the game.

Approach

I moved multiplayer labels onto language keys while keeping domain events language-neutral. For significant rule implementations, we also required a documented source or acceptance reference. The goal was not academic documentation; it was to make later disagreements traceable back to the official rule instead of settling them from memory.

Outcome

Localization stayed out of the domain engine and rule changes became easier to trace. When playtest or client feedback disagreed with current behaviour, the decision no longer depended on intuition about which version sounded more reasonable.