Shield guard works now!
burstfire working for skorne, not a +3 but what the hey.
backswing's no longer simultaneous... huh...
Thank the lord the archangel is immune to saeryn's feat.
Shield guard works now!
burstfire working for skorne, not a +3 but what the hey.
backswing's no longer simultaneous... huh...
Thank the lord the archangel is immune to saeryn's feat.
nom nom nom
If you search for Back swing in the rules forum there are plenty of threads about timing issues with it, but basically the main problem as I see it was the whole having to declare the target for both attacks before rolling to hit with either... I think they probably just got fed up with the many many problems people had with it, especially when logically it would make sense for them to be sequential rather than simultaneous...
Zerkova: Fools! How hard can it be to kill one measily elf? Where the hell is he anyway?
Narn: I is in your base, killing all your doodz!
Zerkova: Harsh!
And here I was hoping for some Mountain King love.
Too soon I guess. Too soon.
-L
Poor Vigilant. Oh well, barely anyone took you anyway.
Grab your pick, grab your shovel, head on down to the Amish rumble!
Siege's ground pounder got a lot better.
Missed that one apparently.
Requested page could not be found.
Page not found!![]()
"You must seek out the saint of the ring!"
Not happy with the lock errata PP! The Raek and a few of the light jacks with open fist got some play because of this previously nifty trick now you render them obsolete.
Locking large based models would force them to use their action if they couldn't find help to free them from the lock. Light jacks and beast dont see that much play as it is, please just make the lock errata to Collosals.
Khador Power Supreme!
The change to Breach was a nice surprise, though. The ruling about "suffer damage == suffer a damage *roll*, not damage > (ARM * 1/2)" was already around, but the errata wording means that the auto-damage from a Defender's hammer or a Lancer/Thorn's cortex damage does not cause Breach to go away on the affected model.
Semper Paratus Apparatus Belli
Woldwatcher is in the almost identical situation.
I think we have to play this but its a huge buff to heavies with shields. I guess it doesn't matter too much to Menoth, they hit plenty hard, but the Woldwatcher was used as an effective -2ARM buff to the most heavily armoured heavies and that actually let us have a chance of destroying them.
Lets see.
Am I the only one for whom the supplied errata link doesn't work?
Use the link on this page... it works...
http://privateerpress.com/organized-play
Lonely Monk http://lonelymonk.wordpress.com/
The two highest achievements of the human mind are the twin concepts of "loyalty" and "duty." Whenever these twin concepts fall into disrepute ? get out of there fast! You may possibly save yourself, but it is too late to save that society. It is doomed.
New link available, some gremlins got into mainframe and started causing havoc.
http://files.privateerpress.com/op/errata/errata.pdf
Damn! File not found. Right. Which one of you buggers stole it? C'mon, fess up.
![]()
charges stop once you contact an obstacle (which a wall is) it has been clarified befor that if you may "advance through without penalty" then you dont contact the obstacle. both wordings allow them to charge across a wall.
This thread just got 20% cooler because of Rainbow Dash.
My Gator Paintings
My Cryx Paintings
My PINK Khador Thread!
atm, I don't see why you couldn't use Pthag's feat on the Archangel.
the gargantuan rules say it cannot be placed, but this only applies while the gargantuan is actually in play. if thagrosh is feating to bring it back, its rules are not in play until it is once more in play. which doesn't occur until the feat is complete, and the model is already placed.
my head hurts.
I realize this sounds odd, but doesn't makes a sort of sense? I would honestly just prefer PP to flat out state he can't by changing his feat to say no huge bases. otherwise this will be argued a lot, and I'd rather save myself the headache.
anyway, this is a loophole that I can see.
oh, and link broken![]()