Differences

This shows you the differences between two versions of the page.

--- arma:scripting [2007-07-10 09:52]
127.0.0.1 external edit
+++ arma:scripting [2009-04-01 00:27]
snakeman fixed code formatting. added live execVM tip.
@@ Line 2: / Line 2: @@
 Scripting in ArmA is changed somewhat from OFP times.
+In OFP we have the SQS scripts which are read line by line, in ArmA now we have the SQF scripts which are read like a code. They are so much more powerful and easier to use once you get the idea, do not be afraid of them even if you've mastered the SQS method before but now the SQF things look strange and scary. Trust me on this, learn it and you'll be amazed how great SQF scripting is.
+In a nutshell you never ever should create ArmA SQS content anymore, always create only SQF scripts.
 ====== Overview ======
-ArmA has “” quotes for STRINGS only and {} curled braces for CODE only. Script commands doesn’t have to be in one line now with the curled braces. Command lines always end with ; instead of a ; *or* carriage return. So you can format code to be more readable
+How do you run SQF script?
+argument execVM filename
+Example:
+<code cpp>
+var = [player] execVM "test.sqf";
+</code>
+Argument is passed to the script as local variable _this.
+The Script is first searched for in the mission folder, then in the campaign scripts folder and finally in the global scripts folder.
+ArmA has "" quotes for STRINGS only and {} curled braces for CODE only. Script commands doesn’t have to be in one line now with the curled braces. Command lines always end with ; instead of a ; *or* carriage return. So you can format code to be more readable
-<code>
+<code cpp>
 {
     if (condition) then
@@ Line 17: / Line 34: @@
         DoSomething5;
      };
-} foreach array;
+} forEach array;
 </code>
 Instead of the terrible ofp classic
-<code>
+<code cpp>
 {if (condition) then {DoSomething1; DoSomething2; DoSomething3; DoSomething4; DoSomething5;};} foreach array;
 </code>
+====== Comments ======
 Comments are no longer the same character as the end of command character.
-<code>
+<code cpp>
 // my comment
 instead of
@@ Line 36: / Line 55: @@
 You can use block comments now.
-<code>
+<code cpp>
 /*
-  Comment line 1
+Comment line 1
-  Comment line 2
+Comment line 2
-  Comment line 3
+Comment line 3
-  Comment line 4
+Comment line 4
-  Comment line 5
+Comment line 5
-  Comment line 6
+Comment line 6
 */
 </code>
@@ Line 49: / Line 68: @@
 Quotes are no longer a valid substitute for braces.
-Some SQF things
+====== Some SQF things ======
-<code>
+Some misc SQF things here ;)
+<code cpp>
 _resultArray = [0,""];
 _handle = [_resultArray] execVM "resultScript.sqf";
@@ Line 59: / Line 80: @@
 _resultString = _resultArray select 1;
 </code>
+And
+<code cpp>
+myFunction1 = compile loadFile "myFunction1.sqf";
+myFunction2 = compile preprocessFile "myFunction2.sqf";
+call myFunction1;
+[1, 2] call myFunction2;
+</code>
+Return value?
+<code cpp>
+value = call compile preprocessFile "return.sqf";
+// value is now RETURN_VALUE
+call compile preprocessFile "return.sqf";
+// valid, but RETURN_VALUE is not saved anywhere
+</code>
+====== Private ======
+Using the private list.
+<code cpp>
+private ["_t", "_p", "_yea"];
+</code>
+Is to make the _local variables really a private ones in the SQF script.
+====== Exit while loop ======
+<code cpp>
+if (condition) exitWith {Code}
+if (_x > 5) exitWith {echo "_x is too big"; _x}
+</code>
+And
+<code cpp>
+for "_j" from 1 to 10 do
+{
+	player sideChat format ["%1",_j];
+	if (_j == 5) exitWith {player sideChat "5 is enough"};
+};
+player sideChat "Complete";
+</code>
+====== Switch ======
+Switch is quite nice option to check many conditions at once.
+Example 1
+<code cpp>
+switch (_a) do
+{
+	case 1:
+	{
+		hint "1";
+	};
+	case 2:
+	{
+		hint "2";
+	};
+	default
+	{
+		hint "default";
+	};
+;}
+</code>
+Example 2
+<code cpp>
+switch (_a) do
+{
+	case true:
+	{
+		hint "true";
+	};
+	case false:
+	{
+		hint "false";
+	};
+	default
+	{
+		hint "default";
+	};
+};
+</code>
+Example 3
+<code cpp>
+switch (_a) do
+{
+	case "string1":
+	{
+		hint "string1";
+	};
+	case "string2":
+	{
+		hint "string2";
+	};
+	default
+	{
+		hint "default";
+	};
+};
+</code>
+====== Script to nil ======
+When you have script like this
+<code cpp>
+MyScript = compile preProcessFile "myScript.sqf";
+</code>
+When you want to unload the script, set MyScript equal to nil.
+<code cpp>
+MyScript = nil;
+</code>
+====== Dynamic Variables ======
+Dynamic variables are very cool, sometimes on those random / complex missions you want to make variables later in the mission, which you cannot specify at mission start (hardcoded).
+<code cpp>
+_MyVariable = 20;
+_MyVariableContent = "MyContent";
+call compile format["MyDynamic_%1=_MyVariableContent",_MyVariable];
+</code>
+This would create: MyDynamic_20 variable with content: "MyContent"
+Another example
+<code cpp>
+_name = format ["mytrigger%1", triggerIndex];
+call compile format ["%1 = createTrigger [....]", _name];
+</code>
+====== Misc PMC Example Scripts ======
+Place random vehicles + some units on all found **pmc_** gamelogics script, [[arma:scripting:pmc_logic1|here]].
+====== Running Scripts "Live" ======
+When you start your mission in mission editor, you can go and edit your scripts and then they are called the next time, they will be reloaded at the same time so your edits to them will be usable.
+This is very nice feature to have, just run ArmA in window mode as you should always do when mission editing, then edit away and for example keep a "runme.sqf" script in the dir executed from radio alpha (or action menu) repeatedly, then you can edit the runme.sqf and add any additional script there what you want to run.
+You can now run a long mission and always bring new scripts into the play and so on. Imagine how many times have you play tested a mission and had to wrote down notes that "in this and that part you need to add XYZ", but now... you can just write a quick script (or use existing one) and add that to the runme.sqf and just call it up... script is run and you can proceed with the mission. Great.

PMC Editing Wiki

User Tools

Site Tools

Differences

Page Tools