The first and largest home of the Ogre Kingdoms — preserved.
Filter by date range
Standalone from the search box above — this queries Pagefind
directly and checks each result's date itself, since the packaged search
widget can only match a single exact date, not a range.
So I was thinking of experimenting with yhetees, as I have had 6 painted models lying around since the original army box set came out in 2004, but haven't really used them that much. apart from the odd game or two.
Am I getting this right:
If an enemy unit fails a fear-test against a unit of Yhetees and have their weapon-skill redued to 1, the frost aura will further reduce it to 0. This will not only make the yhetees auto-hit but will also disable the opponent from attacking me?
This is how the other ogre players in my club interprets the rule, and alsohow Iread it although I find it a bit too awsome to believe.
Shadowlord12 Mar 2013
You will auto hit but the opponent is still able to strike back - hitting on 6s.
At least that is how our gaming club use it/read the rules as.
My hood is my castle...
hardyworld12 Mar 2013
You play it the way I play it.
Some people argue that units with WS0 are auto-hit, but can still attack and hit by the "always hit on 6s" rule. But the way I read the rules, units with WS0 have no weapon ability at all, which means they have no viable attacks with which to hit. Similar to how a model with BS0 and and a ranged weapon cannot use the weapon at all (A saurus oldblood with a Staff of the Lost Sun for example).
8th Edition OK Record Crushing Victory: 5 Victory: 4 Draw: 1 Loss: 10 Crushing Loss: 3
7th Edition OK Record Massacre: 3 Solid Victory: 4 Minor Victory: 3 Draw: 2 Minor Defeat: 2 Solid Defeat: 4 Massacred: 5
grey templar12 Mar 2013
The aura only effects models in BtB.
So if the unit fails a fear test all the models in base contact with the yhetees will be WS0 and everyone else will be WS1.
As the Yhetees are only in BtB with WS0, they will hit automatically. The models with WS0 will only hit on 6s(as a 6 always hits) and everyone else will hit on 5s.
Current win streak: 10
Things Fluffy,my Stonehorn, has flattened: Ancient Stegadon, Unit of 5 Chariots with Tomb king, Chaos Lord, Herald of Khorne on Jugger, x58 Forever steadfast (\__/) (='.'=) (")_(") This is Bunny________ This is bunny after a Thunderstomp
grey templar12 Mar 2013
You play it the way I play it.
Some people argue that units with WS0 are auto-hit, but can still attack and hit by the "always hit on 6s" rule. But the way I read the rules, units with WS0 have no weapon ability at all, which means they have no viable attacks with which to hit. Similar to how a model with BS0 and and a ranged weapon cannot use the weapon at all (A saurus oldblood with a Staff of the Lost Sun for example).
That is incorrect, having "no ability to fight" is purely fluff text. And the actual rules simply say that WS0 is automatically hit, it doesn't say they may not attack. The only way they can hit is by using the 6s always hit rule.
Current win streak: 10
Things Fluffy,my Stonehorn, has flattened: Ancient Stegadon, Unit of 5 Chariots with Tomb king, Chaos Lord, Herald of Khorne on Jugger, x58 Forever steadfast (\__/) (='.'=) (")_(") This is Bunny________ This is bunny after a Thunderstomp
hardyworld13 Mar 2013
It is a rule, not fluff text. A Saurus Oldblood is BS 0 and, therefore, not allowed to use a ranged weapon. Similarly, a unit with WS 0 is, therefore, not allowed to use a close combat weapon. The rule is printed on page 4. I understand why people think the "always hit on 6's" rule supersedes the above rule (and I understand why I believe the opposite), but you cannot ignore a part of a rule (dismissing it at fluff) just because that part is not 100% clear. In addition to having "no ability whatsoever in that skill", the next paragraph states that blows against units with WS0 automatically hits. This additional clarification was needed to supplement the first paragraph because opposing units trying to hit units with WS0 need to know what is required to hit them. Such a clarification is not needed for any other characteristic because the only other opposing roll that is affected by a target's characteristic is Toughness, and the third paragraph states such an occurrence cannot happen because a T0 target cannot exist (it should already be removed from the game as a casualty).
Which rule takes precedence is the only unclear item. Characteristics of 0 or Roll to Hit (a natural dice score of 6 always hits)
My opinion is that the former takes precedence and no to hit rolls may be attempted.
This should probably be moved to the rules forum.
8th Edition OK Record Crushing Victory: 5 Victory: 4 Draw: 1 Loss: 10 Crushing Loss: 3
7th Edition OK Record Massacre: 3 Solid Victory: 4 Minor Victory: 3 Draw: 2 Minor Defeat: 2 Solid Defeat: 4 Massacred: 5
grey templar13 Mar 2013
Except the BS0 and being disallowed from using a ranged weapon is explicitly stated. WS0 has no such qualifier saying they may not use melee weapons.
Current win streak: 10
Things Fluffy,my Stonehorn, has flattened: Ancient Stegadon, Unit of 5 Chariots with Tomb king, Chaos Lord, Herald of Khorne on Jugger, x58 Forever steadfast (\__/) (='.'=) (")_(") This is Bunny________ This is bunny after a Thunderstomp
Shadowlord13 Mar 2013
Except the BS0 and being disallowed from using a ranged weapon is explicitly stated. WS0 has no such qualifier saying they may not use melee weapons.
Yep, it is as true as it is written.
My hood is my castle...
SeBM13 Mar 2013
Except the BS0 and being disallowed from using a ranged weapon is explicitly stated. WS0 has no such qualifier saying they may not use melee weapons.
Yep, it is as true as it is written.
Well if you look at the to hit table, WS 0 doesn't allow anyone to hit anyone... And then it's explicitly said that WS 0 is autohit by anyone.
Armies played: Ogre Kingdoms and Lizardmen Record in 8th : W / L / D Ogre Kingdoms: 9 / 2 / 0
Shadowlord13 Mar 2013
That is true, but it also add the line about hitting on 6s.
My hood is my castle...
grey templar13 Mar 2013
Except the BS0 and being disallowed from using a ranged weapon is explicitly stated. WS0 has no such qualifier saying they may not use melee weapons.
Yep, it is as true as it is written.
Well if you look at the to hit table, WS 0 doesn't allow anyone to hit anyone... And then it's explicitly said that WS 0 is autohit by anyone.
Normally this would be the case. If GW hadn't added the line that you always hit on a natural roll of a 6
Current win streak: 10
Things Fluffy,my Stonehorn, has flattened: Ancient Stegadon, Unit of 5 Chariots with Tomb king, Chaos Lord, Herald of Khorne on Jugger, x58 Forever steadfast (\__/) (='.'=) (")_(") This is Bunny________ This is bunny after a Thunderstomp
SeBM13 Mar 2013
One could argue that since WS0 isn't on the table, it isn't able ever to attack, since it's not in the realm of possibilities on the chart. The always hit on 6 I feel was intented so that penalties never make it so that you can't hit.
I really don't mind much, those situation rarely occurs, I was just trying to be smart haha.
Armies played: Ogre Kingdoms and Lizardmen Record in 8th : W / L / D Ogre Kingdoms: 9 / 2 / 0
vred13v27 Apr 2013
as bad as GW is with some rules, i believe they would have explicitly stated that a unit with WS0 hits on 6's when attacking, if they were allowed to attack
honestly, i dont care, i dont use yhettees often enough that it comes up
grey templar28 Apr 2013
One could argue that since WS0 isn't on the table, it isn't able ever to attack, since it's not in the realm of possibilities on the chart. The always hit on 6 I feel was intented so that penalties never make it so that you can't hit.
I really don't mind much, those situation rarely occurs, I was just trying to be smart haha.
No, because GW included the "6s always hit" rule they can always hit on a 6. Regardless of being on the table or not.
Current win streak: 10
Things Fluffy,my Stonehorn, has flattened: Ancient Stegadon, Unit of 5 Chariots with Tomb king, Chaos Lord, Herald of Khorne on Jugger, x58 Forever steadfast (\__/) (='.'=) (")_(") This is Bunny________ This is bunny after a Thunderstomp
Opens a new GitHub Issue pre-filled with a link back here — sign in with GitHub to post. If someone already restarted this thread, please add to that issue instead of opening a second one.