Spearhead 1944 Scenario Creation Guide - Revision history

R3vo: R3vo moved page Spearhead 1944: Scenario Creation Guide to Spearhead 1944 Scenario Creation Guide

2025-09-07T09:52:19Z

R3vo moved page Spearhead 1944: Scenario Creation Guide to Spearhead 1944 Scenario Creation Guide

← Older revision	Revision as of 11:52, 7 September 2025
(No difference)

Lou Montana: Fix hl template issue

2025-05-22T21:27:25Z

Fix hl template issue

← Older revision		Revision as of 23:27, 22 May 2025
Line 160:		Line 160:
	[[File:spe scenario guide layers.png\|1024px]]		[[File:spe scenario guide layers.png\|1024px]]

	As you may have noticed, I am ~~{{hl\|}}~~using ~~“SPE_”~~ frequently as a prefix to help make clear any and all custom variable names. We did this out of necessity for the CDLC, I am doing this optionally for my own unofficial projects simply because it helps me stay organized and clear on what I have input into the system. In addition to the prefix, I am trying to include in all custom names, a little detail on what the thing is, for example:		As you may have noticed, I am using "SPE_" frequently as a prefix to help make clear any and all custom variable names. We did this out of necessity for the CDLC, I am doing this optionally for my own unofficial projects simply because it helps me stay organized and clear on what I have input into the system. In addition to the prefix, I am trying to include in all custom names, a little detail on what the thing is, for example:

	* {{hl\|SPE_var_x}} is used for a variable		* {{hl\|SPE_var_x}} is used for a variable

R3vo: added link to the scenario

2025-03-23T16:19:44Z

added link to the scenario

← Older revision		Revision as of 18:19, 23 March 2025
Line 6:		Line 6:
	This guide was created by {{Link\|https://steamcommunity.com/id/h34dup/myworkshopfiles/\|HeadUp}} and is additionally avaiable as flipbook [https://issuu.com/h34dup/docs/arma_3_scenario_editing_guide_the_making_of_the_l here]!<br />		This guide was created by {{Link\|https://steamcommunity.com/id/h34dup/myworkshopfiles/\|HeadUp}} and is additionally avaiable as flipbook [https://issuu.com/h34dup/docs/arma_3_scenario_editing_guide_the_making_of_the_l here]!<br />
	[[File: spe scenario guide flipbook.jpg\|250px]]		[[File: spe scenario guide flipbook.jpg\|250px]]
			<br/><br/>
			You can find the link to the scenario '''''The Lock''''' {{Link\|https://drive.google.com/file/d/1WuckrMjweG5_av3Lax2YpcKH_OWASsR3\|here}}.
	}}		}}

	In this guide, I will share my process for creating the singleplayer scenario, "''The Lock''", a simple airborne infantry-based mission taking place during the early hours of Operation Overlord during WWII. In creating this guide, my hope is that details of my approach to mission making will help fellow Arma editors, whether it’s introducing a new technique or confirming the way you already work, so players at large can enjoy more quality community-authored scenarios.		In this guide, I will share my process for creating the singleplayer scenario, '''''The Lock''''', a simple airborne infantry-based mission taking place during the early hours of Operation Overlord during WWII. In creating this guide, my hope is that details of my approach to mission making will help fellow Arma editors, whether it’s introducing a new technique or confirming the way you already work, so players at large can enjoy more quality community-authored scenarios.

	A sliver of background on myself for those curious. I have been a longtime gamer and modder, starting with Medal of Honor: Allied Assault in 2001, and releasing mods of various sizes and levels of popularity for Call of Duty 1 and 2, Company of Heroes, Skyrim, {{arma2}}, and most recently, {{arma3}}. Games of the Arma series are unique in that they offer a platform for exploring realistic tactical and strategic scenarios, that, with CDLC and mods covering a wide range of historical conflicts and settings, empowers modders and editors to bring history to life. Whether its units playing amazing and painstakingly created ops based on real historical actions, elaborate screenshot art that tricks the eye into thinking it’s a real photograph, or a virtual ocean of addons, it’s a community unlike any other. It was this hobby of reading real accounts of combat and attempting to render them in Arma that got my scenarios noticed by HOW and ultimately led to my involvement in [[Spearhead 1944]]. So, it’s in that spirit that I created The Lock, and as such that I’ll lay out this guide.		A sliver of background on myself for those curious. I have been a longtime gamer and modder, starting with Medal of Honor: Allied Assault in 2001, and releasing mods of various sizes and levels of popularity for Call of Duty 1 and 2, Company of Heroes, Skyrim, {{arma2}}, and most recently, {{arma3}}. Games of the Arma series are unique in that they offer a platform for exploring realistic tactical and strategic scenarios, that, with CDLC and mods covering a wide range of historical conflicts and settings, empowers modders and editors to bring history to life. Whether its units playing amazing and painstakingly created ops based on real historical actions, elaborate screenshot art that tricks the eye into thinking it’s a real photograph, or a virtual ocean of addons, it’s a community unlike any other. It was this hobby of reading real accounts of combat and attempting to render them in Arma that got my scenarios noticed by HOW and ultimately led to my involvement in [[Spearhead 1944]]. So, it’s in that spirit that I created The Lock, and as such that I’ll lay out this guide.

