Rules Reference Corrections

[Guest AMG_Luke]

This thread contains official corrections to the current version of the Star Wars: Legion Rules Reference. These corrections supersede the authority of the Rules Reference. These corrections will be deleted whenever the Rule Reference is updated. 

[Guest AMG_Luke]

Rules Reference Correction: In the “Transported” entry, subsection “Transport X: Open,” the following bullet point should be considered removed: 

• While a unit is being transported, its weapons lose all fixed keywords.

 

In its place the following bullet point should be considered added:

• While a transported unit is performing an attack, it ignores the restrictions of any fixed keywords on its weapons (the weapons are still considered to have fixed keywords for the purposes of other game effects).

 

This resolves an unintended interaction with the transport x: open keyword and the generator upgrades. 

[Guest AMG_Luke]

Rules Reference Correction: In the “Standby” entry, the following bullet point should be considered added:

• Repulsor vehicles cannot perform the standby action and cannot gain or spend standby tokens. If a repulsor vehicle would gain a standby token through a game effect, the token is returned to the supply instead.

 

This resolves an issue with repulsor vehicles gaining standby tokens via Lando Calrissian’s command card Ace Up His Sleeve. Note that repulsor vehicles with the hover: ground keyword ignore this rule. 

[TalkPolite]

Rules Reference Correction: In the “Barricade” entry the following bullet point should be added: 

• Barricades cannot be placed overlapping objective or condition tokens.

 

This resolves an unintended interaction caused by placing barricades with the "Fortified Positions" condition card and objective tokens. 

[TalkPolite]

Rules Reference Correction: In the Detachment: Unit Name/ Type (Unit Keyword) entry, the following bullet point should be considered removed: 

• During the Deploy Units step of Setup, a unit with the detachment keyword must be placed at speed-1 and within height 1 of a unit leader from a friendly unit that has the unit name or type specified by the detachment keyword.

 

In its place the following bullet point should be considered added:

• During the Deploy Units step of Setup, the unit leader of a unit with the detachment keyword must be placed at speed-1 and within height 1 of a unit leader belonging to a friendly unit that has the unit name or type specified by the detachment keyword.

 

This resolves an unintended interaction with miniature placement in units with multiple minis and the detachment keyword. 

[TalkPolite]

Rules Reference Correction: In the Embark/Disembark entry the following bullet point should be removed: 

• A unit that is being transported can use its standby token to disembark.

 

In its place the following bullet point should be considered added:

• A unit that is being transported by a vehicle with transport X: open can use its standby token to disembark; a unit transported by a vehicle with transport X: closed cannot spend standby tokens.

 

This resolves an unintended interaction with transport x: closed units. 

[TalkPolite]

Rules Reference Correction: In the Base Contact entry the following sub-bullet point should be removed:

» Second, the vertical space separating the two bases is less than the thickness of a standard Star Wars: Legion base.

 

In its place the following sub-bullet point should be considered added:

» Second, the vertical space separating the two bases is less than the thickness of a standard Star Wars: Legion base. Or, if players are using the official silhouette found in the Star Wars: Legion Tournament Regulations, the vertical space separating the two bases is less than the height of the official silhouette.

 

This resolves an unintended issue with units that are under overhanging bases. 

[TalkPolite]

Rules Reference Correction: In the Repulsor Vehicle Movement Summary subsection of the Movement entry, the following bullet point should be removed:

• While performing a standard move, reverse, or strafe, a repulsor vehicle mini can move onto or over a piece of a terrain that has a height that is equal to or less than the height of the unit leader’s mini.

In its place the following bullet point should be considered added:

• While performing a standard move, reverse, or strafe, a repulsor vehicle mini can move onto, over, or off of a piece of a terrain that has a height that is equal to or less than the height of the unit leader’s mini.

This resolves an unintended interaction where Repulsor Vehicles such as the AAT and Saber tank could not move off of terrain that has a height that is equal to or less than the height of the unit leader’s mini. 

