Report, edit, etc...Posted by Screwed on 2005-05-06 at 03:47:19
Would -
Trigger("Player 1"){
Conditions:
Switch("Switch1", clear);
Bring("Force 3", "Terran Marine","^16",exactly,1);
Actions:
Comment("");
so on.....
be the same as
Trigger("Player 1"){
Conditions:
Switch("Switch1", clear);
Bring("Force 3", "Terran Marine","^16",exactly,1);
Actions:
Comment("");
if so, the spaces in front of the functions are just to make it easier to read right?
Also, another question, does there need to be a space bar after each comma?
e.g.
would
Bring("Force 3","Terran Marine","^16",exactly,1);
be the same as
Bring("Force 3", "Terran Marine", "^16", exactly, 1);
Also, are function names case sensitive?
Trigger("Player 1"){
Conditions:
Switch("Switch1", clear);
Bring("Force 3", "Terran Marine","^16",exactly,1);
Actions:
Comment("");
so on.....
be the same as
Trigger("Player 1"){
Conditions:
Switch("Switch1", clear);
Bring("Force 3", "Terran Marine","^16",exactly,1);
Actions:
Comment("");
if so, the spaces in front of the functions are just to make it easier to read right?
Also, another question, does there need to be a space bar after each comma?
e.g.
would
Bring("Force 3","Terran Marine","^16",exactly,1);
be the same as
Bring("Force 3", "Terran Marine", "^16", exactly, 1);
Also, are function names case sensitive?
Report, edit, etc...Posted by LegacyWeapon on 2005-05-06 at 06:28:21
Not case sensitive. Not space sensitive.
Once I had a trigger written out in a line and SCMD2 fix it for me when I reloaded the triggers after compiling
Once I had a trigger written out in a line and SCMD2 fix it for me when I reloaded the triggers after compiling
Report, edit, etc...Posted by SI on 2005-05-06 at 07:18:29
trigedit works like most programming languages, it treats all whitespaces as one, IE you can put erverything on 1 line or have 100 blank lines, it doesn't care.
Report, edit, etc...Posted by Screwed on 2005-05-06 at 22:10:01
Oh, ok thats all I need. Trigedit is more flexible than I thought. Thanks guys!