Multiple commands can be sent in a single message (e.g. /laps=10 /cars=UF1 /wind=1), however, starting a message with /i or /o will result in any following slash character (if preceded by a space) to be interpreted as a command.

Examples:

• /i Testing /i messages
  
  Sends 2 IS_III messages, containing "Testing" and "messages".
  
  
• /o Hidden message triggering /i IS_III
  
  Sends an IS_MSO (MSO_O) "Hidden message triggering" and an IS_III "IS_III".
  
  
• /o Sending a message and some command: /laps 2
  
  Sends an IS_MSO (MSO_O) "Sending a message and some command:" and changes lap count.
  
  
• /o Disable SC/VSC
  
  Sends IS_MSO "Disable SC/VSC"
  
  
• /o Disable SC / VSC
  
  Sends IS_MSO "Disable SC" and throws an "Unknown command" error for "/ VSC"
  

I believe that /i and /o messages should be excluded from multi-command parsing, at the very least if they're the first command in the message, since those messages are supposed to be parsed by an InSim application anyway.

Thanks, in my version I've added /i and /o to the commands that are excluded from command line splitting.

Quote from Bokujishin :

starting a message with /i or /o will result in any following slash character (if preceded by a space) to be interpreted as a command.

Worth mentioning that there is also another bug related to pretty much this: if there is username, AI-driver name, heck probably any name that has the "/" character (or I think even the "\" character), any command that has parameter [name] doesn't work with that name, because LFS thinks you are setting two commands.

I don't think you even need to start your message with a /i or /o command to reproduce this very similar bug. Easy way for Scawen to reproduce this: set your name to "Scawen /LFS Developer". Then try to add a command like /pitlane Scawen /LFS Developer. LFS thinks you're trying to type two commands: /pitlane Scawen and /LFS Developer

Weirdly though, this bug doesn't happen when setting commands in LFS Host Control Panel on LFS.net, only in LFS in-game.

Does it work if you escape the slash character as ^s ? I haven't tested it myself, I don't even know if escaping works in this direction as well.

Quote from Flame CZE :

Does it work if you escape the slash character as ^s ? I haven't tested it myself, I don't even know if escaping works in this direction as well.

Doesn't look like it works in LFS in-game. If I try to type a command by typing ^s[command name] instead of /[command name] it just makes me type a message ^s[command name] which makes me look like an idiot - and if I try to assign a command with parameter name and replace the / character in the parameter with ^s, it just reports that parameter is not valid.

I also tested it in LFS Host Control Panel in LFS.net. I can change the color of messages Host writes by putting ^0-8 before the text, but if I try to add ^s instead of slash, it will still print out literally "^s" on chat - so ^0-8 doesn't show on the screen but ^s does