Algesan's Blog
  • Home
  • Blog Page
  • Black Templar Lists
  • 6th Edition Tips, Tricks & Issues

Using Occam's Razor

12/9/2011

2 Comments

 
The question got asked me about how does one apply Occam's Razor when dealing with things like rules disputes.  So what is Occam's Razor?  It is a way of choosing between competing theories and is often summarized as "simpler explanations are, other things being equal, generally better than more complex ones."  Another way is that the explanation that fits all the known hard data, as opposed to interpretations of the data, with the fewest assumptions (interpretations) probably is the most correct one.  It does not mean the explanation that can be stated the most simply is necessarily the correct one (a common error in application of the Razor), because there may be hidden assumptions that require lots of explaining to support or refute them.  Also, pulling in the data sources might be more complicated than just looking in one place and going AHA!

After all, just using our eyes the fact that the sun circles the earth is perfectly valid.  It takes observations, with some kind of vision enhancement (telescopes) of a number of different celestial bodies in the solar system to gather the data that refutes a geocentric view.  Especially when that view is a mature and accurate theory.  For trivia's sake, if you go to a planetarium and enjoy the show about the solar system, the entire setup uses a geocentric model for the same reason that geocentric theory was developed.  It is the best way of dealing with bare eye observations of the solar system from the earth, especially with modern computers.  Heliocentric theory simplifies the math, so it fits Occam's Razor.

The worst thing is that laying out a case like this, even on a simple matter, to overcome existing beliefs, becomes a wall of text even handled relatively briefly.  In RL, this took me minutes to figure out once I started studying the relevant rules sections.  So, long post ahead.

_I'm going to try to do this using an older discussion of the assault rules that were discussed in both the Black Templars and Official Rules sections of the Bolter & Chainsword forum.  This is not to reopen that dispute or get into another debate about it, but to lay out how Occam's Razor can be used in a rules dispute.   I'm currently using and will continue to use the common interpretation of the rules in my games because it is so ingrained into the 40k player base that only GW openly dealing with the issue in a FAQ will solve it. 

The first thing we will look at is the rules on Declaring Assaults on page 33.  Looking at the summary, the second bullet of 1 is "Declare which enemy unit it is going to assault".  The right column of page 33 has the rules for declaring assaults.  The first thing is that all assaults is to measure the assault range.  The next is the subsection on "Disallowed Assaults".  There we find five bullet points and a conditional clause ("must assault unit you shot at" - will only use "must assault" for this from now on).  Interpreting this, the first question is do we assume that GW used standard English and style rules writing this section.  If yes, then we have five "hard" conditions that always apply and a "soft" condition that only applies in some cases.

Note: When you make assumptions to prove a theory, you also have to understand the implications of that assumption.  Therefore, assuming that GW messed up the writing here and "really meant to have six 'hard' conditions" implies that anything written in the rulebook can be tossed out (RAW) in favor of interpretation (RAI) on the basis of "it should read this way, GW just wrote it wrong".  That is a can of worms that tosses all of the rules away at whim.

