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.