XS insertion

[River_God]

ok, I looked at the map. From what I have seen from that map, CB and FW, it looks like you create a function "send chat", with the message being "*/"+ a line of code to enter +"/*" and then call it for every line of code you want inserted.  What I want to know is:

What are all the symbols that can affect the code inserted, and what do they do?
What is the point of XS injection?
Do I just use the trigger code in the code insertion, or something else?
What's the point of this line(line 23 in TOS_BloodSport-v3-3):
 rmSetTriggerEffectParam("Message", "\"); }} /*", false);

[pftq]

There are two methods I know of for insertion - you are mixing them together and trying to combine them...

Do you understand what custom effects/conditions are in scenarios? Quite the same here.

You basically can insert your own trigger code and create your own effects/conditions.  It is also more direct - you feed the commands straight to the computer.  Normally, trigger conditions/effects are read by the computer and then referenced with the typetest file; the computer then goes and compiles the commands itself (meaning more load time than if you gave the commands straight off).

It is virtually being able to script actions DURING the game, as opposed to only affecting the map generation, which is RMS.

The line you mentioned is used to start a series of insertions IF you wish for the variables to remain "global" (usable across numerous triggers)

The pattern is usually:

Send Chat - Start
Send Chat - XS Code
Send Chat - End

For more general use, I use:
SetIdleProcessing
Param: ("IdleProc", "true); "+xs+" trSetUnitIdleProcessing(true")