R3vo: Adding links and formatting

2025-03-23T15:35:52Z

Adding links and formatting

← Older revision		Revision as of 17:35, 23 March 2025
Line 190:		Line 190:

	=== Systems and Modules ===		=== Systems and Modules ===
	I will often include any initial systems and~~/or~~ modules early on. [[Spearhead 1944]] comes with a number of modules that help editors to easily implement a detailed suite of features and improvements and unlock a more authentic WWII gameplay experience. These modules include:		I will often include any initial systems and modules early on. [[Spearhead 1944]] comes with a number of modules that help editors to easily implement a detailed suite of features and improvements and unlock a more authentic WWII gameplay experience. These modules include:

	Ambient War Sounds - to help give the sense that players are on a battlefield		* Ambient War Sounds - to help give the sense that players are on a battlefield
	AI Systems - to improve everything from combat behavior to adding flee/retreat/surrender		* {{Link\|Spearhead 1944 AI Systems (AIS)}} - to improve everything from combat behavior to adding flee/retreat/surrender
	Enhanced Revive - to ensure single players have access to healing if they are incapacitated (note that we can easily turn this on or off for the player using a script command)		* {{Link\|Spearhead 1944 Enhanced Revive (ER)}} - to ensure single players have access to healing if they are incapacitated (note that we can easily turn this on or off for the player using a script command)
	Indirect Fire Support - to give players access to devastating fire support options with deep customization (in this case, I want players to have limited access to only 3 artillery strikes)		* {{Link\|Spearhead 1944 Indirect Fire Support (IFS)}} - to give players access to devastating fire support options with deep customization (in this case, I want players to have limited access to only 3 artillery strikes)

	Additionally, I like to use other systems like the Cover Map module to help players focus and know where the intended “playable area” is, the Animals module to add furry friends for increased immersion in the countryside, and the Show Terrain Object and Edit Terrain Object modules to adjust small details in the terrain in support of the gameplay (eg. useful for removing a rock or a tree when a tank’s path keeps getting stuck because of it).		Additionally, I like to use other systems like the '''Cover Map module''' to help players focus and know where the intended “playable area” is, the Animals module to add furry friends for increased immersion in the countryside, and the '''Show Terrain Object''' and '''Edit Terrain Object''' modules to adjust small details in the terrain in support of the gameplay (e.g. useful for removing a rock or a tree when a tank’s path keeps getting stuck because of it).

	Each of these systems is organized into the layers mentioned above. Less important but worth noting is that most if not all of these systems have names with SPE_sys_ prefix, as it can be useful if you want to target a specific system.		Each of these systems is organized into the layers mentioned above. Less important but worth noting is that most if not all of these systems have names with {{hl\|SPE_sys_ prefix}}, as it can be useful if you want to target a specific system.

	For more information on SPE Modules, check the Biki:		For more information on SPE Modules, check the Biki:

R3vo: /* Animated Units */

2025-03-23T11:41:33Z

Animated Units

