arma3:missions
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
arma3:missions [2016/10/31 14:19] – added good old 2d mission editor header. snakeman | arma3:missions [2024/08/02 15:59] (current) – links added. snakeman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Missions ====== | + | ====== |
- | This is all about missions | + | [[https:// |
- | **Campaign Missions** | + | This page is all about missions and campaigns for [[: |
- | mission\description.ext | + | | [[arma3: |
- | <code cpp> | + | | [[arma3: |
- | author = "Snake Man"; // Author | + | | [[arma3: |
- | onLoadName = "PMC 2 mission"; // Mission | + | |
- | onLoadMission = " | + | |
- | class CfgDebriefing | + | [[arma3: |
- | { | + | [[arma3: |
- | class End1 | + | [[arma3: |
- | { | + | [[arma3: |
- | title = "End1 Activated"; | + | [[arma3: |
- | subtitle = ""; | + | [[arma3: |
- | description = "Yeah end1 rulez"; | + | [[arma3: |
- | backgroundPicture = ""; | + | [[arma3: |
- | picture = " | + | [[arma3: |
- | pictureColor[] = {0.0, | + | |
- | }; | + | |
- | class pmc1 | ||
- | { | ||
- | title = "PMC 1 Activated"; | ||
- | subtitle = ""; | ||
- | description = "Yeah pmc1 rulez"; | ||
- | backgroundPicture = ""; | ||
- | picture = " | ||
- | pictureColor[] = {0.0, | ||
- | }; | ||
- | }; | ||
- | </ | ||
- | |||
- | Then any script or trigger during mission to end it: | ||
- | <code cpp> | ||
- | [ " | ||
- | </ | ||
- | |||
- | Or | ||
- | <code cpp> | ||
- | [ " | ||
- | </ | ||
- | |||
- | Its very cool now that we can define our own mission ending setups and are not limited to the existing 7 mission ending triggers available. | ||
- | |||
- | |||
- | ====== ArmA 3 Campaign description.ext ====== | ||
- | |||
- | **ArmA 3 Campaign description.ext** | ||
- | |||
- | This following inside every **mission** class is not necessary: | ||
- | <code php> | ||
- | briefingName = " | ||
- | author = "Snake Man"; | ||
- | overviewText = " | ||
- | </ | ||
- | Because these values are read from the mission description.ext instead. | ||
- | |||
- | When you are creating your ArmA 3 campaign and if you get this error: | ||
- | < | ||
- | Warning Message: No entry ' | ||
- | </ | ||
- | You need to add one line in description.ext file: | ||
- | < | ||
- | briefingName = "My Campaign!"; | ||
- | </ | ||
- | And its fixed. | ||
- | |||
- | |||
- | ====== ArmA 3 Campaign saveStatus and weaponPool ====== | ||
- | |||
- | **exit.sqf** | ||
- | |||
- | exit.sqf script wont run from campaign\scripts\ directory at mission end, it has to be in each mission dir :( | ||
- | |||
- | **saveStatus** | ||
- | |||
- | If you do saveStatus and then try to loadStatus on different class character, you have no uniform/ | ||
- | |||
- | **FIA Randomized Headgear** | ||
- | |||
- | In v1.44 at least FIA rhs_g_Soldier_F seems to have randomized headgear and goggles (glasses), even with saveStatus/ | ||
- | <code php> | ||
- | this setVariable [" | ||
- | </ | ||
- | |||
- | |||
- | ====== ArmA 3 Campaign Editing Tips ====== | ||
- | |||
- | Make empty mission with only red markers designating the mission areas, not individual objectives but main mission area, for example main objective for specific mission. | ||
- | |||
- | Then when you actually create these missions, you can then load this marker only mission and after each mission is done, you turn that objective / area marker to green. | ||
- | |||
- | With this you can very easily keep track of the campaign creation and which missions are done, which areas are covered etc. | ||
- | |||
- | Another idea is to first build all the player side troops + triggers and do dry run of the campaign to see all missions end nicely. I mean surely you already only place triggers that work, of course, but still it would be nice to go over the campaign basic design actually playing it, instead of just watching .ext and .sq? files. | ||
- | |||
- | Put trigger activation lines in sqf scripts, easier to edit and manage / find. PMC Fury had lot of " | ||
- | |||
- | Unique and descriptive names for scripts! No more fish.sqf shit, there is no shame using even very long sqf names if necessary. If script can be used in several missions, do it and put it on Scripts\ directory with good parameters. | ||
- | |||
- | |||
- | ====== Misc ====== | ||
- | |||
- | **ArmA 3 Mission file name length**, see [[arma2: | ||
- | |||
- | |||
- | ====== Steam Subscription ====== | ||
- | |||
- | When you subscribe to a mission, steam client / ArmA 3(?) creates SteamPreviewCache\ directory in your profiles dir, it places preview image of the mission there (assuming, if one is available). | ||
- | |||
- | Mission is available from Scenarios -> Subscriptions. When you select the mission there and click PLAY, then the mission is downloaded. | ||
- | |||
- | Mission is placed on your **profiles \Users\YOURNAME\Saved\steam\** directory. | ||
- | |||
- | |||
- | ====== Good Old 2D Mission Editor ====== | ||
- | |||
- | Do you think eden editor is not ready yet? Do you think its too fancy for its own good? Do you think it sucks? | ||
- | |||
- | No problems, you can still launch the good old 2D editor we all learned to use since OFP times. In ArmA 3 main menu click / choose Editor, then in the terrain selector screen use shortcut **CTRL-O** and it will start the 2D editor. |
arma3/missions.1477923558.txt.gz · Last modified: 2016/10/31 14:19 by snakeman