Star Wars Unlimited indirect damage: how to assign it
On this page
Indirect damage in Star Wars Unlimited is unpreventable damage assigned by the receiving player among their own units and base. A unit cannot receive an assignment exceeding its remaining HP. Shield tokens do not prevent this damage and are not removed by it. All indirect damage from one ability is dealt simultaneously.
The player producing the effect determines the affected player as instructed; the receiving player normally chooses the distribution. That division of decisions is the central difference from an effect that simply damages a chosen unit.
Establish the recipient and total first
Read the ability to determine who receives the indirect damage and how much it deals. Do not begin distributing an assumed amount before applying any relevant modification or condition. The actual resolving ability supplies the total.
The receiving player then assigns that total among any number of their units or their base under the indirect-damage rules. This does not grant them permission to put it on an opponent's unit or on a card in the resource zone.
If the ability has special wording about who assigns damage, read it in full. The general procedure here explains the normal case. A card-specific instruction can require additional analysis rather than being ignored because it differs from an introductory example.
Units in both arenas can receive it
Ordinary indirect damage is not limited to the arena of the unit that produced the ability. The recipient can consider their eligible units in both ground and space, as well as the base. The amount is not automatically confined to a single combat.
This differs from choosing what an attacking unit attacks, where arena and Sentinel rules can matter. Indirect damage from an ability is a separate assignment process. Do not import the attack-target restrictions unless the relevant instruction actually calls for an attack.
When presenting your choice, identify each receiving unit and the amount assigned. A clear allocation across both arenas is easier to verify than moving several damage counters while saying only that you will “spread it out.”
Remaining HP sets each unit's ceiling
A unit's remaining HP is its current HP minus damage already on it. Include applicable HP modifiers when calculating the amount. Its printed HP alone may not be the correct ceiling if an upgrade or other effect changes the current value.
Imagine a unit with 5 current HP and 3 damage. It has 2 remaining HP, so you cannot assign all 6 incoming indirect damage to it to absorb the event. At most 2 can be assigned to that unit; the rest needs other legal destinations.
This limit prevents using a nearly defeated unit as an unlimited damage sink. Do not confuse it with ordinary damage effects that can sometimes deal more damage than needed. The indirect assignment rule contains its own explicit restriction for units.
The base offers a different destination
You can assign indirect damage to your base. The rule's stated over-assignment restriction concerns units; do not invent the same unit ceiling for the base merely because both objects have HP. Apply the base's damage and defeat rules normally.
For example, if no units are available, the base is the normal remaining destination. You do not cancel the effect because you would prefer to lose a unit, and you do not create a fictional unit to receive it.
Choosing base damage can preserve a strategically important unit, while choosing legal unit damage can preserve base health. Evaluate the actual board and future threats. The rules permit a distribution; they do not identify one universally optimal choice.
| Object in a simple example | Current HP and damage | Maximum unit assignment |
|---|---|---|
| Ground unit | Five HP, three damage | Two |
| Space unit | Three HP, no damage | Three |
| Unit with an HP modifier | Use modified HP minus damage | Calculate from current values |
| Base | Track its damage normally | Unit-specific ceiling is not its rule |
Shield tokens remain while damage gets through
Indirect damage ignores prevention, including Shield tokens. The comprehensive rules explicitly state that damage is placed as though the unit had no Shields and that those Shields are not defeated or affected by that damage.
Suppose a unit has 4 remaining HP and a Shield token. Assigning 2 indirect damage places that damage on the unit without using the Shield to prevent it. If the unit survives and nothing else removes the token, the Shield remains attached.
That matters for a later ordinary damage event. Do not discard a surviving unit's Shield merely because you placed indirect damage on it. Conversely, do not erase the indirect damage because the Shield is still visibly present.
Damage prevention cannot make an assignment harmless
The unpreventable property also applies to effects saying a unit cannot be damaged. Do not allocate damage to such a unit on the assumption that the ability will absorb it without consequence. The current rules explicitly include those effects among prevention that indirect damage ignores.
Other kinds of interactions need their own analysis. “Unpreventable” describes prevention; it is not permission to ignore every rule concerning a unit or to disregard an effect that changes a different part of the process.
For a complex combination, name the exact cards and identify whether the disputed instruction prevents damage, changes HP, modifies the total or changes another event. A broad label such as “protected unit” is too vague to determine the rules outcome.
One ability deals its allocated damage simultaneously
After making the legal distribution, all indirect damage from that single ability is dealt simultaneously. You do not damage and defeat one unit first, resolve its follow-up effects and then decide where to put the remaining portion of the same event.
This distinction can matter when several units will be defeated or abilities react to damage. Establish the complete allocation before applying the event. Then process the resulting consequences under the normal timing rules.
Separate abilities are separate events. If an effect sequence produces another indirect-damage ability later, use the resulting state for that later event. Do not assume the original allocation permanently locks in how all future indirect damage must be assigned.
The source remains the original damage dealer
Letting the recipient distribute the damage does not make them its dealer. The rules retain the player who controlled the indirect-damage ability as the player dealing the damage. If a unit's ability deals it, that unit is the relevant source under the stated rule.
This can matter for abilities that refer to friendly damage, a particular unit dealing damage or an opponent's effect. Do not change the source attribution merely because the receiving player touched the counters and selected the destinations.
When recording a game, distinguish “player A's ability deals six” from “player B assigns two, two and two.” Those statements describe different roles in the same event and make later trigger questions easier to assess.
Work through a full allocation example
Suppose you receive 6 indirect damage. You control a ground unit with 2 remaining HP, a space unit with 3 remaining HP and a base that can receive damage. Assume no other relevant effects.
One legal distribution is 2 to the ground unit, 3 to the space unit and 1 to the base. Another can preserve one or both units by putting more on the base. Assigning 4 to the ground unit would be illegal because it exceeds that unit's remaining HP.
If the space unit has a Shield, its 3-point assignment still gets through and the Shield does not absorb it. Apply the complete damage event, then handle defeated units and other consequences in the proper timing. The example does not let you postpone part of the allocation until after a defeat trigger.
Choose a distribution with the next action in mind
Before making the choice, consider which units support your next play and how much base damage the opponent could produce afterward. An allocation that preserves every unit can still be a poor decision if it leaves the base exposed to a straightforward follow-up.
Conversely, sacrificing a useful unit can lose an important attack or ongoing effect. Compare these consequences using the actual cards, not only a total HP calculation. Indirect damage offers flexibility, but it does not remove the tactical cost of taking the damage somewhere.
No general article can promise the best allocation for every board. Practise several legal distributions and explain what each preserves. That exercise develops decision-making while keeping rules legality separate from strategic preference.
Verify the final assignment publicly
Announce the total, each destination and the amount. Check unit ceilings using current HP and existing damage, then confirm the numbers add up to the incoming total. Apply the damage without using Shields to prevent it.
Keep the current comprehensive rules available for unusual interactions. The official Lightspeed rules update explains the mechanic's introduction, while the latest rules provide the present procedure. Use the current document if an older article and a revised rule differ.
At an event, ask a judge before resolving a disputed allocation. Give the full ability and board state, including Shields and HP modifiers. That is enough information to assess the proposed distribution without relying on an incomplete memory of another game.
Frequently asked questions
Can a Shield token absorb indirect damage?
No. It is unpreventable, and the rules say the Shield is not defeated or affected by that damage.
Can I assign everything to a unit with one remaining HP?
No. A unit cannot be assigned more indirect damage than its remaining HP.
Can I divide it between ground and space units?
Yes, under the normal procedure you can use your eligible units in both arenas and your base. The ability's full text still matters.