New Errata Is Up!

http://files.privateerpress.com/op/errata/errata.pdf

What I love about this is they seem to have listened to everything we complained to them about on the forums. Even the changes are in a different colour (we complained about that) and I think everything we bitched about in the forums has been fixed.

Shield Guard - you no longer have to be able to become a target, otherwise works the same. Now you can't change facing to avoid triggering shield guard.

Backswing - the attacks used to be simultaneous which confused a lot of people and introduced unnecessary complication. Now you just make two melee attacks.

Weapon/Head lock - I don't know if I mentioned this but it was causing a lot of consternation on the forums. You could have a light warjack/warbeast lock a colossal and it would be forced to make only melee attacks and lose it's initial attacks in the arc the warbeast/warjack was in. The top Everblight player picked up fairly quickly that with Absylonia she could take a Raek and it could move 7" jump 5" (for 12" move) then lock a colossal, if you then put blight field on the colossal it could not be allocated focus or forced meaning the colossal could not shoot and could not attack the Raek in melee as it would lose the attack from that weapon and not be able to buy more attacks. It seemed a little stupid that a light warbeast could lock a Colossal's arms and it really hurt colossals but now it's been fixed. You can only lock an equal or smaller base.

There was a second complaint about locks, that with the strength difference a lot of warjacks/beasts would be physically unable to break locks done by colossals, this has stayed in place. I don't have a problem with this, Colossals are worth a lot more points than the model they are holding in place and lose the ability to make all of their own attacks as well. It's also a good ability fluff wise, a massive colossal should be able to hold onto a smaller jack without a great deal of difficulty. It's not quite the same as a tiny 4 point Raek neutralising a massive 18-20 point Colossal.

Siege - feat clarified says suffers a damage roll now rather than suffers damage. Though infernals had told people how to work the feat, it had meant that until the clarification suffers damage didn't have a clear meaning or had a different meaning in this context.

His special AOE attack was clarified to not suffer target in melee penalty and not be rerolled against other models. Before the change you could place the AOE over two modeles in melee and it was possible he'd shoot one of them twice. Especially if you put one of your high DEF models in melee with a low DEF enemy model.

Wreck Markers from theme forces - Some theme forces let you place wreck markers and people weren't sure if they had the same restrictions as other terrain (it didn't specify). They do, 3" from other terrain (I am terrible at remembering this rule).

Cankerworm and Scrap Thralls - Could only affect heavy not colossal wreck markers, now colossal wreck markers work the same as heavy wreck markers.

Burst Fire - again Colossals/Gargantuans now work the same as heavies. Burst Fire is a rule a lot of Skorne shooting has that causes additional damage to large targets.

Side Step - only melee attacks (previous errata had limited it only to initial attacks to prevent Molik Karn being able to kill warcasters from 20"+ away).

Jarl's Feat (trollbloods) - Jarl puts down AOEs that among other things allow you to move through terrain and your own models, the errata changed move to advance. Important because move includes things like being slammed by your opponent or pushed, advance is only voluntary movement of the model.

Saeryn's feat - will not affect the everblight Gargantuan. Yep, fair enough. Her feat stops things in her battlegroup from being targetted by melee attacks. Two Gargantuans, which you generally can't kill in a single round anyway with an additional round free from melee attacks (you really aren't going to shoot these guys to death)... was never going to be particularly balanced. Skarre2 received the same treatment last year (her feat could effect battle engines).

There are also a bunch of grammar edits for stuff that was already pretty clear but still technically wrong.