Briefing – Arma 2
m (category) |
Lou Montana (talk | contribs) m (Text replacement - "\[ *((ftp|http)s?:\/\/[^ ]+)([^{])=([^}])([^ ]+)" to "[$1$3{{=}}$4$5") |
||
(3 intermediate revisions by the same user not shown) | |||
Line 3: | Line 3: | ||
Prior to {{arma2}}, briefings were constructed through a [[Briefing.html]] file. | Prior to {{arma2}}, briefings were constructed through a [[Briefing.html]] file. | ||
{{Feature|arma3 | For {{arma3}} briefing, see [[Arma 3 Briefing]].}} | {{Feature|arma3|For {{arma3}} briefing, see [[Arma 3: Briefing]].}} | ||
== Briefings == | == Briefings == | ||
Line 10: | Line 11: | ||
Example: | Example: | ||
<sqf>player createDiaryRecord ["Diary", ["Situation", "Things are looking bad."]];</sqf> | |||
This adds a note called 'Situation', and when you click on that a bigger message screen comes up with the message 'Things are looking bad.' | This adds a note called 'Situation', and when you click on that a bigger message screen comes up with the message 'Things are looking bad.' | ||
Line 18: | Line 19: | ||
See [[Tasks]]. | See [[Tasks]]. | ||
Example: | Example: | ||
<sqf> | |||
tskExample1 = player createSimpleTask ["Task Message"]; | |||
tskExample1 setSimpleTaskDescription ["Task Message", "Task Title", "Task HUD Title"]; | |||
// Make sure you have an empty marker called 'mkrObj1' | |||
// and you will see a semi-transparant circular marker which will light up when you set the task as active. | |||
tskExample1 setSimpleTaskDestination (getMarkerPos "mkrObj1"); | |||
</sqf> | |||
In your diary, "Task Title" is displayed for each task you set, and when you click on each task, it is "Task Message" appears. And "Task HUD Title" is what gets shown on the HUD. | In your diary, "Task Title" is displayed for each task you set, and when you click on each task, it is "Task Message" appears. And "Task HUD Title" is what gets shown on the HUD. | ||
We force a task upon a player by executing this on his machine: | We force a task upon a player by executing this on his machine: | ||
<sqf>player setCurrentTask tskExample1; // This will highlight the objective marker, and show him the through the HUD where the objective is.</sqf> | |||
We alter the task status during the mission by the following options: | We alter the task status during the mission by the following options: | ||
<sqf> | |||
tskExample1 setTaskState "SUCCEEDED"; // Makes the checkbox green | |||
tskExample1 setTaskState "FAILED"; // Puts a red cross in the checkbox | |||
tskExample1 setTaskState "CANCELED"; // Puts a grey diagonal line through the checkbox | |||
tskExample1 setTaskState "CREATED"; // Clears the checkbox (makes it look like you've just created it) | |||
</sqf> | |||
You can show the state of the task with the [[taskHint]] command, or for an alternative method see this [http://www.ofpec.com/forum/index.php?topic{{=}}33768.0 OFPEC topic]. | |||
[[Category:Briefing]] | [[Category:Briefing]] |
Latest revision as of 17:20, 28 April 2023
The briefing is an essential part of any mission. It usually displays a synopsis of what to do to complete the mission, as well as objectives.
Prior to Arma 2, briefings were constructed through a Briefing.html file.
Briefings
Adding Notes
Example:
This adds a note called 'Situation', and when you click on that a bigger message screen comes up with the message 'Things are looking bad.'
Adding Tasks
See Tasks. Example:
In your diary, "Task Title" is displayed for each task you set, and when you click on each task, it is "Task Message" appears. And "Task HUD Title" is what gets shown on the HUD.
We force a task upon a player by executing this on his machine:
We alter the task status during the mission by the following options:
You can show the state of the task with the taskHint command, or for an alternative method see this OFPEC topic.