← Older revision		Revision as of 13:41, 23 March 2025
Line 378:		Line 378:

	=== Animated Units ===		=== Animated Units ===
	In addition to both static and patrolling units, I will often place units that have AI disabled and switchMove playing a looping animation. These units are there to help establish a scene. While there are different ways to achieve this, I typically only place these types of units either in a starting area away from the action, or some initial phase to be hidden once combat kicks off, since simulated AI units in combat and AI-disabled units with looping animations don’t mix well. Basically, I will place a unit into a group (they can be all this way or part of a mixed unit with some units that can patrol, just don’t make an animated unit a group leader), disableAI “PATH”, “MOVE”, and “ANIM” followed by switchMove with an animation selected from the Animations Viewer tool. While units animated in this way have been shown to hog less engine power than the slightly more robust and editor-friendly ~~bis_fnc_ambientAnim~~, it’s still necessary to clean them up once they’ve served their purpose. I typically either delete or hide and desimulate these units in their layers once the opening phase is over or the starting area props are no longer within player view.		In addition to both static and patrolling units, I will often place units that have AI disabled and switchMove playing a looping animation. These units are there to help establish a scene. While there are different ways to achieve this, I typically only place these types of units either in a starting area away from the action, or some initial phase to be hidden once combat kicks off, since simulated AI units in combat and AI-disabled units with looping animations don’t mix well. Basically, I will place a unit into a group (they can be all this way or part of a mixed unit with some units that can patrol, just don’t make an animated unit a group leader), disableAI “PATH”, “MOVE”, and “ANIM” followed by switchMove with an animation selected from the Animations Viewer tool. While units animated in this way have been shown to hog less engine power than the slightly more robust and editor-friendly [[BIS_fnc_ambientAnim]], it’s still necessary to clean them up once they’ve served their purpose. I typically either delete or hide and desimulate these units in their layers once the opening phase is over or the starting area props are no longer within player view.

	=== Presence, Vantage Points, and Strong Points ===		=== Presence, Vantage Points, and Strong Points ===

R3vo: /* Make a Marker Sketch */ fixed typo

2025-03-23T11:40:20Z

Make a Marker Sketch: fixed typo

← Older revision		Revision as of 13:40, 23 March 2025
Line 52:		Line 52:
	Thirdly, bear in mind your own skill level in the Editor. Even if you’re no scripting guru (I’ll be the first to admit I am not a scripting guru, tbh I consider myself barely more than a novice), there’s no reason you can’t put together an awesome and fun scenario using only the basics. If you have the skill and experience, the sky really is the limit, but the point is not to bite off more than you can chew. The process I lay out in this guide should help you avoid wasting a lot of time for a mission that fundamentally can’t work in Arma before you’ve had a chance to change it so it does work, but it’s always best to know what you’re capable of. And of course, there is ample support online from the excellent BI wiki and forums to discord and beyond, so take this all into account and don’t sell your idea short if you know where to go to get your idea working.		Thirdly, bear in mind your own skill level in the Editor. Even if you’re no scripting guru (I’ll be the first to admit I am not a scripting guru, tbh I consider myself barely more than a novice), there’s no reason you can’t put together an awesome and fun scenario using only the basics. If you have the skill and experience, the sky really is the limit, but the point is not to bite off more than you can chew. The process I lay out in this guide should help you avoid wasting a lot of time for a mission that fundamentally can’t work in Arma before you’ve had a chance to change it so it does work, but it’s always best to know what you’re capable of. And of course, there is ample support online from the excellent BI wiki and forums to discord and beyond, so take this all into account and don’t sell your idea short if you know where to go to get your idea working.

	=== Make a Marker ~~Scetch~~ ===		=== Make a Marker Sketch ===
	[[File:spe scenario guide sketch 1 bridgehead.jpg\|500px]] [[File:spe scenario guide sketch 2 droueries.jpg\|500px]]		[[File:spe scenario guide sketch 1 bridgehead.jpg\|500px]] [[File:spe scenario guide sketch 2 droueries.jpg\|500px]]

	OK enough about ideation, let’s have some fun and put “pen to paper” by creating a marker sketch. Here are a few marker sketches I came up with for the Carentan terrain for example.		OK enough about ideation, let’s have some fun and put “pen to paper” by creating a marker sketch. Here are a few marker sketches I came up with for the Carentan terrain for example.

R3vo: /* Start with the History */

2025-03-23T11:39:07Z

Start with the History

