Special Movements During Deployment

By Loophole Master, in Dust Tactics Rules Discussion

Posted at

heh i did not have that kind of rule discussion in years .....

When i play deployment is ACTION , so you just put unit on the board.

but as i said

rulebook 17pg

"Abilities and Special Units

Important! Whenever a special rule for a special weapon or ability contradicts the
general rules, it is the special rule that prevails!"

which means that FAST rule overwrites deployment rules so you can get extra square becouse "one square move" is move.

going back to horrible deployment rules in rule book page 16.

Attack!
During the first round, the units must enter the gameboard. Their first action on the battlefield
is always a one square move ( ), symbolizing the fact that the unit “enters” the
gameboard.
IF we think about it " one square move" have no sense here unless its just part of MOVE action.
In case of DEPLOYMENT as an action they could just write that unit appears on the board
Example: the Allies player wins the initiative. He chooses to play his Hot Dog
first: the robot has MOVE 1. The Allies player spends this MOVE to enter the gameboard,
Here if it was not part of move allowance whole "HD has 1 movement and spends" has no sense.
Iam probably wrong but this is how it works in RAW ......

Posted at

Major Mishap said:

It doesn't seem right that a Fast unit can move an extra square and a unit that is even faster (M2) can't.

Yeah, which is part of the reason I concluded that Fast can't be used in the deployment action. Deployment is a Move action, but it's a "one square move", so no ability should be able to make it a two square move.

You can use Fast on your second action that turn, just as you can use Charge with that second action as well.

Posted at

Loophole Master said:

Major Mishap said:

It doesn't seem right that a Fast unit can move an extra square and a unit that is even faster (M2) can't.

Yeah, which is part of the reason I concluded that Fast can't be used in the deployment action. Deployment is a Move action, but it's a "one square move", so no ability should be able to make it a two square move.

You can use Fast on your second action that turn, just as you can use Charge with that second action as well.

Okay, I got back to this and looked it up. You are correct that on page 16 it says: "Their first action....is always a one square move (->)..."

However, turning back to the movement rules on page 7 the amount you can move during a MOVE action is the value of the unit's ->. Therefore unless you find a "DEPLOY" action, then a unit with a 2 movement (2->) can move 2x(->) in each MOVE action.

Makes a lot more sense, discards all the extra junk and caveats and doesn't make me refer to the box at the top of the second column on page 4. You really, really don't want to go there when you talk about something being "clearly stated" or that the rules "clearly don't allow" something.

Posted at

Algesan said:


Okay, I got back to this and looked it up. You are correct that on page 16 it says: "Their first action....is always a one square move (->)..."

However, turning back to the movement rules on page 7 the amount you can move during a MOVE action is the value of the unit's ->. Therefore unless you find a "DEPLOY" action, then a unit with a 2 movement (2->) can move 2x(->) in each MOVE action.

Makes a lot more sense, discards all the extra junk and caveats and doesn't make me refer to the box at the top of the second column on page 4. You really, really don't want to go there when you talk about something being "clearly stated" or that the rules "clearly don't allow" something.

Algesan so you are saying that deployment should look like this right

-put unit on table in deployment zone

-its first action have to be regular MOVE

-do as you please (MOVE or ATTACK)

Make sens - less exception based rules no loop "MOVE action that is not MOVE action" or special deployment action .

COOL! i go with this interpretation .