Guild Wars 2

for the sPvP version, let’s make it a bit special.

proposal #1
Sigil of Nullification
60% Chance on Critical: Remove a Boon. Remove Might Boon if possible.
(Cooldown: 10 Seconds)

proposal #2
Sigil of Nullification
60% Chance on Critical: Remove a Boon. Remove Might Boon if possible.
60% Chance on Hit: Reduce remaining Cooldown by 1 second if target has Might Boon.
(Cooldown: 10 Seconds)

discuss:
feasibility
numbers
whether or not this is code-able by justin, evan and gang.

edit:
proposal #3 by DaveGan seems good.

DaveGan.8065:

Nullification should not be intended to focus certain classes that hard, but it definitely does need to prioritize (or randomize) the boon it does remove.

I had a list of buffs (and stacks/duration) in a previous thread which I would consider “priority”, and any boon removal sigil should be looking at more than just might.

• Might over 6 stacks
• Stability over 3 seconds
• Protection over 5 seconds
• Fury over 5 seconds
• Vigor over 5 seconds
• Regen over 5 seconds
• Swiftness over 10 seconds
• Retaliation over 10 seconds

Ideally removal should be prioritized in roughly the order above.

The alternative (and probably significantly easier to code) would be to RNG the removal.

DOES TARGET HAVE A BUFF?

• YES: Does target have 1 or more “high priority” buffs?
  ——- YES: Randomly remove a high priority buff and trigger the internal cooldown.
  ——- NO: Randomly remove any buff and trigger the internal cooldown
• NO: Do nothing

edit 2:
proposal #4
Sigil of Nullification
60% Chance on Critical: Remove a Boon.
(Cooldown: 5 Seconds)

Archon.6480 said the cooldown of 10 seconds is too high, should be 5 seconds instead. and the base functionality should be left as it is.

just prioritize might and itll be good

Booms.2594:

just prioritize might and itll be good

ah u mean the 1st proposal.

how should the in game text description be worded?

and it should be code-able by justin, evan and team right?

Deimos Tel Arin.7391:

Booms.2594:

just prioritize might and itll be good

ah u mean the 1st proposal.

how should the in game text description be worded?

and it should be code-able by justin, evan and team right?

dont need to change anything, things like corrupt boon and path of corruption already have a priority for boon strip

Nullification should not be intended to focus certain classes that hard, but it definitely does need to prioritize (or randomize) the boon it does remove.

I had a list of buffs (and stacks/duration) in a previous thread which I would consider “priority”, and any boon removal sigil should be looking at more than just might.

• Might over 6 stacks
• Stability over 3 seconds
• Protection over 5 seconds
• Fury over 5 seconds
• Vigor over 5 seconds
• Regen over 5 seconds
• Swiftness over 10 seconds
• Retaliation over 10 seconds

Ideally removal should be prioritized in roughly the order above.

The alternative (and probably significantly easier to code) would be to RNG the removal.

DOES TARGET HAVE A BUFF?

• YES: Does target have 1 or more “high priority” buffs?
  ——- YES: Randomly remove a high priority buff and trigger the internal cooldown.
  ——- NO: Randomly remove any buff and trigger the internal cooldown
• NO: Do nothing

Booms

dont need to change anything, things like corrupt boon and path of corruption already have a priority for boon strip

They seem to only prioritize the last-applied boons. To prioritize might and/or other boons, more coding is definitely necessary.

DaveGan.8065:

Nullification should not be intended to focus certain classes that hard, but it definitely does need to prioritize (or randomize) the boon it does remove.

I had a list of buffs (and stacks/duration) in a previous thread which I would consider “priority”, and any boon removal sigil should be looking at more than just might.

• Might over 6 stacks
• Stability over 3 seconds
• Protection over 5 seconds
• Fury over 5 seconds
• Vigor over 5 seconds
• Regen over 5 seconds
• Swiftness over 10 seconds
• Retaliation over 10 seconds

Ideally removal should be prioritized in roughly the order above.

The alternative (and probably significantly easier to code) would be to RNG the removal.

DOES TARGET HAVE A BUFF?

• YES: Does target have 1 or more “high priority” buffs?
  ——- YES: Randomly remove a high priority buff and trigger the internal cooldown.
  ——- NO: Randomly remove any buff and trigger the internal cooldown
• NO: Do nothing

Booms

dont need to change anything, things like corrupt boon and path of corruption already have a priority for boon strip

They seem to only prioritize the last-applied boons. To prioritize might and/or other boons, more coding is definitely necessary.

nah there’s a definite prioritization as stab/prot are always stripped last no matter what

aye thanks Booms and DaveGan for the feedback!

i added DaveGan’s idea to the first post.

Booms.2594:

nah there’s a definite prioritization as stab/prot are always stripped last no matter what

If this is really true, doesn’t that mean the current coding kind of sucks and should be avoided with a 30 ft pole? lol

DaveGan.8065:

Booms.2594:

nah there’s a definite prioritization as stab/prot are always stripped last no matter what

If this is really true, doesn’t that mean the current coding kind of sucks and should be avoided with a 30 ft pole? lol

well its not too bad if it helps out with getting rid of might haha
also remember bountiful theft steals stab/aegis before everything else so that also has prioritizations

I rather prioritize stability.

I think it should be left as is and the internal cooldown should be changed to 5s. It’s worthless in the current state because boons are so easily reapplied by the kind of builds we would use this against.

How about a new sigil that corrupts 1 boon, with priority given to might, on weapon swap or crit (id prefer swap since itd be less rng, but then again on crit would require people to not be full bunkers to get use out of it)

We already have transfer condition sigils so this cant be too big of a stretch

@ runeblade.7514
you don’t mind people stacking 25 might and do lots of damage?

@ Archon.6480
hmm a 5 seconds cooldown does seems better. but don’t you think prioritizing certain boons could be better?

@ Sizer.5632
that would be a new topic then. a sigil that corrupts boons hmm.

Deimos Tel Arin.7391:

@ Archon.6480
hmm a 5 seconds cooldown does seems better. but don’t you think prioritizing certain boons could be better?

Prioritizing boons would be better for me against—ahem, celestials—but would make it so they can’t “cover” the boons they want to keep with less important ones. I like the skill required to cover conditions, and think good players should have the option to do this for boons. What do you think?

If they made sigil of nullification a 5 second cooldown and added sizer’s weapon swap boon corruption sigil…I think we would be in good shape to counter builds that rely too heavily on might/boon stacking.

@ Archon.6480
hmmm i suppose you are right. i can agree with that.
if certain boons are prioritized, then it would remove the option to “protect” the boons from being stripped / stolen by covering them with new boons.

but … won’t a 5 seconds cooldown it too strong? or it is fine as long as it requires a critical hit to proc?

hmmm regarding Sizer’s proposal about a sigil that corrupts boon, wouldn’t it better if it requires critical hit to proc? to discourage bunkers. but my knights amulet warrior with deep strike can benefit from them anyway.