Thank you for the report, I'll check it out later. It is a very strange bug since I didn't override any trigger, but I'll do more testing.

Hi there,
Thank you for maintaining the English translation for this great mod!
I encountered an issue where the "Promote a Consort" event is visible, but choosing an option does nothing. I checked the error.log and found a recurring parsing error:
code
Code
[persistent.cpp:88]: Parsing Error. File: "events/ms_evt_consort_choose.txt", Error: Unknown effect type. Key: ms_set_consort_effect, near line: 34
[persistent.cpp:88]: Parsing Error. File: "events/ms_evt_disaster.txt", Error: Unknown effect type. Key: ms_set_consort_effect, near line: 552
The game doesn't recognize the scripted effect ms_set_consort_effect, which is called in several event files. This is because the file that defines this effect in the English translation seems to be an older version and is missing the necessary definitions.
Solution:
The problem was completely resolved on my end by replacing the scripted effects file in the English translation's common/scripted_effects/ folder with the corresponding file from the latest version of the original (main) mod.
Including the updated scripted effects file in the next release of the translation patch should fix this bug.
Hope this helps, and keep up the great work!

Hello @Carlist and thank you for the help! I actually know which file you meant, it's the "ms_efx_1named.txt" file. I actually have already included the latest version of that file into my mod, so I'm actually confused if this is really the cause of the choose consort button not working. I will try testing this issue.

Hello @Carlist, so I managed to fix this decision not by adding the event files like you suggest.

The unknown key error appears because the "ms_efx_1named.txt" was saved using the wrong encoding for it, thus causing the engine to be unable to read the keys. Changing that file's encoding (and all files other than the localisation files) fixes the "Choose a consort" button and possibly other decisions/events as well.

But anyway, thank you very much for reminding me that error.log exists. It was really helpful in fixing the mod.

Oh and @Selvaria, your issue is fixed in version 1.2.0. Please try it and let me know.