Source Code Project Mantis - FSSCP
View Issue Details
0003204FSSCPlocalizationpublic2018-02-26 12:402018-02-26 12:40
Assigned To 
PlatformOSOS Version
Product Version3.8 
Target VersionFixed in Version 
Summary0003204: $Command Sender as #Command source in messages
DescriptionIn 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 ReproduceCreate a mission, set an invidiual command name in the mission specs and then make a send-message event with #Command as communication source.
Additional InformationThe $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.
TagsNo tags attached.
Attached Files

There are no notes attached to this issue.

Issue History
2018-02-26 12:40NovachenNew Issue