Switch Theme:

Rules listing things and using i.e.  [RSS] Share on facebook Share on Twitter Submit to Reddit
»
Author Message
Advert


Forum adverts like this one are shown to any user who is not logged in. Join us by filling out a tiny 3 field form and you will get your own, free, dakka user account which gives a good range of benefits to you:
  • No adverts like this in the forums anymore.
  • Times and dates in your local timezone.
  • Full tracking of what you have read so you can skip to your first unread post, easily see what has changed since you last logged in, and easily see what is new at a glance.
  • Email notifications for threads you want to watch closely.
  • Being a part of the oldest wargaming community on the net.
If you are already a member then feel free to login now.




Made in gb
Norn Queen






Three rules I have found seem to have contradictory statements in them. They say they can apply to many things, but then use "i.e." which suggests it only works on that specific thing.

Dark Eldar Combat Drugs: Serpentin: +1 Weapon Skill (i.e. WS 3+ becomes WS 2+)

Tau Early warning override: If an enemy unit is set up within 12" of a model equipped with an early warning override as the result of an ability that allows them to arrive mid-battle (i.e. teleporting to the battlefield), the model may immediately shoot at that unit as if it were your Shooting phase.

Space Marine Storm of Fire: Each time you roll a wound roll of 6 or more for a friendly <CHAPTER> unit within 6" of the Warlord in the Shooting phase, the Armour Penetration characteristic of that attack is increased by 1 (i.e. AP0 become AP-1, AP-1 becomes AP-2)

Am I reading too much into this or can it be argued that, for example, the Tau EWO can't be used to attack units who use Grav Chutes rather than teleport, or that an AP -3 weapon (Like a Plasma Pistol) won't benefit from Storm of Fire? Note that the Deathwatch special ammunition uses e.g., so they do make a distinction.

This message was edited 1 time. Last update was at 2017/08/20 22:34:30


 
   
Made in gb
Potent Possessed Daemonvessel





Why Aye Ya Canny Dakkanaughts!

Think you're reading way too much into that.

Ghorros wrote:
The moral of the story: Don't park your Imperial Knight in a field of Gretchin carrying power tools.
 Marmatag wrote:
All the while, my opponent is furious, throwing his codex on the floor, trying to slash his wrists with safety scissors.
 
   
Made in gb
Longtime Dakkanaut





UK

It's really sloppy writing and demonstrates a lack of attention to English.

But yes, it can be argued that way since ie, or id est, technically means that is.

So as reading:

Tau Early warning override: If an enemy unit is set up within 12" of a model equipped with an early warning override as the result of an ability that allows them to arrive mid-battle (that is teleporting to the battlefield), the model may immediately shoot at that unit as if it were your Shooting phase.


Wouldn't recommend doing so though. That's borderline, if not flat out TFG behaviour. The rest of the clause clearly implies that using any sort of ability to arrive mid-battle triggers the respective ability (or increase AP in the case of Storm of Fire).

YMDC = nightmare 
   
Made in de
Longtime Dakkanaut




It seems obvious from the text that this is just a mistake, and they meant "e.g." instead. This strikes me as about as significant for how we should interpret the rules as (hypothetically) Guilliman's buffs affecting "ULTARMARINES" units instead of "ULTRAMARINES".
   
Made in us
Longtime Dakkanaut




Common use has ie and eg meaning the same.
   
Made in us
Decrepit Dakkanaut






Springfield, VA

The way I was always taught is that i.e. is a stand in for "that is to say."

So you could then parse those sentences as "blah blah blah blah (that is to say, WS 3+ becomes WS 2+)."

In context that makes sense.
   
Made in de
Longtime Dakkanaut






i.e. = it est = it is
e.g. = exempli gratia = for example

They meant e.g. and failed to understand the difference.

   
Made in gb
Grim Dark Angels Interrogator-Chaplain





Cardiff

This is the kind of thing worth emailing GW about for future reprints, but not the stuff of a YMDC thread. There is no way to claw advantage from this.

Being a total pedant, the AP and WS examples read just fine with i.e., though e.g. would be preferable. But there's no advantage to be gained by trying to start an argument over this mid-battle, unless you don't like having opponents to play.

 Stormonu wrote:
For me, the joy is in putting some good-looking models on the board and playing out a fantasy battle - not arguing over the poorly-made rules of some 3rd party who neither has any power over my play nor will be visiting me (and my opponent) to ensure we are "playing by the rules"
 
   
Made in gb
Longtime Dakkanaut



Glasgow

I.E. means E.G. just as codexs means codices just as.....

Half of GW rules writtin problems occur because of sloppy use of English.
   
Made in ca
Insect-Infested Nurgle Chaos Lord






I would like to remind people of the Tenets of YMDC, specifically #3, #5 and #6.

The last one specifically deals with GW's weird english.

Gwar! wrote:Huh, I had no idea Graham McNeillm Dav Torpe and Pete Haines posted on Dakka. Hi Graham McNeillm Dav Torpe and Pete Haines!!!!!!!!!!!!! Can I have an Autograph!


Kanluwen wrote:
Hell, I'm not that bothered by the Stormraven. Why? Because, as it stands right now, it's "limited use".When it's shoehorned in to the Codex: Space Marines, then yeah. I'll be irked.


When I'm editing alot, you know I have a gakload of homework to (not) do. 
   
 
Forum Index » 40K You Make Da Call
Go to: