Class StratConDeploymentOrders

java.lang.Object
mekhq.campaign.digitalGM.stratCon.StratConDeploymentOrders

public final class StratConDeploymentOrders extends Object
Deployment Orders: how a contract's command rights are felt on the map. Every so often the employer orders the player to move a formation to a position in the Area of Operations, placed as a point of interest that is also a strategic objective (see StratConDeploymentOrderBehavior). Letting one lapse costs the player a Complete Success.

How many orders come is set by the contract's command step (see getCommandStep(mekhq.campaign.mission.contract.contractData.ContractCommandRights, mekhq.campaign.universe.Faction)): its command rights, shifted by how controlling the employer is. Each month brings the command step's worth of orders per point of the contract's Scale, rounded normally, each on its own random day of the month:

Deployment Orders per month, by command step
StepOrders
0None (Independent, or a lenient employer under Liaison command rights)
11 x Scale (Liaison)
22 x Scale (House)
33 x Scale (Integrated)
44 x Scale (Integrated, under a controlling employer)
Since:
0.51.01
  • Method Details

    • getCommandStep

      public static int getCommandStep(@Nullable ContractCommandRights commandRights, @Nullable Faction employerFaction)
      Works out how tightly the employer directs the contract. Liaison command rights start at step 1, House at 2, and Integrated at 3; a controlling employer then adds a step, and a lenient one takes one away. Independent command rights are always step 0, however controlling the employer is: the player answers to no one on the ground.
      Parameters:
      commandRights - the contract's command rights, or null if it has none
      employerFaction - the contract's employer, or null if it has none
      Returns:
      the command step, from 0 to 4
      Since:
      0.51.01