Reply to thread

Message: <blockquote data-quote="Tonester" data-source="post: 4344884" data-attributes="member: 71788">I seriously don't understand the confusion. There are a few pages which mention this topic: P.55  P. 226 They then give an example of a paladin using a fire keyword weapon as the implement/accessory of a paladin power that deals radiant damage. In this case, the damage would be evenly radiant and fire.  P.276  Now, to answer the questions: The at-will allows you to turn on/off the weapon's ability to deal Cold damage. While the book doesn't specifically indicate whether this overwrites all damage types, I'm pretty sure it does not. It simply means that the weapon doesn't always deal cold damage (i.e. you attack something that is healed by cold damage, thus making your weapon worthless) If a Paladin power is used that deals radiant damage with this weapon while the cold keyword is turned on, the power will evenly deal cold and radiant damage. Or, if the player prefers, the power can deal radiant only. However, if a critical hit is scored, then the extra Critial damage done for being a frost or flame weapon will always be fire or cold. Additionally, the Daily power that deals an extra amount of damage on a hit will always be cold/fire. If you had feats that gave +1 to radiant and andother that gave +1 to cold as feat bonuses, then you would just pick one since they would not stack. For example, if fighting something that is resistant to radiant damage, you might opt to pick the cold or fire feat bonus instead, but never both.  Based on what is printed in the PHB, I would say yes - you gain combat advantage while using a Frost Weapon and having the Wintertouched feat. However, I think this is due to an oversite on their part. Wintertouched specifically states: It clearly does not state "When dealing cold damage." It states very clearly that whenever any power is used that has a keyword of "Cold." However, the book also states equally clearly, "When you use a magic item as part of a racial power or class power, the keywords of the item's power and the other power all apply." In this case, if you choose to do so, all attacks made with a Frost or Flame weapon can have the Fire or Cold keyword. This also means that any powers that use Weapon as the accessory/implement would benefit from this keyword as well... including Basic Attacks. Now onto the issue of Reliable. This doesn't work. Powers have "accessories." This is a weapon or an implement (Holy Symbol, Rod, Orb, Staff, Want, etc). Class powers inherit the benefits from accessories when the accessories are used to channel or deliver the power. It doesn't say anywhere in the PHB, to my knowlege, that the reverse is true. Furthermore, most of the wording deals with damage keywords and not effect keywords... Reliable is an Effect keyword. A Fighter Class power with the Reliable Keyword would also have the Fire keyword if the attack/power was made with a Flaming Weapon. Why? Because the Accessory Keyword of the Power is Weapon. Therefore, the Power inherits the benefits of that Accessory when using the power, but the reverse is not true. I can't even imagine a scenario (mechanically, not realistically) where this is possible in the game since not a single item that I can see actually "makes an attack" as part of its power. Weapons don't make attacks in 4e. They are accessories/implements to powers that do. Powers inherit the benefits/keywords of their Accessories/Implements. As a quick followup, this is also why many of the character generators you see out there screw up Paladin stuff - because they aren't coded correctly to handle Powers with the Weapon keyword. They tend to hardcode weapon ToHit based upon either Str or Dex depending on whether the weapon is Melee or Ranged. However, they should never hardcode abil modifiers to a weapon since weapons don't benefit from abilities.... ever. Only powers do.  They should be adding the Prof bonus however. Weapon is just an implement for martial powers. I don't understand why this is so hard to comprehend. heh</blockquote>

Verification