Talk:Of Slaying

Recent update (introducing Hard Mode) changed all +25% vs Charr of Slaying collector updates to 20% unless previously salvaged, so I removed the note. Crenel 19:23, 23 April 2007 (CDT)
 * Depending on the area you're attempting to Vanquish, these might finally have some use. Arshay Duskbrow 20:21, 23 April 2007 (CDT)
 * Agreed. I'm just glad that I decided to grab a 25% Charrslaying Bow Grip a few days before Hard Mode came out. I'm the proud owner of a Grinning Recurve Bow of Charrslaying (25%). Crenel 23:46, 23 April 2007 (CDT)

does anyone know if this works for spells or just wep dmgTenshi_strife
 * Does it gives you 20% + dmg even if you use spells ? or just dmg as staff it self gives. Gcardinal 19:37, 24 May 2007 (CDT)
 * I was wondering the same thing. im going to test it now.

Major issue with slaying mod
Currently, at least some mods are broken. For example, 20% "charr slaying" mod reduces the damage dealt to non-charr enemies by 3-4 times, at least in the two collector weapons I personally tested. This cerainly wasn't the case in the (1-year-ago) past, so it's most likely a bug.

See comments below for details. Please remove this once you feel this issue is resolved.

Barbed Ascalon Razor of Charrslaying is not working. Compared to identical dmg Rinblade (dmg 10-14), the Razor deals only 11 dmg with Wild Blow, while the Riblande deals 37 dmg with Wild Blow to the same creature (Flash Gargoyle Lv 3). Is it intentional that the weapon of Charrslaying deals almost 4 times less damage on non-Charr enemies? It is probably a bug.

I tried one more weapon of Charrslaying, and it exhibited the same bug. This time it is War Hammer of Charrslaying (also taken from a collector); it deals tiny damage compared to any non-Charrslaying weapon of similar characteristics. It seems that the whole "of slayer" modifier is bugged.

Related discussions (by others) are here:

http://guildwars.incgamers.com/forums/showthread.php?t=438475

http://www.guildwarsguru.com/forum/showthread.php?t=10071514

The author of the second report observed the problem on 3 Nov. 2006. He also stated that this problem did not exist at an earlier (unspecified) date; so some patch prior to 3 Nov 2006 caused this bug.