So, the best reading is that there are five 'hard' (bullet) conditions and one 'soft' condition about only being able to assault the unit you shot at.  The next assumption (these could also be called "interpretation") comes when deciding if a destroyed unit still counts as a unit for the purposes of "must assault".  Of course, if the target unit is still functional on the board (IOW, doesn't count as a KP), then the "must assault" condition is triggered.  So, we are left with two choices:  A unit that is destroyed (which includes wrecked vehicles even though the model may still be on the board as terrain) either is still a unit in the next phase OR it isn't a unit, it is just a KP because it is destroyed.  Although I think that making the assumption that units still "exist" in later phases is a bit iffy (it is a bit hard to declare an assault on something that isn't there, but that is what assuming the dead unit "exists" requires).  Another issue is that even though "must assault" logically must be a soft condition, if you consider the unit "exists" even when it doesn't, this assumption shoves "must assault" back into the hard category because if you shoot, it doesn't matter what happens to the unit you shot at, you "must assault" it.  Well, duh, this turns it back into the same problem as considering it a hard condition from the beginning with the same implications for the entire rulebook.

The next strand in the theory is the use of the note (Note) in the second column of page 67 at the end of the Effects Of Damage Results On Passengers section.  It reads as follows:  Note:  remember that all models in a single unit fire simultaneously, so a sqquad cannot take out a transport with its lascannon and then mow down the occupants with their bolters.  However, if a transport is destroyed (either result) by a ranged attack, the unit that shot it may assault the now disembarked passengers, if it is allowed to assault according to the assault rules.

The common interpretation considers this to be an exception to a hard "must assault" assumption, either from directly or indirectly interpreting the RAW conditional statement as a bullet point or hard condition.  This can cause some problems reading the Note as written.  Again, there are two cases to consider:
  1. This is an exception because the "must assault" is defined as a hard condition.
  2. This is simply a clarifying note because "must assault" is a soft condition.
Let's deal with the first one.  The first sentence references page 18, the first sentence in the main text that says that all units fire simultaneously.  If the Note is an exception, then this is a throwaway sentence and totally irrelevant, but the connection between the two sentences is "However,...".  Why this distinction?  Hmmm.
Next, we see that a unit that shoots and destroys a transport may assault the passengers, "if it is allowed to according to the assault rules."  Of course, this immediately counts as an exception to the hard "must assault" condition, but are there any other exceptions?  Well, obviously the shooter must be in assault range (and have a WS), so this applies to the Disallowed Assaults section and its hard conditions.  Why not just the "must assault" condition?  Because the Note does not give any other trigger as an exception except the transport be destroyed in the shooting phase and the shooter shot at it.  Two choices again, either all of the hard conditions still apply or none of the apply if the exception's trigger is met.  Logically the first three bullets (locked in CC, ran, GtG) cannot apply because the unit could not have shot.  If the other three all apply, then the shooter cannot assault. 
However, if this is an exception, then a unit that fired RF or Heavy weapons and a unit that is falling back also must get the exception if they qualify by having shot at the transport and are within assault range of the passengers.  So, to make this fit in the common interpretation, two more assumption have been made; the final phrase of the Note doesn't apply to the hard conditions and that it only applies to the "must assault:" hard condition.

For point 2 above, the Note is read as a clarification.  This fits with the "remember" reference for shooting and then ties into the "However,..." for a relevant clarification since we are discussing transport vehicles.  If "must assault" is soft and the dead no longer exist for game purposes, it is fairly easy to point out for non-vehicles because they are pulled off the board as the models die.  For vehicles, the rules state that they remain on the board as terrain when wrecked (page 62).  I've seen more than enough players who would point at the wreck and say that the model is still there so the unit is "still there", but you cannot assault it because it is wrecked!  More seriously, it clarifies that even though the passenger unit was off the board at the beginning of the turn (and therefore not a target for shooting or assault normally), by coming on the board during the shooting phase, it definitely may be assaulted, subject, of course, to the assault rules, including being in assault range and using the applicable hard conditions.  No need for extra assumptions, it reads exactly as it is written.

So, both positions must assume GW wrote what they meant or didn't write what they meant.  Then they must assume that a destroyed unit exists in later phases or that a destroyed unit ceases to exist for game purposes except as a kill point.  Finally, the supposed exception of the Note (which is cited by the defenders of "must assault" as a hard condition) requires two assumptions (does not apply to all hard conditions and only applies to a hard "must allow.

So, four assumptions to two assumptions (I'd say five or six to two, but not now), which gives the "must assault" as a soft condition that doesn't apply to destroyed units the benefit of Occam's Razor for simplicity.  Notice that this does NOT deal with seriously judging the validity of some of those assumptions, but I noted some issues in passing above.  Heh, in some cases the trump card in defense of a hard "must assault" was quoting the 4th Edition rules on assaults verbatim.  For 5th Edition
rules!


2 Comments
Devjon link
12/9/2011 08:13:51 am

I would like to point out another assumption that you're making, because you left it out and it applies to the topic (of Occam's Razor).

It is the assumption that GW would have, as part of their rules, something which you could not come to without thoroughly examining certain parts of the rules. Except for making a case with the Note, there is nothing in the 'must assault' clause to imply that if you killed the unit you shot at then you may assault something else. And it isn't like they couldn't have included the phrase 'unless you kill the unit you shot at' or 'unless that unit is dead' or something. It makes no sense for it to be that way and so you must assume it.

Also, if the Note as an exception makes no sense because it has nothing in it to retain the other conditions on assaulting, then you need to see how that reasoning affects other parts of the rules, just as you said. This was something you never addressed properly, and that really didn't help your case. If the Note requires a proviso to be an exception to that one rule, than so do other exceptions, such as Relentless. Relentless allows you to assault after firing a Rapid Fire or Heavy weapon, but have no provisos for the other rules. If those Provisos are necessary, then a unit of CML Terminators can, while falling back, shoot and stun a Rhino and then assault a near-by Dreadnought. So does only the Note require a proviso (which would mean you are ignoring similar circumstances with other rules), or are you assuming that far more rules have always been played wrong.

And there could be a third assumption that I could point out, depending on if you claim that this is simply how the strict RAW is, or that GW intended the rules to be like this (basically, that it hasn't been caught yet).

I know that you said you didn't want to start this up again, but I think that it is worth pointing out to others how difficult it can be to realize how many assumptions are made without realizing it, which was part of what caused so much controversy on B&C (unwittingly making an assumption when no-one else did, or explaining something in such a way that it appears you have made an assumption).

Reply
Algesan link
12/15/2011 09:33:52 am

No problem, you are addressing this correctly. First go after the assumptions.

For the first one: No, I don't need to examine multiple parts of the rules to reach my conclusion. I simply had never read that section, or not carefully, since I'd been taught by word of mouth that certain assaults were disallowed unless you had a rule to let you. When I did turn back and read it, then the fact that the format is of five hard conditions and one soft condition, that there must be times when the soft condition does not apply. Notice that I don't need an exception to make it not apply at all times since exceptions apply to the hard conditions.

So, at what point does the "must assault" soft condition not apply? If the unit survived the shooting phase, then it will apply. Therefore the other option (target unit dies) must be when the condition does not apply. Nothing else needed there. The only reason I dealt with the note on page 67 was because that was being cited as an exception in defense of the interpretation that you cannot assault any unit other than the one you shot at no matter what. "See, look, there is an exception, therefore this interpretation must be right and GW screwed up writing the rules." The entire case for the common interpretation rests on the premises that GW screwed up writing the rules and/or Assault works just like it did in 4th Edition.

USRs don't help the defense of the note as an exception.
FLEET-"... A unit with this rule may assault in the same turn in which it has run."
RELENTLESS-"..., and are also allowed to assault in the same turn they fire them (RF & Heavy)."

Lots of exceptions in the rulebook, look under the unit types. In each case the exception is clearly spelled out, not an ambiguous "..if it is allowed to assault according to the assault rules." That ambiguity guts the idea of justifying "must assault" as a hard condition with the note as an exception. Either *all* of the conditions apply (including "must assault") or none of the disallowed conditions apply.

It could have caused the troubles on B&C, but the mod there who closed both threads stated something along the lines of "the rules are clearly written", which means the mod doesn't understand the point.

Remember, I don't need anything past the RAW on page 33. Five hard conditions (that require exceptions to break them) and one soft condition (that does not require an exception). If you shoot at unit, the unit either survives or it does not. If it survives then the condition applies. If it does not, then the condition does not. Otherwise the case is that GW screwed up on the rules. Yes, I know they have done so some before, but I've seen far more quibbles over rules that when GW did actually "clarify" them, it turns out that it was a reader error, not a writer error.

Why don't I make a big huhu out of people "playing wrong"? Because in almost all cases it is a silly thing that applies both ways, but doesn't matter as long as everyone is consistent about it. In one case it is not, but I simply exploit it for all I'm worth and do my best to make sure it is not exploited on me.

Reply



Leave a Reply.

    Author

    Comments about 40K and maybe about anything else that I decide to mention.

    Archives

    March 2014
    February 2014
    November 2013
    September 2013
    August 2013
    July 2013
    June 2013
    May 2013
    April 2013
    March 2013
    February 2013
    January 2013
    December 2012
    November 2012
    October 2012
    September 2012
    August 2012
    July 2012
    June 2012
    May 2012
    March 2012
    February 2012
    January 2012
    December 2011
    November 2011
    October 2011
    September 2011
    August 2011
    July 2011
    May 2011
    April 2011
    March 2011
    February 2011
    January 2011
    December 2010

    Categories

    All
    All
    Battle
    Black Templar
    Dark Angel
    Dust Tactics
    Dzc
    Fluff
    Laeroth
    List
    Misc
    Necron
    Necrons
    Nova
    Painting
    Progress
    Proxy Models
    Rant
    Sisters Of Battle
    Theory

    RSS Feed


Powered by Create your own unique website with customizable templates.