Mission Design: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Linked to PBO definition)
m (Text replacement - "{{Feature | Informative | " to "{{Feature|informative|")
 
(23 intermediate revisions by 7 users not shown)
Line 1: Line 1:
[[Category:Missions: Flashpoint]]
{{TOC|side}}
[[Category:Editing: Flashpoint]]
[[Mission Design]] is an important aspect to consider in order to keep the player(s) entertained. '''Arma is a game''' after all!


But what makes a mission ''enjoyable''? This page aims to define what players usually expect from a game:
# Wanting to play through the whole mission
# Seeing an effect to their actions
# In the end, having '''a sense of accomplishment'''.


To learn the basics of mission editing, there is a tutorial delivered with the Flashpoint CD. An online version of this tutorial can be viewed: [[Mission Editing Tutorial]].
<!-- {{Feature|informative|This page does not apply to all milsim-targeted missions, which may or may not be completely "eventless"!}} -->


This article will illustrate the possibilities of the Flashpoint mission editor and its engine, and how to start.
== Action/Reward ==


----
The meat of player's interest is here; an achieved goal must reward the player with an evolution: either a reward (new intel, less enemies, easier progress) or a scenario evolution (enemy counterattack, reinforcements incoming, radio update).
'''<big>Mission components</big>'''<br><br>


A mission is comprised of multiple files, and optionally compressed into a '''.[[PBO]]''' file.


Upon un-PBOíng a mission you will see all files used in missions. The files used in missions are:
== Mission Structure ==


=== Gameplay Structure ===


[[Mission.sqm |mission.sqm]]<br>
''PvP (DM/TDM/etc)''
This file contains (in order) the required addons, the position and information of all units, the triggers ("sensors") , waypoints, markers, and miscellaneous information.


[[Briefing.html | briefing.html]]<br>
In missions without scenario (or a very basic one), '''fighting''' is the main course.
The briefing contains the text stored in the "notebook", i.e. the mission plan, objectives, and notes for the mission. For more information on how to make briefings there are multiple tutorials available.
Players want to fight, battle, win over the other team. So firefight it is!


{{Feature | important | When winning an objective, it is important to know that something has been achieved. If the action is not obvious by itself, use the HUD to inform the players.}}


[[Description.ext | description.ext]]<br>
==== Balance ====
This file contains all sorts of information, ranging from respawn, to different options in multiplayer. Selectable armament (in the "gear" tab of the notebook) can also be arranged here.
'''''Balance''''' is a bigger concern in these missions as a feeling of unfairness can kill the mood. Balance does not mean equal forces (e.g 1 airplane, 3 tanks and 20 soldiers each) but it should mean that with same-level players, the chances of winning is 50/50 (or 33.33/33.33/33.33 in the event of a tripartite scenario).


