Nurglitch wrote:Brother Ramses wrote:Kaaihn wrote:The problem in most rules debates isn't actually permissive versus prohibitive from what I have seen. Most players get that.
The problem is typically from fundamentally different views on some of the other core functions of the how the game works. That, combined with some poor reading comprehension, leads to some wildly different views on how the game works.
I disagree. So many times I have seen a debate boil down to:
"Show me in the rules/codex where it says I can't do xxxx!"
There's all sorts of ways to be stupid with the rules. The old double-negative you've cited has a companion "Show me in the rules where it says I have to do x!" Which is usually followed, after you cite the passage in the rules where it requires you to do x, "It doesn't say that!"
Take the whole Deff Rolla question, of whether a Deff Rolla does
D6 S10 hits when its Battlewagon rams another vehicle. It seems to turn on what people take the term "special type" to mean.
In my opinion (and no doubt lots of people feel the same way about me), that nearly all problems with the rules come down to poor reading-comprehension. I think the Warhammer
40k rules, barring one or two exceptions in the text, are quite clearly and plainly written, and that people who find them vague or confusing need to work on their reading-comprehension skills. I think it is no coincidence that the people who complain about the way that
GW writes rules tend to be terrible writers themselves, if their posts are any evidence of writing/reading skills.
There is a large grain of truth in exactly this. There is more to it though; some people simply view the function of the rules differently than others.
One example would be how you follow rules in a linear fashion, and only the exact condition at the moment is taken into consideration towards the next rule you attempt to use. You conflict check at each step, but you don't hold a conflict over through multiple steps.
If you have a choice of doing Action A or action B, but you are restricted from doing action A because it conflicts with rule 1 while action B doesn't conflict with rule 1, you can do action B. Whatever condition you are in after performing action B is what is used to determine if you can then do action A. If the new condition is no longer in conflict with rule 1, and the condition after completing action B doesn't conflict with action A, you can now do action A.
You wanted to go A then B, but rule 1 prevented A but not B. So you did B, which took you out of conflict with rule 1, and then performed action A.
I guarantee there are many folks that agree with that being a core function of the rules, and just as many that will disagree completely. If people can't agree on core functions like this, they will rarely come to the same conclusion about how something that isn't spelled out in idiot proof language works.
The book needs a "rules on how to use the rules" section at the beginning, that would give everyone the process for resolving a huge amount of questions that the rules don't explicitly cover for various situations.