| Next revision | Previous revision | 
| ofp:missions:overview.html [2007/07/09 01:43]  – created overview.html initial page snakeman | ofp:missions:overview.html [2024/07/31 15:05] (current)  – links added. snakeman | 
|---|
| ====== Overview html ====== | ====== OFP Overview html ======  | 
|   |   | 
|   | [[https://www.pmctactical.org/forum/viewforum.php?f=43|OFP Forum]], [[:ofp|OFP Home]], [[ofp:file_formats|OFP File Formats]], [[ofp:tools|OFP Tools]], [[ofp:missions|OFP Missions]], [[ofp:modeling|OFP 3D Modeling]], [[ofp:terrain|OFP Terrain]]  | 
|   |   | 
|   | **Operation Flashpoint (OFP)** aka ArmA: Cold War Assault (CWA) | 
 |  | 
| The //overview.html// is an optional file, which simply means the game won't crash without it, but it adds polish to your creative efforts. It appears on the notebook before you start a mission or campaign.  When you click on a mission, on the right you see an overview, which is mostly comprised of a picture and one or two lines of text. Alternatively, you could de-PBO an existing mission and use its overview file as a template. | The //overview.html// is an optional file, which simply means the game won't crash without it, but it adds polish to your creative efforts. It appears on the notebook before you start a mission or campaign.  When you click on a mission, on the right you see an overview, which is mostly comprised of a picture and one or two lines of text. Alternatively, you could de-PBO an existing mission and use its overview file as a template. | 
|   * single missions, |   * single missions, | 
|   * a campaign, and |   * a campaign, and | 
|   * individual  missions of a campaign. |   * individual missions of a campaign. | 
 |  | 
| The overview of a mission within a campaign is not visible until after you have played that mission. The intent of all overviews is to provide a brief idea of what the mission is about. The keyword is 'brief', because space in the notepad is at a premium. | The overview of a mission within a campaign is not visible until after you have played that mission. The intent of all overviews is to provide a brief idea of what the mission is about. The keyword is 'brief', because space in the notepad is at a premium. | 
 |  | 
| Version numbers and mission author details should really be kept to the //ReadMe.txt// file, but many authors choose to include this information within the overview for reference. | Version numbers and mission author details should really be kept to the //ReadMe.txt// file, but many authors choose to include this information within the overview for reference. | 
|   |   | 
| ======  Anatomy of the overview.html ====== | ======  Anatomy of the overview.html ====== | 
 |  | 
| <code> | <code html> | 
|  <html><br> |  <html><br> | 
|  <head><title>Overview or anything you like or nothing at all</title></head><br> |  <head><title>Overview or anything you like or nothing at all</title></head><br> | 
| The three displayed elements of this html are | The three displayed elements of this html are | 
 |  | 
|   * A centred title |   * A centered title | 
|   * A centered picture |   * A centered picture | 
|   * One or more sentence descriptions |   * One or more sentence descriptions | 
| The title of the overview (not the html <title> above, the name of the mission this overview represents) comes from one of two sources: | The title of the overview (not the html <title> above, the name of the mission this overview represents) comes from one of two sources: | 
 |  | 
| * The filename of the mission folder will be displayed. Eg Apples.Pbo.Cain OR | * The file name of the mission folder will be displayed. Eg Apples.Pbo.Cain OR | 
| * The briefingName= contained in the //mission.sqm// of the mission folder, written as follows: | * The briefingName= contained in the //mission.sqm// of the mission folder, written as follows: | 
 |  | 
| <code> | <code cpp> | 
|  class Intel |  class Intel | 
|  { |  { | 
| </code> | </code> | 
 |  | 
| It would be rare for you to want the mission filename to be displayed. In order to work 'correctly' | It would be rare for you to want the mission file name to be displayed. In order to work 'correctly' | 
 |  | 
|   * the briefingName= must exist |   * the briefingName= must exist | 
|   * the briefingName= must be different to the filename. |   * the briefingName= must be different to the file name. | 
 |  | 
| There is a "bug" in OFP, in that if the briefing name is identical to the primary name of the mission folder the mission folder is displayed.  | There is a "bug" in OFP, in that if the briefing name is identical to the primary name of the mission folder the mission folder is displayed. | 
 |  | 
| **Example:** folder name apples.cain (or apples.pbo.cain) | **Example:** folder name apples.cain (or apples.pbo.cain) | 
 |  | 
| <code>  | <code cpp>  | 
|  breifingName="apples"; results in the briefing name effectively being ignored. For this reason, you will often see |  breifingName="apples"; //results in the briefing name effectively being ignored. For this reason, you will often see | 
| </code> | </code> | 
 |  | 
| <code>  | <code cpp>  | 
|  breifingName="apples "; (a space is added to force correct display) |  breifingName="apples "; //(a space is added to force correct display) | 
| </code> | </code> | 
 |  | 
| Or, the name of the folder containing the mission has underlines or some other device to make it different. | Or, the name of the folder containing the mission has underlines or some other device to make it different. | 
 |  | 
| **Note:** Filename title is also displayed as a diagnostic aid if you use cheat sequence -campaign. | **Note:** File name title is also displayed as a diagnostic aid if you use cheat sequence -campaign. | 
 |  | 
| **Pictures** | **Pictures** | 
| </code> | </code> | 
 |  | 
| Many simple HTML tags will work in the [[ofp:missions:briefing.html|briefing.html]] or //overview.html//. For an added touch of professionalism, centre your text by adding the following above your main body of description. | Many simple HTML tags will work in the [[ofp:missions:briefing.html|briefing.html]] or //overview.html//. For an added touch of professionalism, center your text by adding the following above your main body of description. | 
 |  | 
| <code> | <code html> | 
|  < p align="center" > |  < p align="center" > | 
| </code> | </code> | 
 |  | 
| A tutorial for creating mission pictures is available Overview Picture. | A tutorial for creating mission pictures is available Overview Picture. | 
|   |  | 
 |  | 
| ====== See Also ====== | ====== See Also ====== | 
 |  | 
| [[ofp:missions:briefing.html|briefing.html]] | [[ofp:missions:briefing.html|briefing.html]] | 
 |   | 
| ====== Resources ====== |   | 
 |   | 
| [[http://www.flashpoint1985.com/index2.html|BI]] has a few tools to get you started. |   | 
 |  |