If forces are imbalanced, think of {{Link|https://en.wikipedia.org/wiki/GoldenEye_007_(1997_video_game)|GoldenEye (N64)}} Golden Gun system: a player with an insta-kill weapon stood against all the other players, but had to reload after each shot.
In {{arma}} this could be translated as one person having an assault helicopter with Air-to-Ground locking missiles, while all the other players have AA guns and try to take him down.


[[Overview.html | overview.html]]<br>
Another example of "balanced imbalance" would be high technology blufor forces outnumbered 2 to 1 by rusty AK47-equipped insurgents - the goal would then be to ''Survive, Adapt, and Win''.
When you click on a single mission, on the right, you see the overview, which is mostly comprised of a picture and one or two lines of text. Tutorials on how to make an overview can be found on '''OFPEC'''. Alternatively, you could unPBO a existing mission and use its overview as a template.


==== Examples ====
{| class="wikitable"
! [[Multiplayer Game Types#Available Types|Game Type]] !! HUD !! Information
|-
| DeathMatch || Top Score on the screen || {{n/a}}
|-
| Team DeathMatch || rowspan="4" | [[Side]]'s Score on the screen || {{n/a}}
|-
| Capture The Flag || A [[Arma 3: Notification|Notification]] on flag taken/captured/dropped/picked up
|-
| CTI || A [[Arma 3: Notification|Notification]] on city under attack/captured/lost
|-
| Sector Control || A [[Arma 3: Notification|Notification]] on sector under attack/captured/lost
|-
| Last Man || Number of Survivors on the screen || {{n/a}}
|}


'''.sqs files''' ('''S'''e'''Q'''uence '''S'''cript):<br>
=== Narrative Structure ===
Scripts are the backbone for creativity. They create, control and monitor all entities in a mission: Weather, AI, Armament, Smoke and Fire Effects. With good scripting humans can become zombies and a click on the map will bring a rain of artillery down. To learn about scripting look at this site's [[Scripting]] section.


''PvE (rarely PvP)'' (SP/MP)


[[Init.sqs | init.sqs]]<br>
<!-- {{Feature|informative|The narrative structure only applies to story-driven scenarios and does not have to be respected for missions that are mostly focused on immersion/gameplay.}} -->
A mission init.sqs (initialisation script) gets processed before the mission starts. This prevents "laggy" moments ingame, but might take the mission a long time to load.
The basics are that most stories follow the {{Link|https://en.wikipedia.org/wiki/Narrative_structure|narrative structure}}, which can be boldly boiled down to the following step:


{| class="wikitable"
! Initial Situation
|
* The initial situation does not have to be peaceful or positive
* [[:Category:Briefing|Briefing]] can be used to provide some background without having to create it in-game
|-
! Event<br><small>bringing imbalance to the situation</small>
|
* The origin of it is not always coming from the designated or future enemy
* The event can or can not come from a player's action
|-
! Actions and resulting events
|
* Actions can be taken against said event, but also (and/or) against its consequences
|-
! ''Dénouement''
| ''Dénouement'' means the end of actions and situation evolution, it can be:
* A lead to solve the initial situation
* A way to escape it
* Reaching the goal set by it
|-
! Ending
|
* Ending does not always mean problem resolution; it can be:
** Reducing the damages provoked by event's consequences
** Leaving the immediate danger
** Solving the initial problem and getting everything back to normal.
|}


'''image files''':<br>
{{Feature|informative|[[Scripting]] aside, The difference between Singleplayer and Multiplayer is the felt importance of '''Cooperation'''.}}
The briefing can contain pictures in '''.jpg''', '''.paa''' and '''.pac''' format, that follow the same basic size rule as textures ('''*^²'''), for example 256 X 128 pixels. Images can be manually sized to any width and height using HTML code. Note that if the image is too big, this will ruin the layout of the notebook. For information on adding images refer to a site such as '''OFPEC'''.


==== Mission Goal ====
While the ''mission's'' goal can remain hidden or obscure to the player(s), his ''current'' goal must be crystal clear. For example, the end goal of "fighting back" can remain hidden, but the first goal of "patrol the camp" must be made obvious so the player is not at loss and feels he has something to accomplish.


'''audio files''':<br>
==== Examples ====
Audio files in Flashpoint can be in '''.OGG''' (compressed), '''.WAV''' (uncompressed, but large filesize), or '''.WSS''' (good compression:size ratio) formats. The basic rule: More compression means longer time to process before the file gets heard.
{| class="wikitable"
! Initial Situation !! Event !! Actions !! Dénouement !! Ending !! Notes
|-
| During blufor/opfor war, a specops operation at night with the objective to blow up enemy tanks || {{n/a}} || '''Player's role:''' fulfilling the mission || Tanks are blown up || Extraction || This scenario may look bland, and should therefore focus on '''immersion''' and '''achievement'''
|-
| During blufor/opfor war, a specops operation at night with the objective to blow up enemy tanks || While approaching, the alarm is raised because the opfor got some information about a night attack. || '''Player's role:''' fulfilling the mission while a sub-group goes and creates a diversion in another depot || Diversion is made, then tanks are blown up || Extraction || This additional event gives (the) player(s) the feeling to have influenced the story, making the '''cooperation''' feel useful
|-
| Normal day || Enemies attack the base || Riposting, taking fire<br>'''Player's role:''' take strategical shooting positions and cover fellow soldiers || Killing/defeating all the enemies || Back to normal || Same as above, the scenario might be seen as too simple ("defending") and immersion should be prioritised
|-
| Normal day || Nuclear attack || Panic, explosions, firefights<br>'''Player's role:''' survive || Getting to a long-range radio || HQ sends a team to extract the player || This whole scenario is based on player's survival
|}




'''video files''':<br>
[[Category:Mission Editing]]
No known format of video is supported by OFP.
 
 
'''subfolders''':<br>
Script, image, and audio files might have been put in separate folders to keep things clear, but if you decide to put your (example) fire.sqs in a subfolder called "scripts", please note that you will have to use "\scripts\fire.sqs" to call the script". ''It is advisable to keep the init.sqs away from subfolders.''
 
 
<br>'''<big>Creating briefing, sqs, and ext.</big>'''<br><br>
 
Briefings, scripts, and description files can be done manually in Notepad and saved as ''filename.customextension''.
 
A good alternative for mission makers is [http://www.chenderman.com/CHOFPSE.htm '''CH'''ris's '''OFP S'''cript '''E'''ditor]
 
<br>'''<big>Mission editor limitations</big>'''<br><br>
 
Great effort has been put into making the mission editor as limitless as possible. However, it isn't.

Latest revision as of 21:41, 16 May 2024

Mission Design is an important aspect to consider in order to keep the player(s) entertained. Arma is a game after all!

But what makes a mission enjoyable? This page aims to define what players usually expect from a game:

  1. Wanting to play through the whole mission
  2. Seeing an effect to their actions
  3. In the end, having a sense of accomplishment.


Action/Reward

The meat of player's interest is here; an achieved goal must reward the player with an evolution: either a reward (new intel, less enemies, easier progress) or a scenario evolution (enemy counterattack, reinforcements incoming, radio update).


Mission Structure

Gameplay Structure

PvP (DM/TDM/etc)

In missions without scenario (or a very basic one), fighting is the main course. Players want to fight, battle, win over the other team. So firefight it is!

⚠
When winning an objective, it is important to know that something has been achieved. If the action is not obvious by itself, use the HUD to inform the players.

Balance

Balance is a bigger concern in these missions as a feeling of unfairness can kill the mood. Balance does not mean equal forces (e.g 1 airplane, 3 tanks and 20 soldiers each) but it should mean that with same-level players, the chances of winning is 50/50 (or 33.33/33.33/33.33 in the event of a tripartite scenario).

If forces are imbalanced, think of GoldenEye (N64) Golden Gun system: a player with an insta-kill weapon stood against all the other players, but had to reload after each shot. In Arma this could be translated as one person having an assault helicopter with Air-to-Ground locking missiles, while all the other players have AA guns and try to take him down.

Another example of "balanced imbalance" would be high technology blufor forces outnumbered 2 to 1 by rusty AK47-equipped insurgents - the goal would then be to Survive, Adapt, and Win.

Examples

Game Type HUD Information
DeathMatch Top Score on the screen N/A
Team DeathMatch Side's Score on the screen N/A
Capture The Flag A Notification on flag taken/captured/dropped/picked up
CTI A Notification on city under attack/captured/lost
Sector Control A Notification on sector under attack/captured/lost
Last Man Number of Survivors on the screen N/A

Narrative Structure

PvE (rarely PvP) (SP/MP)

The basics are that most stories follow the narrative structure, which can be boldly boiled down to the following step:

Initial Situation
  • The initial situation does not have to be peaceful or positive
  • Briefing can be used to provide some background without having to create it in-game
Event
bringing imbalance to the situation
  • The origin of it is not always coming from the designated or future enemy
  • The event can or can not come from a player's action
Actions and resulting events
  • Actions can be taken against said event, but also (and/or) against its consequences
Dénouement Dénouement means the end of actions and situation evolution, it can be:
  • A lead to solve the initial situation
  • A way to escape it
  • Reaching the goal set by it
Ending
  • Ending does not always mean problem resolution; it can be:
    • Reducing the damages provoked by event's consequences
    • Leaving the immediate danger
    • Solving the initial problem and getting everything back to normal.
ⓘ
Scripting aside, The difference between Singleplayer and Multiplayer is the felt importance of Cooperation.

Mission Goal

While the mission's goal can remain hidden or obscure to the player(s), his current goal must be crystal clear. For example, the end goal of "fighting back" can remain hidden, but the first goal of "patrol the camp" must be made obvious so the player is not at loss and feels he has something to accomplish.

Examples

Initial Situation Event Actions Dénouement Ending Notes
During blufor/opfor war, a specops operation at night with the objective to blow up enemy tanks N/A Player's role: fulfilling the mission Tanks are blown up Extraction This scenario may look bland, and should therefore focus on immersion and achievement
During blufor/opfor war, a specops operation at night with the objective to blow up enemy tanks While approaching, the alarm is raised because the opfor got some information about a night attack. Player's role: fulfilling the mission while a sub-group goes and creates a diversion in another depot Diversion is made, then tanks are blown up Extraction This additional event gives (the) player(s) the feeling to have influenced the story, making the cooperation feel useful
Normal day Enemies attack the base Riposting, taking fire
Player's role: take strategical shooting positions and cover fellow soldiers		 Killing/defeating all the enemies Back to normal Same as above, the scenario might be seen as too simple ("defending") and immersion should be prioritised
Normal day Nuclear attack Panic, explosions, firefights
Player's role: survive		 Getting to a long-range radio HQ sends a team to extract the player This whole scenario is based on player's survival
Retrieved from "https://community.bistudio.com/wiki?title=Mission_Design&oldid=364466"