← Older revision		Revision as of 13:39, 23 March 2025
Line 41:		Line 41:
	The first step in my process is to get inspired (and educated) about the history of the terrain. For [[Spearhead 1944]] 1.0 and 1.1, the entire HOW team was deeply immersed in historical research. We got our hands on real After Action Reports, along with historical accounts from multiple different sources, and explored how they might play out on the terrains. This kind of explorative play can help you understand what works best in the {{arma3}} engine and can likely fill up a modest list of initial ideas.		The first step in my process is to get inspired (and educated) about the history of the terrain. For [[Spearhead 1944]] 1.0 and 1.1, the entire HOW team was deeply immersed in historical research. We got our hands on real After Action Reports, along with historical accounts from multiple different sources, and explored how they might play out on the terrains. This kind of explorative play can help you understand what works best in the {{arma3}} engine and can likely fill up a modest list of initial ideas.

	{{Feature\|informative\|~~TIP:~~		{{Feature\|informative\|I suggest coming up with multiple ideas before you dig in, your first idea isn’t always your best, and try not to be too precious about your vision at this stage, be open to significant changes while you haven’t sunk much time in if those changes will make your scenario better.}}
	I suggest coming up with multiple ideas before you dig in, your first idea isn’t always your best, and try not to be too precious about your vision at this stage, be open to significant changes while you haven’t sunk much time in if those changes will make your scenario better.}}

	=== Initial Gameplay Considerations ===		=== Initial Gameplay Considerations ===

R3vo: S.O.G._Prairie_Fire to S.O.G. Prairie Fire

2025-03-23T11:38:20Z

S.O.G._Prairie_Fire to S.O.G. Prairie Fire

← Older revision		Revision as of 13:38, 23 March 2025
Line 417:		Line 417:
	The other area I always give some attention to is the starting area of the mission. I often find that, unless the player is meant to start the mission aboard some insertion vehicle, a vacant mission starting area is a big missed opportunity. Just as the set pieces help tell the story, the player’s starting area should also help orient the player to the side they’re on, the condition of their unit, how well-supplied (or not) they are, and the overall combat intensity. For The Lock, I decided that the starting area should not be built up, practically at all, aside from a makeshift command post outside Addeville, where a small contingent in-game representing a larger bulk of the 101st that had set up there, can be found by curious players.		The other area I always give some attention to is the starting area of the mission. I often find that, unless the player is meant to start the mission aboard some insertion vehicle, a vacant mission starting area is a big missed opportunity. Just as the set pieces help tell the story, the player’s starting area should also help orient the player to the side they’re on, the condition of their unit, how well-supplied (or not) they are, and the overall combat intensity. For The Lock, I decided that the starting area should not be built up, practically at all, aside from a makeshift command post outside Addeville, where a small contingent in-game representing a larger bulk of the 101st that had set up there, can be found by curious players.

	As a rule, while the player should quickly be able to “get in the action” this action should be some safe distance from the starting area, and the action should commence as appropriate once the player leaves that starting area. Another way to think about it is that the starting area can and should serve as a mini-showcase, akin to the faction showcases included in CDLCs like [[S.O.G.~~_Prairie_Fire~~]] and [[Spearhead 1944]]. Using the named layer hide technique, or even simple dynamic simulation to de-simulate at a certain distance, depending on the design of your scenario, you should be able to clean up anything happening that is no longer needed.		As a rule, while the player should quickly be able to “get in the action” this action should be some safe distance from the starting area, and the action should commence as appropriate once the player leaves that starting area. Another way to think about it is that the starting area can and should serve as a mini-showcase, akin to the faction showcases included in CDLCs like [[S.O.G. Prairie Fire]] and [[Spearhead 1944]]. Using the named layer hide technique, or even simple dynamic simulation to de-simulate at a certain distance, depending on the design of your scenario, you should be able to clean up anything happening that is no longer needed.

	Finally, regarding the “starting experience,” while it’s not an immediate concern at this stage of the process, I am mindful of what the player sees upon mission load, considering what they might see on screen without touching the keyboard or mouse for a few seconds, and what information I can give them in just that initial shot. A silhouetted scene that evokes the classic “Band of Brothers” title sequence is what felt right for The Lock, together with a bit of BGM added later. To achieve this, I lined up a group of AI units, part of the “Reserve Element” I had waypoints set for them to essentially bring up the rear as the player fought their way south. All units in this group would be disableAI on path, move, and anim, and I added “warmup” animations to give them the dramatic poses they have. When the player triggered the Reserve Element to move up (after securing the checkpoint), in the group’s Waypoint #1, the one following their initial synced waypoint, I added in the on activation field, commands to enableAI and a default animation to reset their animation state so the AI could resume normal movement. In this way, I achieved a memorable opening scene without wasting the AI units by leaving them animated behind at the starting area.		Finally, regarding the “starting experience,” while it’s not an immediate concern at this stage of the process, I am mindful of what the player sees upon mission load, considering what they might see on screen without touching the keyboard or mouse for a few seconds, and what information I can give them in just that initial shot. A silhouetted scene that evokes the classic “Band of Brothers” title sequence is what felt right for The Lock, together with a bit of BGM added later. To achieve this, I lined up a group of AI units, part of the “Reserve Element” I had waypoints set for them to essentially bring up the rear as the player fought their way south. All units in this group would be disableAI on path, move, and anim, and I added “warmup” animations to give them the dramatic poses they have. When the player triggered the Reserve Element to move up (after securing the checkpoint), in the group’s Waypoint #1, the one following their initial synced waypoint, I added in the on activation field, commands to enableAI and a default animation to reset their animation state so the AI could resume normal movement. In this way, I achieved a memorable opening scene without wasting the AI units by leaving them animated behind at the starting area.
