What version did the issue occur in?
No response
Description
There is an issue with localization files inside modules. Module localization works in general, but if a module contains a localization file with exactly the same relative path and filename as a file in the core content, the module’s localization file is silently ignored.
I think there should be either an automated test or, at the very least, a clear warning or error message when such a conflict occurs. Right now, it is difficult to understand why the localization is not being loaded, since the conflict is not obvious.
As a result, modular localization loses much of its purpose. Module developers still have to use a differently named directory, like "_Shitcode", just to avoid conflicts with core localization files.
Reproduction
- Create a localization file in the core content.
- Create a module localization file with exactly the same relative path and filename.
- Add or change a localization string in the module file.
- Start the game and check the affected string.
- Notice that the module localization file is ignored and no warning or error is shown.
Additional Context
No response
What version did the issue occur in?
No response
Description
There is an issue with localization files inside modules. Module localization works in general, but if a module contains a localization file with exactly the same relative path and filename as a file in the core content, the module’s localization file is silently ignored.
I think there should be either an automated test or, at the very least, a clear warning or error message when such a conflict occurs. Right now, it is difficult to understand why the localization is not being loaded, since the conflict is not obvious.
As a result, modular localization loses much of its purpose. Module developers still have to use a differently named directory, like "_Shitcode", just to avoid conflicts with core localization files.
Reproduction
Additional Context
No response