Jump to content

Recommended Posts

I lost 5 marine scouts 5 scions, eisonhorn, 2 bullgryn, 3 infantrymen, 20 wounds off knight.

 

It was "easy." I won the roll to go first and he failed to sieze. Called it top of turn 3. I imagine it will get tougher as they learn the little tricks and combos.

 

My list was 3 commanders, 6 las/plas infantry squads, 2 basilisk, 2 wyvern, manticore, knight crusader, 10 raven guard scouts, eisenhorn, valk, 3 bullgryn, priest, 3 primaris psykers, 5 scions.

 

He brought stormsurge, 2 riptides, 3 broadsides, 2 devilfish, a bunch of pathfinders and firewarriors.

Link to comment
https://bolterandchainsword.com/topic/345354-beat-new-tau-last-night/
Share on other sites

Very happy to hear this. 

 

I believe with the Tau codex GW has more or less implicitly admitted the utter nonsense that the -1 hit proliferation has created. Yes, this is a bit of an obsession to me, but it gives hope to see this apparent change of course.

 

As far as I can see, the only thing that has -1 hit in the codex are Stealth suits, which is ok and makes sense. The Dal'yth 'camouflage field' sept does not, as I initially feared, confer -1 hit across the whole army. I'm pretty sure that a couple of months ago this would have just been the "free -1 hit to all your units over 12 away" we are now so sadly familiar with.

 

If you have a look at the Necron factions recently previewed by WH Community, there is no sign of -1 hit there either. At a glance, it seems to me that the Tau codex is quite balanced, and so far the Necron traits seem ok as well. Perhaps GW is realizing to what extent some of the other recent codexes have messed up the game, and is paying more attention to balance now.

 

Perhaps there is hope. Let us see if now they are able to bring balance to some absurdly abusive stuff that is too late to change around, like the Craftworld codex. I doubt it, but at least these last two codexes seem to limit the damage.

Never forget the only good Tau is a dead Tau - victory for His Guard (and support)! ;) Are there any things in particular that you can share with the barracks to help other commanders to glory against the upstart xenos?

Riptides have "Fly" found that out the hard way when he flew off and shot my bullgryn he was in combat with moments ago.

 

 

Supporting fire is nasty. Multi charge unit A and B, A fired overwatch, B fired supporting overwatch. B fires overwatch, A fired supporting overwatch.

Never forget the only good Tau is a dead Tau - victory for His Guard (and support)! ;) Are there any things in particular that you can share with the barracks to help other commanders to glory against the upstart xenos?

Supporting fire is nasty. Multi charge unit A and B, A fired overwatch, B fired supporting overwatch. B fires overwatch, A fired supporting overwatch.

Uh, no! The supporting overwatch rule states that if your unit uses it, it is not allowed to shoot overwatch ever again this phase. Even if they are charged directly afterwards from another unit.

 

But maybe another valid sequence would be, just now that I think about it:

Multi charge unit A and B, A fired overwatch, B fires overwatch, B fired supporting overwatch, A fired supporting overwatch.

 

I am not sure this is legal. But I don't have my codex with me, so I can't read up on it.

Order of operations shows it is still illegal.

 

If unit A fires overwatch, unit B must decide then and there to fire overwatch with Supporting Fire. All units declare whether they are firing Overwatch at once, as part of the same phase, since they are both being charged.

 

In the scenario presented, Supporting Fire provides no benefit.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.