[TalkPolite]

Rules Reference Correction: In Speeder X the following bullet point should be removed:

• During a move, a unit that has the speeder x keyword can move over terrain equal to or less than height x.

In its place the following bullet point should be considered added:

• During a move, a unit that has the speeder x keyword can move over terrain equal to or less than height x. Measure the height from the unit leader's starting position.

The following bullet point should also be considered added:

• During a move, a unit that has the speeder x keyword may end its movement at any height lower than its starting position, regardless of the value of x.

This resolves unintended difficulty with speeder movement. 

[TalkPolite]

Rules Reference Correction: In the Ion X entry, the following bullet point should be considered removed: 

• At the start of the “Roll Defense Dice” step, before any other effects, if the attack pool includes the ion x keyword, for each hit or critical result, up to x, the defender must flip an active shield token if able. The defender does not add block results for shield tokens flipped in this way

In its place the following bullet point should be considered added:

• If an attack pool as the ion x keyword, During the Apply Dodge and Cover step of the attack, the defender must apply any other effects (such as dodge tokens and cover) before flipping active shield tokens. Then, for each hit or critical result remaining up to x, where x is the value of the ion x keyword, the defender must flip an active shield token to its inactive side. Shield tokens flipped in this way do not cancel a hit or critical result. After doing so, if any active shield tokens remain, the defender may flip them to cancel hit or critical results as normal. 

This removes an unintended interaction where Shield tokens could be spent before ion: x takes effect. 

[TalkPolite]

Rules Reference Correction: In the “Melee” entry the following bullet point should be considered added: 

• When either player is placing their minis in base contact with an enemy unit, they must place their minis in such a way that as many of their minis can be placed in base contact as possible.

This gives players clear direction for how to place their miniatures in a melee.

[TalkPolite]

Rules Reference Correction: In Embark and Disembark the following bullet point should be removed:

• When a unit disembarks, if the vehicle that is transporting that unit has performed more than one standard move or reverse during the current round, disembarking uses that unit’s entire activation and it cannot perform additional actions or any free actions.

In its place the following bullet point should be considered added:

• When a unit disembarks, if the vehicle that is transporting that unit has performed more than one non-pivot move during the current round, disembarking uses all of its available actions, and it cannot perform additional actions or any free actions.

This resolves an unintended interaction where a unit with transport could strafe twice, and the unit inside could disembark and still take its entire activation. 

[TalkPolite]

Rules Reference Correction: In Withdraw the following bullet should be removed: 

• To withdraw a unit must use its entire activation and spend all of its available actions to perform a single speed-1 move

In its place the following bullet point should be considered added:

• To withdraw a unit must spend all of its available actions to perform a single speed-1 move and it cannot perform additional actions or any free actions.

[TalkPolite]

Rules Reference Correction: In Embark and Disembark the following bullet should be removed: 

• To embark into a transport with the transport x: closed keyword, a unit spends its entire activation to perform a speed-1 move that puts its unit leader into base contact with a friendly vehicle that can transport that type of unit.

In its place the following bullet point should be considered added:

• To embark into a transport with the transport x: closed keyword, a unit must spend two actions to perform a speed-1 move that puts its unit leader into base contact with a friendly vehicle that can transport that type of unit.

[Guest AMG_Luke]

Rules Reference Correction: In the “Wounds” entry the following bullet point should be considered added: 

• A unit leader cannot be chosen to suffer wounds, unless it is the only mini in the defending unit that is in line of sight of the attacker, if it is the only wounded mini in the unit, or if it is the last mini in the unit.

This bullet point was unintentionally removed in a previous update. 

[TalkPolite]

Rules Reference Correction: In the “Barricades” entry the following bullet point should be considered added: 

• Barricades that have been nominated with an objective token cannot be moved by game or player effects. 

This bullet point was added to prevent Barricades nominated as objectives from being moved by cards such as "Force Lift". 

