Mission Save File – Operation Flashpoint: Elite

Latest revision as of 20:32, 31 January 2021

The Directory Tree

The directory tree looks something like this.

UDATA                    Default directory for all games.
  434d005a               The game title folder.  
      BD22517280DF       A generated number representing the user save.
         ...             More user saves
      A160043E221B       A generated number representing another user save

Notes:

OFP:Elite will automatically generate a number representing the mission save, you have no control over this, it just happens.

OFP:Elite will accept folder names, such as MyMissionName. Its possible to rename the mission folder name to somthing sensible, which can help in archiving and sharing missions.

Contents of user created save

Within subfolder 434d500a, there should be the following files:

TitleImage.xbx           //Image File
TitleMeta.xbx            //TitleName=Operation Flashpoint: Elite
SaveImage.xbx            //Image File
A subfolder named with an obscure name like "BD22517280DF"

Within subfolder of the mission save, the following files should exist:

SaveMeta.xbx             
saveimage.xbx            
header.bin               
mission.par

SaveMeta.xbx

The savemeta.xbx file is a UTF8 (unicode) encoded text file with details of the mission name and the profile name used to create the mission save.

Although readable (and unfortunately) writeable by text editors such as notepad, be aware that this is not 'simple' single-character-style text.

Header.Bin

The header.bin file contains information about the mission owner (user profile), the type of mission (Multi Player vs Single Player), the mission name, and the template used to create the mission.

This file is also rAP'd and signed by the OFP: Elite engine.

Notes

In order to allow you to play a PC mission on OFP: Elite, it is the templates option that you need to modify and point to your mission save folder.

Example:

Template=U:\MyMissionName;

Mission.par

The mission.par file is the meat of the mission. The file is much like the PC version of the mission.sqm file, it contains the details of the units placed in the editor, any waypoints the user has created, along with the time, date, weather settings.

This file has some special properties, the file is rAP'd and signed by the OFP: Elite engine.

Action Replay Notes

Keep in mind when preparing your mission for the Action Replay application these points.

1. All files must be zipped up into a single archive to be recognized by the AR (the name of the ZIP archive seems inconsequential).

2. The first sub folder within this archive should be named "UDATA"

Note There is a size restriction in how large mission can be. The Action Replay application will accept any size of mission, however when one tries to copy the save back through the Xbox memory manager you will receive an error. Safe sizes so far have been aroudn 500k. Missions over 1024k seem to fail.

@@ Line 1: / Line 1: @@
-==Introduction==
+== The Directory Tree ==
-==The Directory Tree==
 The directory tree looks something like this.
@@ Line 18: / Line 14: @@
 OFP:Elite will <u>automatically</u> generate a number representing the mission save, you have no control over this, it just happens.
-OFP:Elite doesn't mind normal names, such as '''MyMissionName'''.
+OFP:Elite will accept folder names, such as '''MyMissionName'''. Its possible to rename the mission folder name to somthing sensible, which can help in archiving and sharing missions.
-==Contents of user created save==
+== Contents of user created save ==
@@ Line 37: / Line 33: @@
   mission.par
-===SaveMeta.xbx===
+=== SaveMeta.xbx ===
 The '''savemeta.xbx''' file is a UTF8 (unicode) encoded text file with details of the mission name and the profile name used to create the mission save.
@@ Line 43: / Line 39: @@
 ''Although readable (and unfortunately) writeable by text editors such as notepad, be aware that this is '''not''' 'simple' single-character-style text.''
-===Header.Bin===
+=== Header.Bin ===
 The '''header.bin''' file contains information about the mission owner (user profile), the type of mission (Multi Player vs Single Player), the mission name, and the template used to create the mission.
@@ Line 57: / Line 53: @@
 '''Example:'''
-  Template=U:\MyMissionName
+  Template=U:\MyMissionName;
-===Mission.par===
+=== Mission.par ===
 The '''mission.par''' file is the meat of the mission. The file is much like the PC version of the [[Mission.sqm|mission.sqm]] file, it contains the details of the units placed in the editor, any waypoints the user has created, along with the time, date, weather settings.
@@ Line 65: / Line 61: @@
 This file has some special properties, the file is rAP'd and signed by the OFP: Elite engine.
-==Action Replay Notes==
+== Action Replay Notes ==
 Keep in mind when preparing your mission for the Action Replay application these points.
@@ Line 72: / Line 68: @@
 *2. The first sub folder within this archive should be named "UDATA"
+'''Note''' There is a size restriction in how large mission can be. The Action Replay application will accept any size of mission, however when one tries to copy the save back through the Xbox memory manager you will receive an error. Safe sizes so far have been aroudn 500k. Missions over 1024k seem to fail.
+{{GameCategory|ofpe}}