Guild Wars 2

hey boys and girls I want to discuss the illusionary counter skill. At first I thought it was useless even with the new torment debuff added. But after alot of testing in spvp I created a new build from scratch in which illusionary counter perfectly fits, i love it

But after many hours of testing and having fun with it, i noticed some strange behaviour perhaps some bugs.

- You can’t block skills like magnet, this is strange but it’s working as intended I guess. Even though, it seems that the skill goes on full CD when interrupted by magnet. This seems to be a bug to be honest, as you get like 3s or 4s CD when beeing interrupted.

- Sometimes torment won’t procc on ranged attacks even though I blocked with IC. This seems to be a range issue. Range > 900 -> no torment.

- Sometimes torment won’t procc for no reason. I think it has something to do with AOE skills that require a target. For example you are getting hit by a targeted AOE but you are not the target of that aoe spell. Thief shortbow #1 perfekt example. Torment proccs on direct hit but not on bounce.

Those are my observations regarding strange IC behaviour. While it’s hard to track down whats exactly wrong, I’m pretty sure there’s something wrong :>
Would be cool if other players or devs will have a look on it.

gorma.3725:

- Sometimes torment won’t procc on ranged attacks even though I blocked with IC. This seems to be a range issue. Range > 900 -> no torment.

Well, since the tooltip state a range of 900, I am inclined to think it is intended behaviour

@gorma:
- Magnet is an unblockable skill (source: http://wiki.guildwars2.com/wiki/Magnet)
- Damage + Torment happens ~0.5s after the successful block (not instantly), so I guess there’s a range check before the damage is applied.

From what you say, it looks like when iCounter cannot determine the damage’s source, it won’t be able to damage or apply Torment. This could be an issue in group fight when you intend to block that attack but then out of nowhere another attack hits you first, the block is activated and you lose out on the counter benefits.
I agree that iCounter should be looked at and tweaked a bit to make it more useful for such encounters.

Elidath.5679:

gorma.3725:

- Sometimes torment won’t procc on ranged attacks even though I blocked with IC. This seems to be a range issue. Range > 900 -> no torment.

Well, since the tooltip state a range of 900, I am inclined to think it is intended behaviour

Sure, that’s what the tooltip says. But I have the feeling thakittens not working as intended. Remember when iCounter was only a block that created a clone on the block event? If you got hit from 900+ range the clone didn’t appear but you did the block. The clone you create is a standard scepter clone, this means that the torment is not applied by the clone but by the block itself. So the way it is now, it does make no sense to me. If I block the attack, torment should be applied regardless of range because the block triggers torment not the clone. Get my point? I feel that this the design for this skill and they simply made a mistake implementing it. Dev comment would be highly appreciated.

keenlam.4753:

@gorma:
- Magnet is an unblockable skill (source: http://wiki.guildwars2.com/wiki/Magnet)
- Damage + Torment happens ~0.5s after the successful block (not instantly), so I guess there’s a range check before the damage is applied.

From what you say, it looks like when iCounter cannot determine the damage’s source, it won’t be able to damage or apply Torment. This could be an issue in group fight when you intend to block that attack but then out of nowhere another attack hits you first, the block is activated and you lose out on the counter benefits.
I agree that iCounter should be looked at and tweaked a bit to make it more useful for such encounters.

While this could also be true, I observed what I described in 1vs1 situations too. For example fighting a thief 1vs1 with nobody else around, the thief targeted one of my clones with shortbow #1, I blocked the bounce → no torment applied. I’ll try to reproduce this later.

I managed to record torment not being applied. Seems that using a dodge or beeing interrupted just after the block ends up that tormet is not applied.

http://www.youtube.com/watch?feature=player_detailpage&v=Qz1Z8La8LD0

The torment is applied by the skill, not the block. This has 900 range. This is not a bug.

Unblockable skills, such as magnet, can not be blocked.

The torment is applied with a short delay after the block. If the person dodges when they see the block, the torment will miss. This is not a bug, it is counter play.

Pyroatheist.9031:

The torment is applied by the skill, not the block. This has 900 range. This is not a bug.

Unblockable skills, such as magnet, can not be blocked.

The torment is applied with a short delay after the block. If the person dodges when they see the block, the torment will miss. This is not a bug, it is counter play.

Oh man when torment lands though its GG for the following classes

1. Thieves
2. Eles
3. Rangers
4. Some Warrior Specs.

I have found it hardest to land on mesmers just because their is so much damage coming from alternate sources (clones and phantasms) that it usually winds up landing on a clone. However if it lands on a duelist I will take that too.
Guards don’t really eat up the torment that much. However it can reach 8k damage in total.