|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003204||FSSCP||localization||public||2018-02-26 12:40||2019-05-02 22:59|
|Target Version||Fixed in Version|
|Summary||0003204: $Command Sender as #Command source in messages|
|Description||In missions it is possible to create an custom named sender for command messages. Unfortunately this entry only works for the built-in command messages but not for the actual messages in the mission that has the #Command source.|
They are still send by "Command" even Command is named or specified differently.
For multilingual support it would be better, if #Command is equal to the $Command sender, because then you do not have to change all messages and have to create several versions of the same mission. You can take over the $command sender with an XSTR into the tstrings.tbl, translate it there and then all #Command messages would have the translated name of the source.
Is there a particular reason why both entries are seperate to each other? In which cases is #Command different to the $command sender anyway?
|Steps To Reproduce||Create a mission, set an invidiual command name in the mission specs and then make a send-message event with #Command as communication source.|
|Additional Information||The $command sender line should always added with an XSTR by default in a mission file even if the default entry is used. So that this is always translateable by default.|
|Tags||No tags attached.|
The mission's "Command Sender" refers to the Command persona, not the #Command source specified by send-message.
This issue sounds familiar. Was this already resolved elsewhere?
|2018-02-26 12:40||Novachen||New Issue|
|2019-05-02 22:59||Goober5000||Note Added: 0016925|