Data mods containing Loc strings not getting correctly activated

:arrow_forward: GAME INFORMATION

  • GAME BUILD #: Current
  • GAME PLATFORM: Steam
  • OPERATING SYSTEM: Windows 10

:arrow_forward: ISSUE EXPERIENCED

Data mods containing Loc strings not getting correctly activated in lobbies

:arrow_forward: FREQUENCY OF ISSUE

ALWAYS

:arrow_forward: REPRODUCTION STEPS

Try to host and start a mod with Loc Strings

:arrow_forward: EXPECTED RESULT

Data mods containing Loc string should get activated in lobbies

It was supposed to be fixed, but it still isn’t.

@StepS7578 @Felizon89 @IvanHCastro

If by “not getting activated,” you mean an error (version conflict) occurs when starting a multiplayer lobby, I have noticed that this occurs when both of the conditions below are met. (It’s been a while since I tested this, but below is the behavior I noticed about six months or so ago)

  1. The data mod provides language files for some, but not all languages
  2. Either the host has their game interface language set to a langauge the mod supports and one or more players has the language set to a language the mod doesn’t provide, or the opposite (the host uses a language the mod doesn’t support but one or more players uses a language it does support).

To give a concrete example, let’s say that a certain mod only provides language files for English.
An error will occur in the following situations:

  1. The host has the game language set to English, but one of the players joining the lobby has the game language set to French.
  2. The host has the game language set to French, but one of the players joining the lobby has the game language set to English.

An error would not occur in the following situations:

  1. All players including the host has the game language set to English.
  2. All players including the host has the game language set to French.

I have also never noticed any issues when a mod provides language files for all languages.

No, that’s not what I’m talking about—you’re mistaken. This bug was introduced a few patches ago and was supposed to have been fixed.

Also, this isn’t a version conflict issue. If it were, I would’ve already resolved it.