ArenaNet talk:Skill bugs

Power Block

 * Actually watch the video, I see not "fail to cast" when the meteor shower kills the player casting PBlock.Crimmastermind 03:40, 5 February 2009 (UTC)
 * That's because he had 0 domination, so it only disabled for 3 seconds, which was shorter than the remaining cast time of meteor shower. It only fails if the spell is still disabled when you finish casting, so if, like in this case, the disable wears off before the spell completes, it won't fail. Which is pretty much exactly what the last sentence of my first post said.  &not; Wizårdbõÿ777  ( talk ) 04:01, 5 February 2009 (UTC)
 * I'll admit I didn't see that part, but the fact is, the skill still doesn't work according to its description (interrupts regardless of any skills that would prevent interruption). They need to change the description or the function. & r u sure this is the right place to move this, shouldn't it go in the arena-net skill bugs talk?Crimmastermind 06:00, 8 February 2009 (UTC)
 * Backsword moved it here. ArenaNet talk:Skill bugs would probably be a better place for it, though.  &not; Wizårdbõÿ777  ( talk ) 04:54, 9 February 2009 (UTC)
 * I wasn't able to reproduce this bug with the information given here. Could someone please post a link to the original entry, or clarify the issue?  Thanks! Leah Rivera 17:48, 27 July 2009 (UTC)
 * If you've got a target casting Meteor Shower with Mantra of Resolve up and you hit 'em with Power Block with 0 Domination Magic, Power Block fails to interrupt Meteor Shower as it should, according to Power Block's description. See the section below for more information. ···  Danny  Pew   Pew  18:59, 27 July 2009 (UTC)

Interruption and Interruption Prevention
Well, I'll work from the bottom first:
 * Savage Shot:Only the concise description says that the +dmg only occurs on interrupt. The normal description clearly states If that action was a Spell, you strike for +13...25...28 damage. , note the 'if that action'. As of now, Savage shot works according to the (normal) description. It should be skills which work by their concise description that are changed (concise=shorter=not as much detail=not as likely to be correct =/= long description is wrong and just wastes space).
 * Power Block:The normal description is wrong because the spell isn't interrupted regardless of any effects that prevent interrupts. The concise description is wrong because it still disables even if it doesn't interrupt.
 * Psychic Distraction:Concise description wrong, it doesn't require an interrupt for disable to take effect. Normal description wrong. Oh, and the Description Claims and Actual Behavior text is exactly the same except in a different order (which means nothing). Same for Signet of Distraction. --The preceding unsigned comment was added by User:Crimmastermind (talk).


 * Huh. I don't see a reason for either description to be outright wrong. It's certainly not an space issue when you take extra space to claim somethign that is not correct. Backsword 17:33, 20 February 2009 (UTC)

Item spells
I'm not sure if this is the right place. There is quite a buggy behaviour of when having some ashes in the skill bar. Even at full energy (eg. 30 when holding some ashes) I'm sometimes unable to cast anything, the system giving me "not enough energy". Since this happens in Alliance batttles, a (hidden) death penalty should not apply, but there may have been a previous death of mine. I'm experiencing it even without any foes around. (Holding ashes, being at full Energy seconds after reentering battle via rezz shrine, wanting to summon a bloodsong spirit). ATM, it makes Rt with ashes quite unplayable, at least in AB. I heard about this bug happening in PvE, too, but I'm not sure about this, as I never tried. 85.178.224.33 01:08, 19 February 2009 (UTC)
 * This bug is most frequently documented in FA. When you die with exhaustion while carrying an item, that is your new max energy for the rest of the session (on the Server, but not on your computer). This means that though it shows on your screen that you have enough energy, whenever you try to activate a skill, the server says otherwise.Crimmastermind 05:57, 19 February 2009 (UTC)

Flame traps in EoTN
Someone would have to test this, as I no longer have any summoning stones to test if it is still occuring, but... I clearly recall doing Catacombs of Kathandrax on my monk, and using a Snowman Summoning Stone, after which, all flame traps in the area inflicted daze upon hit. Which, as you may assume, was quite painful and frustrating. Works with the grench and disease too. My assumption? the hidden rock/yellow snow somehow applies to the flame traps as well, but since the preparation is still active, it's constantly re-applied after every hit.76.175.144.6
 * For some reason, the engine considers these skills to have been activated by some nearby creature. This is why you can see the damae numbers when they hit other players. ANd as some of them are spells, they will trier glyphs. Backsword 04:25, 14 June 2009 (UTC)

Signet of Distraction
I've been testing it, the skill is bugged (as far as i can see) First, it doesn't count itself which means if you have this and another signet at 15 Domination Magic the spell would be disabled for only 5 additional seconds (not sure if it's a bug but the description doesn't mention it) Second, this skill doesn't seem to add an additional disable time to spells which have a 30 seconds recharge time or longer. I was testing this skill on the following spells, one time with 1 additional signet and another time with 2 additional signets (15 Domination Magic):  1 additional signet: Lava Font - 4 -> after interruption - 9 Obsidian Flame - 5 -> after interruption - 10 Lightning Ord - 5 -> after interruption - 10 2 additional signets: Lava Font - 4 -> after interruption - 14 Obsidian Flame - 5 -> after interruption - 15 Lightning Ord - 5 -> after interruption - 15 Fire Storm - 30 -> after interruption - 30 --Soulforged  12:39, 9 July 2009 (UTC)

Many of these reported over a year ago are still bugged
So....what exactly does reporting the bug do? Karate   Jesus  21:49, 29 July 2009  (UTC)
 * It gives QA/bug testers some extra things to fix in the game. Sometimes they are too hard to fix/not a priority, so they stay bugged. --JonTheMon 21:56, 29 July 2009 (UTC)
 * It enables QA to make sure it's bugged, then it's attached to a list of bugs and they are fixed based on the priority of things. Fixing bugs is not always the #1 priority, especially if they are relatively minor which most of the ones on this page are. :P Only time bug fixes are #1 priority must fix now is when they provide an unfair environment/allow you to cheat the system (the item duping bug, etc...), otherwise it comes down to whenever the programmer(s) can invest the time to fix the bug without affecting anything else they are working on. :p DarkNecrid 04:18, 30 July 2009 (UTC)


 * Eh, hardly gamekillingi stuff. Some are even quite questionable as bugs. And it's not like this article is their only souce of bugis. In a game of gws size, there will plenty of very minor stuff. Backsword 20:56, 31 July 2009 (UTC)