[1.1.0][5d33] Selection of localisation string decided by content of the string D:

[tom_jones]

edit: to clarify, this behavior is exhibited when .yml files are placed in 'localisation' folder. The files which are put in 'localisation/replace' sub-folder seem to overwrite content of strings without issue. (edit 2: scratch that, if more than one file placed in 'replace' sub-folder tries to replace the same string, the game exhibits this behavior as well)

tl;dr: if more than one localization entry is assigned to a string (e.g. if a mod tries to replace default text) the game appears to decide whether to replace the first entry based on which of the strings comes first in alphabetical order.

I wish I was making this shit up. It's like.. there must be some actual code which does it vs a simple re-assignment so dear gods, why

Proof:

GER_nav_bomber_equipment_1:0 "Heinkel He 59"
GER_nav_bomber_equipment_1_short:0 "He 59"

effect: nope. the game sticks with the vanilla entry.

GER_nav_bomber_equipment_1:0 "A Heinkel He 59"
GER_nav_bomber_equipment_1_short:0 "A He 59"

effect: yup. you can have your custom string, as long as you go for AAAAAAAAAAA cheap classified ads tricks.

let's see, is it case-sensitive?

GER_nav_bomber_equipment_1:0 "a Heinkel He 59"
GER_nav_bomber_equipment_1_short:0 "a He 59"

effect: yup (in ASCII table and more sophisticated derivatives lowercase 'a' comes after capital 'D')

I guess this explains the other issue I've reported a bit back...

 

[Axe99]

Very impressive testing there Tom .

 

[Sleight of Hand]

@podcat
@Archangel85
@Havebeard

This still appears to be the case; wondered if one of you would perhaps be kind enough to take a look?

 

[Havebeard]

You are not supposed to have duplicate loc key entries. If you don't have a errors in text.log I don't know what went wrong.