Mission Package

To distribute multiple missions together with assets such as images and dialog, a MSFS developer mode project is used.

Template project

This zip contains an example Devmode project:

8MB

ExampleMissionPack.zip

archive

Open

Download and extract the .zip file. Open the project in MSFS devmode.

Once opened, you need to change the Package name and other details in the project inspector.

And you need to change the OutputDirs for the all asset groups except for the ScenarioFiles asset group.

Replace CompanyName with your name and MissionName with the name of the mission.

Be sure to change the package and folder names, to avoid conflicts with other missions.

Defining your mission pack details

Preparing ScenarioFiles asset group

In the MSFS project editor, edit the OutputDir of the ScenarioFiles asset group. The last part of the OutputDir should exactly match your package name:

Adding missions

Paste your mission files, thumbnail images, and briefing images in the PackageSources\ScenarioFiles\ folder (See: Sharing and Installing Missions).

In that folder, open the MissionPackDefinition.json file:

Edit all the fields with your own information. You can add more files if needed.

You can add multiple briefing images if you want, like this:

"BriefingImage": ["1MissionName_briefing1.jpg", "1MissionName_briefing2.jpg", "1MissionName_briefing3.jpg"]

Generate a random GUID for your mission pack. You can use https://guidgenerator.com/

Adding custom content

Custom Dialog

Follow the steps in Custom Dialog.

Custom Image

Add the custom image(s) to the PackageSources\CustomImage\ folder. In the Custom Image Image Path, you can specify the image like: CompanyName/MissionName/ImageName.jpg

Custom Script

Add the custom script(s) to the PackageSources\CustomScript\ folder. In the Custom Script Script Path, you can specify the script like: Missions\CompanyName\MissionName\CustomScriptName