Mission Design: Difference between revisions
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
---- | ---- | ||
'''<big>mission components</big>''' | '''<big>mission components</big>'''<br><br> | ||
A mission is comprised of multiple files, and optionally compressed into a .PBO file. the files used in missions are: | A mission is comprised of multiple files, and optionally compressed into a .PBO file. the files used in missions are: | ||
''mission.sqm'': | <br>''mission.sqm'': | ||
This file contains (in order) the required addons, the position and information of all units, the triggers ("sensors") , waypoints, | This file contains (in order) the required addons, the position and information of all units, the triggers ("sensors") , waypoints, markers, and misc. information. | ||
''briefing.html'' | <br>''briefing.html'' | ||
the briefing contains the text stored in the "notebook". For more information about briefings there are multiple tutorials available. | the briefing contains the text stored in the "notebook", The mission plan, objective, and notes of the mission. For more information about briefings there are multiple tutorials available. | ||
''description.ext'' | <br>''description.ext'' | ||
This file contains all sorts of information, ranging from respawn, to different option in multiplayer. | |||
''init.sqs'' | <br>''init.sqs'' | ||
no information yet | no information yet | ||
<br><br>''image files'' | |||
the briefing can contain pictures in .paa and .pac format, that follow thesame basic rule as textures (*^²). for example, 256X128 pixels. Images can be manually sized to any with and size 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. | |||
'' | <br>''audio files'' | ||
Audio files in Flashpoint can be in .Ogg (compressed) , .Wav (uncompressed, but large filesize) , or .WSS (good compression:size ratio) format. The basic rule: more compression means longer time to process before the file gets heard. | |||
<br>''video files'' | |||
No known format of video is supported by OFP. | |||
'''<big>Mission editor limitations</big>''' | <br>'''<big>Mission editor limitations</big>''' | ||
Great effort has been put into making the mission editor as limitless (...) | Great effort has been put into making the mission editor as limitless (...) | ||
Revision as of 10:01, 6 April 2006
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 here.
This article will illustrate the possibilities of the Flashpoint mission editor and it's engine.
mission components
A mission is comprised of multiple files, and optionally compressed into a .PBO file. the files used in missions are:
mission.sqm:
This file contains (in order) the required addons, the position and information of all units, the triggers ("sensors") , waypoints, markers, and misc. information.
briefing.html
the briefing contains the text stored in the "notebook", The mission plan, objective, and notes of the mission. For more information about briefings there are multiple tutorials available.
description.ext
This file contains all sorts of information, ranging from respawn, to different option in multiplayer.
init.sqs
no information yet
image files
the briefing can contain pictures in .paa and .pac format, that follow thesame basic rule as textures (*^²). for example, 256X128 pixels. Images can be manually sized to any with and size 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.
audio files
Audio files in Flashpoint can be in .Ogg (compressed) , .Wav (uncompressed, but large filesize) , or .WSS (good compression:size ratio) format. The basic rule: more compression means longer time to process before the file gets heard.
video files
No known format of video is supported by OFP.
Mission editor limitations
Great effort has been put into making the mission editor as limitless (...)