PMC Editing Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== ArmA 2 Creating Briefing ======

[[https://www.pmctactical.org/forum/viewforum.php?f=50|ArmA 2 Forum]], [[:arma2|ArmA 2 Home]], [[arma2:config|ArmA 2 Config]], [[arma2:file_formats|ArmA 2 File Formats]], [[arma2:missions|ArmA 2 Missions]], [[arma2:modeling|ArmA 2 3D Modeling]], [[arma2:scripting|ArmA 2 Scripting]], [[arma2:terrain|ArmA 2 Terrain]], [[arma2:texturing|ArmA 2 Texturing]], [[arma2:tools|ArmA 2 Tools]]

How to create a briefing.

ArmA 2 does not use the briefing.html anymore for the Notes and Tasks sections. The briefing.html is only used for the Debriefing text which is dependent on the EndMission trigger of the mission.

An Example briefing: (should actually be renamed to debriefing.html now BIS)
<code html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1250">
<title>Title</title>
</head>

<body bgcolor="#FFFFFF">
<! -----DEBRIEFING----->
<hr>
<br>
<h2><a name="Debriefing:End1">end1 title</a></h2>
<br>
<p>
<! ------victory------>
We Won!
</p>
<br>

<hr>
<br>
<h2><a name="Debriefing:End2">end2 title</a></h2>
<br>
<p>
<! ------KIA------>
We lost...
</p>
<br>
<! -----DEBRIEFING END----->

</body>
</html>
</code>
These different endings are activated in triggers, but I'm sure everyone knows about them already (the end1 and end2 endings are in the type listbox of the trigger menu)

So how do we give the mission players Tasks and Notes since we cant do that in the briefing.html anymore?

It's simple, and you only need to know 5 commands.

createDiaryRecord\\
createSimpleTask\\
setSimpleTaskDescription\\
setSimpleTaskDestination\\
setTaskState\\

To add a Note:
<code cpp>
player createDiaryRecord["Diary", ["The title", "The message"]];
</code>

This will add a note to your briefing. If you execute this command multiple times with the same title but different message, the messages will be timestamped.

Adding a task:
<code cpp>
tskAttackVishnoye = player createSimpleTask["Attack Vishnoye"];
</code>

This will add a task with the title "Attack Vishnoye". However, there is no description, and no task-marker on the map, so we need 2 additional commands.
<code cpp>
tskAttackVishnoye setSimpleTaskDescription["Task Description", "Task Title", "HUD Title"];
</code>

This command allows you to add 3 different descriptions to your task. The 1st array element will be the description you'll see in the big box in your briefing, the 2nd will be for the title (yes, you can set that one again with this command), and the 3rd element will be the task description you'll see on the HUD (you know, when you get a move order for example you see it on the HUD, that text you can define now)
<code cpp>
tskAttackVishnoye setSimpleTaskDestination (getMarkerPos "obj1");
</code>

If you added an empty marker near the objective, and you want a task-marker on there, you use this command. When you select this task as current task, the marker will light up. Make sure you use an existing marker here, cause otherwise it will place the task destination at [0,0].

Marker example:
<code cpp>
<marker name='obj1'>Objective 1</marker>
</code>

And image example:
<code cpp>
<img image='path\mission\filename.paa'>
</code>

Color example:
<code cpp>
<font color='#FF0000'>red</font>
<font color='#FFFF00'>yellow</font>
<font color='#008000'>green</font>
<font color='#0000FF'>blue</font>
</code>
I suggest you put these commands in a file called briefing.sqf so you keep your other files clean, and then in your init.sqf write execVM "briefing.sqf"

How to fail or accomplish a task
<code cpp>
tskAttackVishnoye setTaskState "SUCCEEDED"; // yay, success!
tskAttackVishnoye setTaskState "FAILED"; // fail
</code>

Important Notes:

  * The last added Note or Task will be on TOP, so remember to do it in reverse order!!!
  * Everything in italics you can change to your own liking
  * The tskAttackVishnoye is a variable which holds a reference to the task. After youve created the task, you can use that var name to manipulate the task.
  * All these commands are local arg, local effect. So execute them on every machine (throw them in the init.sqf).