Line 479:		Line 479:

	=== Promo Images ===		=== Promo Images ===
	The final thing we’ll need some screenshots for are for promotional purposes. These shots will go on your Steam Workshop page for the scenario. They should be exciting and enticing to players above all. While you can stage these shots or capture them from live play, you should be mindful of creating a false impression as to what players should expect to actually play. For this reason, and again for the sake of ease, for The Lock, I captured all my promo shots (except, as noted, the overview image) by swooping around the AO while the mission was playing out and capturing engagements between AI-controlled belligerents. It was actually a cool challenge trying to hunt for skirmishes by listening for gunfire, and then seeing the dangerous exchanges of fire with the Splendid Camera set to a time scale of 0.1, like in the Matrix. By doing it this way, I can assure players that they are likely to experience the gameplay they see in the screenshots. For other projects, particularly my [[S.O.G.~~_Prairie_Fire~~]] releases, I will include some staged shots that still nail the vibe of the play experience, but offer a little more cinematic and visual flare. In the end, the choice is yours, but you’ll notice the difference some great promo images will have on converting curious players into subscribers of your scenario.		The final thing we’ll need some screenshots for are for promotional purposes. These shots will go on your Steam Workshop page for the scenario. They should be exciting and enticing to players above all. While you can stage these shots or capture them from live play, you should be mindful of creating a false impression as to what players should expect to actually play. For this reason, and again for the sake of ease, for The Lock, I captured all my promo shots (except, as noted, the overview image) by swooping around the AO while the mission was playing out and capturing engagements between AI-controlled belligerents. It was actually a cool challenge trying to hunt for skirmishes by listening for gunfire, and then seeing the dangerous exchanges of fire with the Splendid Camera set to a time scale of 0.1, like in the Matrix. By doing it this way, I can assure players that they are likely to experience the gameplay they see in the screenshots. For other projects, particularly my [[S.O.G. Prairie Fire]] releases, I will include some staged shots that still nail the vibe of the play experience, but offer a little more cinematic and visual flare. In the end, the choice is yours, but you’ll notice the difference some great promo images will have on converting curious players into subscribers of your scenario.

	== Step 7: Releasing Your Scenario ==		== Step 7: Releasing Your Scenario ==

R3vo: /* Presence, Vantage Points, and Strong Points */

2025-03-23T11:37:37Z

Presence, Vantage Points, and Strong Points

