Starting a mission PT2 - Global-Conflicts-ArmA/Olsen-Framework-Arma-3 GitHub Wiki
Now that we've created the mission file and mounted the framework to it, we can go in-game and begin to edit and place basic mission features you'll do each time you create a new mission.
Editing basic mission details
General
We want to edit basic details of the mission such as name and author. To do this, while in the editor, at the top bar click Attributes > General.
Title
- The name of your mission, the same as the mission file we created in PT1, but with spaces instead of underscores _
, and also your mission version at the end.
Author
- The name of the mission maker(s).
Picture
- Leave this blank.
Text
- Shows a short description of the mission in the mission selection screen, add your mission description here.
Require DLC
- Untick this box.
If you scroll down to the next two tabs, you'll see Overview and Overview (Locked).
There's no need to have these different from each other so copy.
Picture
- Here we will add our loading image for the mission. Enter the file path, name, and file format, i.e images\MyLoadingImage.jpg
Text
- Shows a short description of the mission while loading into the mission.
- Note that only .JPG and .PAA files are supported.
Multiplayer
Once you've done general, move to multiplayer. To do this, while in the editor, at the top bar click Attributes > Multiplayer.
Gametype
- You can pick any of these, it doesn't matter. Although it's good practice to choose appropriately.
Min Players
- The minimum number of players the mission is designed.
Max Players
- The maximum number of players the mission will allow connected at one time.
- If you have spectator slots, make sure this number accounts for the playable units and the spectator slots.
Summary
- This is a short description of the mission with important brief info shown in the lobby/role selection screen.
- If this mission is a COTVT or TVT, you MUST put the team ratios at the start in the following format so our ratio calculator can give the correct ratio:
1:2
The calculator reads the ratio in order of the sidesblufor
,opfor
,indfor
, so if you wanted a ratio of for every 1 blufor player, there are two opfor player, you'd write1:2
, or if you wanted the same ratio but for indfor to also have players, you'd give them a ratio also such as1:2:1
Decimal points are supported, so you can create ratios like1.7:3:0.5
Enable AI
- Untick this box.
Singeplayer death screen
- Untick this box.
Headless Client
All missions need a Headless Client module.
- On the right side of the editor, click the icon, followed by the icon.
- In the search bar, type
headless client
, under virtual Entities click the headless client module and place it into your world/map.
https://user-images.githubusercontent.com/4511118/224704484-56a1292d-d537-4cbd-b55f-99325b5b143e.mp4
- Double click on the Headless Client module you just placed on the map and edit it's details.
variable name
- Putheadlessclient
in this field.
Playable
- Tick this box Do not click PLAYER
Role Description
- Putheadlessclient
in this field also.
Spectator
Lets say you created and placed all playable units for clients to connect to, you were set on the number and player limit for the mission, but still wanted clients to connect and at least be able to spectate, this is where the Spectator module comes in to play.
- On the right side of the editor, click the icon, followed by the icon.
- In the search bar, type
virtual spectator
, under virtual Entities click the spectator module and place it into your world/map.
https://user-images.githubusercontent.com/4511118/224708244-187b5a02-d9f4-4063-a4d0-0e72e7118832.mp4
- You must place an individual Virtual Spectator module for each client you wish to be able to join the spectator role.
- Double click on the spectator module you just placed on the map and edit it's details.
In the control tab:
Playable
- Tick this box Do not click PLAYER
Role Description
- Put Spectator
in this field.
In the virtual Spectator tab:
Here you can tick or untick any of these optionally, although typically ticking all is applicable.