AoS FAQ is out. Bastiladon is god

that is literally the associated ability lmao

 

Clarity on skink chiefs, having multiple endless spells, realmshaper, and basti.

Nerfs to rippers and scaly skin.

kinda lame, kinda expected. The realmshaper is the lamest to me. Pretty much guarantees that you'll never play it in a competitive game unless you know you can outdrop them and reach it first.

Basti is still only ok IMO, but i do think their armor mechanic is a pretty interesting solve to creating a tough monster without it being busted.

 

Anyway, now it doesn't matter at all. We cannot use it - that's it.

 

I honestly never thought Scaley applied to MWs anyways, so it isn't a big change to me *shrug*.

 

It should hypothetically have applied to MW inflicted by attacks (hearthguard poleaxes, etc)

It makes our trades with Fyreslayers a little more lopsided but oh well.

 

No RAW it wouldn't. Mortal wounds are not caused by attacks.
You misunderstanding the way the rules work isn't the same thing as RAW.

 

That's not true. If you have 6 mortal wounds as 1 packet of 6 wounds that "ignore saves and determine damage" steps it would still be 6 mortal wounds that would need to be allocated. I'm not sure what you are arguing here.

Unlike the 40k rules, age of sigmar rules never state that MW are individual instances of damage.

 

I seriously don't understand why they didn't just write this down. A 1+ just makes it look like it can ignore the rule about natural 1's always failing, whereas writing it like this leaves no room for arguments.

Seperating the abilities that units solely have because they have a certain weapon from the actual attack made with said weapon because at some point some genius saw it necesary to define what an "attack" is, is stupid & game-y.

Though in fairness, literally all of the caveats surounding scaly skin are stupid and game-y. It is overly niche, virtually useless against some armies while almost providing 50% damage reduction against others for no real reason, which as a faction ability is rather absurd. Also the strict seperation of "attack" and "ability" is contrived as hell. Just look at a stegadon, it's crushing stomps are stopped by scaly skin, it's unstoppable stampede ignores scaly skin. Both the attack and the ability represent the exact same thing; namely a stegadon stomping on your face. But due to some arbitrary definitions one is exempt, the other isn't. There's no logical reason for this to be so. But for some reason GW has gone for this confusing scheme.

A rule should not be that confusing...

On a sidenote, why have attacks actually been defined as a seperate thing to begin with?​

​

​

​

That depends, did the ability trigger once doing 6 mortal wounds? Or did it trigger 6 times doing 1 wound each? For clarity, something like flamethrowers hitting once per model in the target unit would trigger multiple times for 1 damage. Something like arcane bolt triggers once for multiple damage.

If it's once for multiple damage than scaly skin should logically protect you.​

 

Yeah, I dont know too many things with multiple MWs. Off the top of my head from things I have seen/faced.

1) Hearthguard
2) Terrorgeists
3) Longstrikes & Jezzails (hurts our heroes as scaly skin provided some potentially strong anti-sniping buffs)

 

Yep, Saurus could actually trade surprisingly well with Fyreslayers before this.

 

Only if you were playing the game wrong

 

I've never faced Fyreslayers. If I encounter any, some little tips when facing them?

 

I'll echo this and also say Purple Sun

I wonder how much scaly skin will effect our DoT matchup. I know they have tons of mortals, but d3 damage on the flamers seems like it'll take a nice hit from scaly skin.

 

Attacks are regular weapon rolls that must roll to hit, wound, save, and determine damage.
An ability or spell that deals mortal wounds is not an attack.
An ability that is tied to a weapon (such as sunfire thrower) is not an attack.
An ability that activates during an attack (such as on an unmodified hit roll of 6) is still not an attack.
Mortal Wounds generated during an attack sequence are allocated at the same time as all other damage (eg after the unit has finished making all of its attacks) but they are still not an attack.

As @Jason839 mentioned earlier in this thread GW has been using text like "Do not use the attack sequence" and "the attack sequence ends" to convey this is how the game works. It has always worked this way but they are now adding specific text to help clarify, similar to how Mounts were added as a concept in GHB2017 but were never properly defined until Soul Wars.

This was not an errata because they did not change anything about the game. You were playing the game wrong, and they have clarified the correct way to play.