What follows is mostly second nature and "common" sense practice for experienced players, but puts terms, and mental images to many techniques commonly used in games of Armada. I apologize for any incoherence in advance.
Introduction
Formation flying, in my experience, is probably the single most important aspect of winning at Armada and elevating your game, but it is not the only aspect. Engagement Area Development, or EA Dev, is one of those other elements. A properly developed battlefield can disrupt your opponent's formation, while an improperly utilized obstacle can come back to bite you in the butt. What follows are my thoughts on EA Dev as it relates to Armada. To skip the fluffy definitions and read the other important parts (it's all important), go on to the second reply (Screening).
I lay this out by first defining what I mean when I say engagement area, giving several tidbits of personal experience in using pieces of terrain, going in depth describing various obstacle patterns, and finish with giving some closing thoughts
Definitions:
The engagement area (EA) is first a mental construct, and then a physical manifestation as the battle plays out. As a mental construct, the EA is how you view the battlefield prior to deploying your forces and how you plan to deploy your forces. You do this in order to (IOT) take advantage of obstacles to seize, retain, and exploit that advantage with respect to your opponent's forces and the objective in play. As a manifestation, it is how you react to unfolding events (RNG and maneuver commands) IOT seize, retain, and exploit battlefield advantages.
Development is a part of the mental construct. As a mental construct, for the purposes of Armada, this includes the placing of obstacles and planned deployment of forces. These posts will focus on the mental construct portion of EAs (pre battle) because the manifestation would just be too much.
In short, the EA is where the bulk of the battle takes place, but it has to be more nuanced in your mind than "pew pew" in order to be an effective construct, leading to a devastating manifestation. Thus, EA Dev seeks to establish methods IOT facilitate your strategy and achieve the manifestation you want.
The way I see it, EA Dev should be influenced mainly by your fleet composition, the objective, and by whether or not you think you can out-brawl (table) your opponent (their fleet composition). How big of a win you want should also come into play.
Edited by Parkdaddy




