ArmA: Scripting - Getting Started
Scripts are an essential part of making missions. They allow you to create amazing cutscenes, create effects and customize almost every aspect of your mission. Some diverse examples of what could be scripted are: a simulation of artillery fire, a poisonous gas cloud, or a money system for purchasing equipment.
Your first task in writing scripts is to decide what sequence of steps is needed to solve a particular problem. This sequence is what would be called an algorithm.
For example, if you wanted to transport weapons from Petrovice to Lipany, you would (as commander) give these orders:
- Commander: Private Honka, private Kouba, come here!
- Commander: Private Kouba, get in Ural as driver!
- Commander: Private Honka, get in Ural!
- Commander: Private Kouba, drive to Petrovice and load Ural!
- Private Kouba: I don't know where Petrovice is, sir.
Now we have a problem. Kouba only knows how to get to Lipany and Honka only knows how to get to Petrovice. Our soldiers are new recruits and are really quite stupid. They can only take simple orders, one order at a time. They can get in and out of vehicles, drive, and load and unload weapons and ammo. The commander must plan this sequence of orders and make provisions for obstacles that may arise.
1. Destination is Petrovice 2. Get in vehicle 3. If driver does not know the way to Destination, swap driver and passenger 4. Drive to Destination 5. Get out of vehicle 6. Load vehicle 7. Destination is Lipany 8. Get in vehicle 9. If driver does not know the way to Destination, swap driver and passenger 10. Drive to Destination 11. Get out of vehicle 12. Unload vehicle
If you have an algorithm, you need something that can execute it. We have a computer game, Armed Assault, which is able to do this; commanders have soldiers.
It's the way how to write our algorithm for Armed Assault. ArmA scripts are a sequence of 'orders' describing how to do it.
Source code is algorithm written in any programming language.
Syntax is made up of commands and parameters, sometimes just the command is required as in exit, other times the syntax is made up of one or more parameters. Each command has it's own reference in the Scripting section of the wiki. In each case the command + its parameters are listed with examples on how that particular command works.
You should however be aware that there are two similar scripting grammars in Armed Assault, namely SQF and SQS. While the functions are almost the same, there are still minor differences in statement notations, program flow and control structures.
The Armed Assault engine reads your code from script files and translates those instructions for you to achieve your desired outcome/effect in the game.
Every script consist of commands (see category Scripting Commands) and program flow statements (they are implemented as commands in Armed Assault, but it isn't relevant for now). The most useful command in your first script is titleText. It can write any text you want to the player's screen.
titleText["Good morning, captain", "PLAIN DOWN"]
It's a typical way to run commands. Behind the name of the command the parameters follow (but it depends on the command (see Category:Scripting Commands). Every command can only have one parameter before it's name and/or one after (more arguments can be given with arrays which count as one parameter). Parameters can be of various Data types. In this case it's an Array - a list of other data types. It can contain 0 - 4096? values. The first value is a String representing the text to be displayed and the second, in this case, says in what position on the screen the text will be displayed. There can be a third value: a Number which says how long the text needs to fade in. If this value is not entered, its default value (1) is used.
titleText["Good morning, captain", "PLAIN DOWN", 5]
Scripts which are called functions) are stored in .SQF files the mission folder, or in .SQSs files and then called only scripts.
If you want to try our 'script', create a mission in the mission editor, save it as testingmission, open your favorite text edtior (eg. Notepad), write
titleText["Good morning, captain", "PLAIN DOWN"];and save it as hello.sqf to gamefolder/user/yourname/missions/testingmission. Then add a soldier in the mission editor and type
nul =  execVM "hello.sqf" to his initialization line. When you run this mission, you should see output of your first script. Well done, soldier! (If you are confused from this quantum of informations, don't panic, more continuously explanation follows.)
Statements and operators