Confirmed CK III - Scripted Effect Parameters Converted to Strings Improperly

[jumbi]

Short summary of your issue
Scripted Effect Parameters Converted to Strings Improperly

Game Version
1.3.1

What OS are you playing on?
Windows

What platform are you using?
Steam

Do you have mods enabled?
Yes

Have you tried verifying your game files (Steam only)?
Yes

How much "pain" is this causing you?
2

Please explain the issue you experienced in the most condensed way possible
When referencing a scripted effect parameter inside of custom tooltip or other localization block, they do not appear to be converted to strings properly. Rather than remove the leading and trailing dollar signs and display the value of the parameter, they instead delete the character preceding the value in the string and the leading dollar, then display the value followed by the trailing dollar sign.

e.g.
Suppose TRIBUTE_PERCENT = 0.4 and the localization is "Will pay $TRIBUTE_PERCENT$ percent of their income"

Expected output: Will pay 0.4 percent of their income

Actual output: Will pay0.4$ percent of their income

This occurs similarly with character scopes, preventing their use in localization commands due to the tailing dollar sign

Please explain how to reproduce the issue
Create a scripted effect which takes in a parameter and displays it in a tooltip
e.g.
debug_param_effect = {
custom_tooltip = "Hello $DEBUG_PARAM$"
}

Open CKIII in debug mode
Go to the script runner in the object explorer
Enter the command "debug_param_effect = { DEBUG_PARAM = World }"
Parse the command and mouse over its tooltip
Output will be "HelloWorld$" rather than expected "Hello World"

Is there anything else you think could help us identify/replicate the issue?
I have attached the example scripted effect above to quickly reproduce the issue.

I have attached a save game
No

Upload Attachment
File(s) attached

 

[Jarl Ankermann]

Heil og sæl, @jumbi

Thanks for staying Vigilant! I've added the problem to our database.

Cheers!

 

[jumbi]

For anyone else experiencing the same issue, an alternative in the meantime is to supply the param as a value in a custom description:

custom_description = {
    text = tribute_percent_info_tt
    value = $TRIBUTE_PERCENT$
}