← Older revision		Revision as of 13:37, 23 March 2025
Line 381:		Line 381:

	=== Presence, Vantage Points, and Strong Points ===		=== Presence, Vantage Points, and Strong Points ===
	As for where to place units, this is one way to achieve remarkably varied results, depending on many factors, including the terrain, available CPU, and player/AI behavior. Where you place the units, especially static units, matters a lot! I developed a reputation, even before working on [[Spearhead 1944]], with many of my [[S.O.G.~~_Prairie_Fire~~]] missions, for brutal placement of ambushers in every inconvenient corner. I spend a fair amount of time in the editor not only imagining the story of my protagonists, but also thinking in detail about enemy presence, direction of movement, and motivation. I also utilize the “Presence” attribute for the majority of AI combat units to add an element of randomness and improve replayability factor, most of the time setting unit probability of presence to simple values like 25%, 33%, 50%, 66%, or 75%. Of course, many units should be present every time, but I will often place turrets, mines, and other threats randomly.		As for where to place units, this is one way to achieve remarkably varied results, depending on many factors, including the terrain, available CPU, and player/AI behavior. Where you place the units, especially static units, matters a lot! I developed a reputation, even before working on [[Spearhead 1944]], with many of my [[S.O.G. Prairie Fire]] missions, for brutal placement of ambushers in every inconvenient corner. I spend a fair amount of time in the editor not only imagining the story of my protagonists, but also thinking in detail about enemy presence, direction of movement, and motivation. I also utilize the “Presence” attribute for the majority of AI combat units to add an element of randomness and improve replayability factor, most of the time setting unit probability of presence to simple values like 25%, 33%, 50%, 66%, or 75%. Of course, many units should be present every time, but I will often place turrets, mines, and other threats randomly.

	[[File:spe scenario guide vantage.jpg\|1024px]]		[[File:spe scenario guide vantage.jpg\|1024px]]

R3vo: /* Notifications and Hints */ removed _ from SOG

2025-03-23T11:36:21Z

Notifications and Hints: removed _ from SOG

← Older revision		Revision as of 13:36, 23 March 2025
Line 472:		Line 472:
	For the Lock, I wanted to make the terrain feature, the Lock at La Barquette, a prominent one. This would help tell the story and set player expectations. Even though it was a staged photo, players can reach the very same position and expect a somewhat similar firefight coming at them from the other side of the canal! For [[Spearhead 1944]], we painstakingly composed hundreds of images, the majority of which were done by hand. I especially enjoyed recreating real historical photos from Operation Cobra as black and white photos captured in the game. However, for the average time-strapped editor, this won’t be feasible nor worth the time and effort. For this reason, if you only dedicate any real effort to staging one shot, make it the overview image, as it’s the most important one.		For the Lock, I wanted to make the terrain feature, the Lock at La Barquette, a prominent one. This would help tell the story and set player expectations. Even though it was a staged photo, players can reach the very same position and expect a somewhat similar firefight coming at them from the other side of the canal! For [[Spearhead 1944]], we painstakingly composed hundreds of images, the majority of which were done by hand. I especially enjoyed recreating real historical photos from Operation Cobra as black and white photos captured in the game. However, for the average time-strapped editor, this won’t be feasible nor worth the time and effort. For this reason, if you only dedicate any real effort to staging one shot, make it the overview image, as it’s the most important one.
	Task Images		Task Images
	Task images, present for nearly all tasks in both [[S.O.G.~~_Prairie_Fire~~]] and [[Spearhead 1944]] are an important way to guide the player with some visual clues about their objective. The task images can depict anything from the location within the terrain to a specific vehicle or unit that the player should target.		Task images, present for nearly all tasks in both [[S.O.G. Prairie Fire]] and [[Spearhead 1944]] are an important way to guide the player with some visual clues about their objective. The task images can depict anything from the location within the terrain to a specific vehicle or unit that the player should target.

	I forgot to mention above, that with task images and overview images, they should be converted to .paa file format using TexView2, part of Arma Tools, which you can access for free via Steam. Note that .paa files will need to be in specific dimensions, often a 1:1 or 1:2 ratio, and divisible by 8 - eg. 1024x512px. I typically will need to crop my screenshots to fit this requirement. Once cropped and in the correct format, you can easily drag it into TexView2 and save as a .paa. These .paa files are then added to your mission folder and can be referred to in description.ext or your task description entries - note that the syntax for each will vary.		I forgot to mention above, that with task images and overview images, they should be converted to .paa file format using TexView2, part of Arma Tools, which you can access for free via Steam. Note that .paa files will need to be in specific dimensions, often a 1:1 or 1:2 ratio, and divisible by 8 - eg. 1024x512px. I typically will need to crop my screenshots to fit this requirement. Once cropped and in the correct format, you can easily drag it into TexView2 and save as a .paa. These .paa files are then added to your mission folder and can be referred to in description.ext or your task description entries - note that the syntax for each will vary.