|
11 months ago ::
Jul 10, 2012 - 5:07PM
#151
|
|
|
The statements 'treated as a double weapon' and 'both ends are a light blade' are exclussive statements
No they're not.
nice opinion, unfortunately I have provided evidence as to why. You can't just say 'no." But you were the one that was arguing the 'proper way' to make arguments earlier... lol
To clarify you can replace are exclussive with can be exclussive. The evidence supports that in this case it is however, so i word it as such. If English is not your first language I can see how it would be confusing.
It never says to remove flail and two handed weapon
Speciific vs General rules never says it does. Another point you fail to comprehend
|
|
|
|
11 months ago ::
Jul 10, 2012 - 5:09PM
#152
|
Date Joined:
Jun 17, 2010
|
Read my edits. And as far as English as a first language goes, "exclusive" only has one 's.' Can we dispense with the petty insults, now? You've continued to escalate them towards me throughout the thread, whereas I've been saying that your arguments are flawed, not you. My patience for them is waning.
D&D Next = D&D: Quantum Edition
|
|
|
|
11 months ago ::
Jul 10, 2012 - 5:10PM
#153
|
Date Joined:
Jun 17, 2010
|
It never says to remove flail and two handed weapon
Speciific vs General rules never says it does. Another point you fail to comprehend
...wait, so you agree with me? You agree that SvG never says to remove flail and 2HW?
Ok then.
D&D Next = D&D: Quantum Edition
|
|
|
|
11 months ago ::
Jul 10, 2012 - 5:12PM
#154
|
|
|
It doesn't need to. Really, you need to comprehend posts and stop being obtuse on purpose
|
|
|
|
11 months ago ::
Jul 10, 2012 - 5:23PM
#155
|
Date Joined:
Apr 24, 2012
|
Please remember to keep your comments positive, productive, and on topic. Remember we are trying to create a mutually beneficial and productive community for everyone to take part in. At the end of the day we are all in this thing together, and if we don't work together we will never get anywhere! If you have any questions or would like to read the CoC you can find it here: company.wizards.com/conduct Remember, Keep it clean, Keep it nice, and of course Keep it fun! Thank you for your understanding!
|
|
|
|
11 months ago ::
Jul 10, 2012 - 5:56PM
#156
|
Date Joined:
Feb 23, 2012
|
It doesn't need to.
Actually, it would need to in order for you to be correct. The weapon, the spiked chain, generally is a flail. Specifically, with spiked chain training, you can use it as a double weapon with each end as a light blade doing 2d4, however, this specific statement is not enough to make it stop being a flail because the feat never specifically states the spiked chain is no longer a flail therefore it is still a flail.
|
|
|
|
11 months ago ::
Jul 10, 2012 - 6:10PM
#157
|
Date Joined:
Aug 16, 2005
|
The problem is with the wording that says "you can treat" as it is vague in its meaning. It may imply there is a choice to use as a double-weapon or not. This will affect an RAI understanding of how to use this feat.
However, when things are vague in the text my preferred RAI perspective is to take the view that all possibilities are available. The narrow view leads to subjective arguments based on inherent assumptions and system bias.
By RAW though the exception arguement is valid as does not explicitly say that it loses its property as a flail.
|
|
|
|
11 months ago ::
Jul 10, 2012 - 7:07PM
#158
|
|
|
I see. So where I was assuming you were making an incorrect point, instead you are making an inane one.
Committing the Munchkin Fallacy means with respect to determining RAW, your statement is invalid. It says nothing about a statement with respect to determining RAI.
You are saying that violating the RAW of SvG is also violating the RAI of SvG. Which is one of the most meaningless statements I've heard on the CO, since all it's saying is "SvG means what the authors intended it to mean." So by RAI, you are saying that a Munchkin Fallacy is invalid by RAI to determine RAW.
The problem is, Alcestis, that you take this inane little point and then say "RAI is against you!" when no one uses the term "RAI" that way.
From anyone else, "The RAI is against you" or "your argument is invalid by RAI" means that "the author's Intent contradicts your statement." Or more to the point, "your argument is invalid to determine RAI."
If an argument is invalid by the design of the system, it's okay to say that. It's not okay to start stacking on stuff like "it's against RAI too!!" meaninglessly, especially when that just confuses observers who are still confused about what RAI means in the first place.
Please don't tie the Munchkin Fallacy into your misrepresentations, I worked hard to get it to a place where it could be used effectively. I'd rather people not start adding ineffective uses like yours to the pot.
You're welcome to have whatever opinion you like of my point... but calling it inane doesn't make it untrue. I'll repeat: you clearly don't understand what I am saying, I'd encourage you to reread my posts. You can't argue that the system isn't intended to work a certain way, because for one it was built that way and for another the designers were very clear, both in the books and in interviews when 4e came out, that it was designed a certain way.
Again, it isn't "The RAI is against you." It is "any time you commit the Munchkin Fallacy, your argument is automatically wrong by RAI." Not the conclusion, the argument. You could slot in "developer intent" if it makes you feel better. I can hardly be responsible for people being confused because they don't understand what RAI means, either, but I think it is extremely disingenuous to say no one uses RAI to say that the game was built a certain way. Primarily because I see it used that way a dozen times a day. Any time someone looks at a non-functional power and says it was intended to work, you're making a RAI argument about the system.
It is great that you put some effort into posting a thread as a community resource. One of the things that happens when you provide a community resource is people take it further and use it. The strange thing here is that you and I agree on a great deal of the points you're making, they just aren't contradicting my points because you're contradicting an argument I'm not making. You wrote the Munchkin Fallacy assuming the premises could only be used for small situations. My point is when you apply it to the whole system and reason it out, you wind up with some interesting conclusions about the kinds of arguments that can and can't be valid for determining RAI and RAW both. Which is a useful thing to do.
|
|
|
|
11 months ago ::
Jul 10, 2012 - 7:49PM
#159
|
Date Joined:
Feb 11, 2007
|
It doesn't need to.
Actually, it would need to in order for you to be correct. The weapon, the spiked chain, generally is a flail. Specifically, with spiked chain training, you can use it as a double weapon with each end as a light blade doing 2d4, however, this specific statement is not enough to make it stop being a flail because the feat never specifically states the spiked chain is no longer a flail therefore it is still a flail.
OK, this gets to the root of my question. I'm a complete noob to CharOp, and certainly no rules lawyer. But hopefully someone in the 'SCT makes it no longer a flail' (a simplification, I know, just drawing a line somewhere) camp can answer this question:
It seems that your point is that, when using the weapon as a double weapon, it's treated as two light blades, and no longer a flail. What happens if you have a flail-only enchantment on the weapon? Does it no longer get, say, the +6 enhancement bonus since it's now an invalid weapon type for its enchantment? Wouldn't it have to still be a flail to get that bonus?
The Hairhelmet
|
|
|
|
11 months ago ::
Jul 10, 2012 - 8:03PM
#160
|
Date Joined:
Jan 21, 2011
|
It seems that your point is that, when using the weapon as a double weapon, it's treated as two light blades, and no longer a flail. What happens if you have a flail-only enchantment on the weapon? Does it no longer get, say, the +6 enhancement bonus since it's now an invalid weapon type for its enchantment? Wouldn't it have to still be a flail to get that bonus?
Short answer: being "flail-only" is just a restriction on what you can initially enchant with it. There's no other meaning attached, so changing the type afterward would not affect anything.
Example: an urgrosh has an axe end and a spear end. It can be enchanted as an axe. Even when you attack with the spear end, it still benefits from the enchantment - it doesn't fail just because the enchantment is "axe-only."
I am okay with you saying my argument is stupid, or commits the munchkin fallacy, or any other bad thing you want. Particularly if you give a reason/explanation for it.
However, I will ignore any post that calls me stupid, or a munchkin, or what have you. Not because it bothers me; I've just found that people only start name-calling when that's the best argument they have left.
|
|
|