|
Post by Nick P on Apr 3, 2017 10:47:01 GMT -6
TOURNAMENT IS LOCKED. DONT SEND MONEY IF YOU'RE NOT ON THE LIST.
|
|
|
Post by Nick P on Apr 3, 2017 10:59:22 GMT -6
I lied. 1 spot open. Dan K dropped out.
|
|
|
Post by OneEyeRob on Apr 3, 2017 11:07:47 GMT -6
What a Fuckin' Awesome Guy!
Way to go Nick. Crushin this tourney business in Madison's absence.
|
|
|
Post by Nick P on Apr 3, 2017 11:16:32 GMT -6
Yeah and I won't even bring jetbikes and wraithguard to the table either!
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 3, 2017 11:23:41 GMT -6
- 0-1 Super Heavies, Gargantuan Creatures or Lords of War* - If you have any of the above, your opponent always goes first and chooses who Deploys First. No Rolls/Seize
- 0-1 Fortifications*- If you have a Fortification, your opponent always chooses Table Sides and who Deploys First.
The rules for Deployment and First Turn interact in some interesting ways with the tournament rules. Here is the section from the BRB I think it pertinent, its found under the "Standard Deployment Method" section. "The player that deployed first can choose to take the first or second turn. If they decide to take the first turn, their opponent can attempt to Seize the Initiative."If your opponent brings a super heavy, its clear that you decide who deploys first, but I wanted to clarify whether you meant it to force first turn. This has some meta-game advantages I think you may not have considered. For example, if I plan to bring an Alpha strike list that wants to go second (Drop Pod Marines fits this description) then I can purchase a Lord of War and force my opponent to take first turn. Is the intention to give the player without the LOW the decision of first or second turn? If that is the intention then let them choose 1st or 2nd deployment. If they choose to deploy first they'll get to decide whether to take first turn. The fortifications thing likewise has some similar concerns. Is the intention to make Fortifications that unfavorable? As the rules are currently the player without a fortification gets to decide all of the pregame set-up for deployment (Table Sides, Deployment Order, and First Turn). I just wanted to clarify for when I make my list.
|
|
|
Post by Nick P on Apr 3, 2017 11:36:35 GMT -6
The last few tournaments we ran, bringing a LoW meant that the other player always took first turn no matter what, no rolls for seizing the initiative or anything, even if they deployed second. I just added in the deployment aspect so that if the player without the LoW wants, they can force their opponent to deploy first (so they can alpha strike their knight or wraithknight etc).
At such low points values, most people cannot deal with a knight or wraithknight - the least we can do is give the other player a "free shot" at trying to hurt it before it starts rampaging through their list. But it should be a choice and not a given, so I'll change the verbiage so that the non LoW player can CHOOSE who takes the first turn, rather than being "stuck" with it in your example.
Likewise, the fortification rules are intended to discourage things like void shields and landing pads etc. You can bring a fortification if you super want to, but you're going to have a disadvantage in terms of which table half you deploy in and your opponent may force you to deploy first in order to best set their own army up to deal with the fortification. But you will still roll for seizing the initiative as usual, so its a calculated risk by your opponent.
Basically - LoW = randomize the table halves, but the disadvantaged player (read, non LoW) will determine deployment and the first turn and have a shot at weakening the LoW before they get blown away. Fortification = disadvantaged player (non fortification) determines table halves and order of deployment, but the first turn can still be seized.
EDIT: I also changed it from LoW to just super heavies and gargantuan creatures. If you want to bring draigo, for example, you shouldn't be penalized the same way as if you brought a knight or a baneblade.
|
|
|
Post by Eric formerly Eric on Apr 3, 2017 11:52:33 GMT -6
. EDIT: I also changed it from LoW to just super heavies and gargantuan creatures. If you want to bring draigo, for example, you shouldn't be penalized the same way as if you brought a knight or a baneblade. Robot Gullibleman here we go!
|
|
|
Post by Nick P on Apr 3, 2017 12:14:02 GMT -6
. EDIT: I also changed it from LoW to just super heavies and gargantuan creatures. If you want to bring draigo, for example, you shouldn't be penalized the same way as if you brought a knight or a baneblade. Robot Gullibleman here we go! Fuck forgot about him. For some reason I thought he was a GMC though?
|
|
|
Post by Eric formerly Eric on Apr 3, 2017 12:59:41 GMT -6
Nope just an MC. He's not a very large model anyway. Also I'm kinda kidding cause I don't own him
|
|
|
Post by daniel, why on Apr 3, 2017 17:08:00 GMT -6
Sign me up!
|
|
|
Post by daniel, why on Apr 3, 2017 17:08:16 GMT -6
...can I pay you yet?
|
|
|
Post by Nick P on Apr 3, 2017 17:42:10 GMT -6
Dan you're in
|
|
|
Post by Nick P on Apr 3, 2017 17:46:05 GMT -6
Tournament Locked!!
|
|
|
Post by mcsardo on Apr 3, 2017 20:57:13 GMT -6
You hit the nail on the head! Otherwise I'd be playing mine haha Question: are you straight up banning Ynarri? or just the reborn warhost? I.e. could I bring a Ynarri CAD of harlequins with a farseer as an HQ?
|
|
|
Post by Nick P on Apr 3, 2017 21:22:13 GMT -6
The ynarri isn't an army, it doesn't have units - the Ynarri Warhost is a detachment that grants the ynarri faction and soulburst to eldar units taken.
You cannot physically take a Ynarri army without the Warhost. And since it's not a CAD it's out.
|
|