[TalkPolite]

Rules Reference Correction: In the “Divulge” entry the following bullet point should be considered added:

• If a command card is Divulged during the "Deploy Units" step, its effect persists until the end of the "Deploy Units" step, even if it is discarded.

This bullet point was added to prevent an unintended timing gap with Divulge cards and keywords gained from them.

[TalkPolite]

Rules Reference Correction: In the “End Phase” entry the following bullet point should be considered removed:

• 2. Remove Tokens: Players remove all aim, dodge, and standby tokens, as well as one suppression token from each unit.

In its place the following bullet point should be considered added:

• 2. Remove Tokens: Players remove all aim, dodge, surge, smoke, observation and standby tokens, as well as one suppression token from each unit.

This bullet point was amended to confirm which tokens should be removed at the end of each game round. 

[TalkPolite]

Rules Reference Correction: In the “Barricades” entry the following bullet point and sub bullet point should be considered removed:

• Typically, barricades do not provide vehicles with cover.
  • » However, barricades can provide cover to vehicles if, when declaring terrain during Set Up, the barricade obscures half or more of that vehicle. For example, barricades can provide heavy cover to both standing and ball-form droidekas minis, the X-34 Landspeeder, and the TX-225 GAVw Occupier.

The following bullet point should be considered added:

• Barricades do not provide vehicles with cover.

[AMG_Pagani]

Rules Reference Correction: In the “Standby” entry the following bullet point should be considered removed: 

• If a ground vehicle unit performs a move, an attack, or an action, it removes any standby tokens it has. 

In its place the following bullet point should be considered added:

• If a ground vehicle or unit with the hover air/ground keyword performs a move, an attack, or an action, it removes any standby tokens it has.

[TalkPolite]

Rules Reference Correction: In the “Line of Sight” entry the following bullet points should be considered removed: 

• When determining line of sight from an E-Web Heavy Blaster Team mini, players should check from the top of the head of the snowtrooper who is firing the E-Web, regardless of whether it is directly over the center of the base.
• When determining line of sight from a DF-90 Mortar Trooper Mini, players should check from the top of the head of the shoretrooper who is firing the mortar, regardless of whether it is directly over the center of the base.
•  When determining line of sight from a TX-225 GAVw Occupier, players should check from the center of the roof of the crew compartment, regardless of whether it is directly over the center of the base.

 

In its place the following bullet point should be considered added:

• When determining line of sight from the following units, use the provided guidelines. Each ruling is used regardless of whether it is directly over the center of the base. 
  • DF-90 Mortar Trooper: Check from the top of the head of the shoretrooper who is firing the mortar.
  • E-Web Heavy Blaster Team: Check from the top of the head of the snowtrooper who is firing the E-Web.
  • LAAT/LE Patrol Transport: Check from the top of the cockpit glass where it meets the body of the LAAT.
  • TX-225 GAVw Occupier: Check from the center of the roof of the crew compartment.
  • Infantry Support Platform: Check from the angle of the middle support beam, between the two seats.
  • Raddaugh Gnasp Fluttercraft: Check from the top of the chassis, directly above the pilot miniature. 
  • TX-130 Saber-Class Fighter Tank: Check from the notch in the center of turret’s guard, which is above the front-most edge of the top hatch. 
  • AAT Trade Federation Battle Tank: Check from the point where the gun barrel meets the turret
  • DSD1 Dwarf Spider Droid: Check from the top of the spider droids body, where the base of the antenna meets the center of the miniature. 
  • NR-N99 Persuader-class Tank Droid: Check from the top of the body in the center of the wheel. 
  • STAP Riders: Check from the top of the head of the B1 unit leader.
  • A-A5 Speeder Truck: Check from the top of the front middle hatch.
  • AT-RT: Check from the top of the rider's head. 
  • T-47 Airspeeder: Check from the top of the cockpit glass.