Toggles and procs: Energy Aura: Repulse with Force Feedback: Chance for +Recharge
I am pretty sure you have to hit something for it to proc, but I might be mistaken. Someone else will likely come along and confirm/deny.
Basic rules on Procs and 120s.
Clicks - it checks on activation. If an attack, requires a target, as I recall - I do know that when something like Foot Stomp or Dark regeneration is used, it has a chance to activate per critter hit. So no critter would then be no chance.
Autos, Rains and Toggles check once every 10 seconds. Rains and Toggles won't fire unless there is a critter in the area of affect (and rains after the initial hit are their own caster, so the proc in question isn't much good in it), and I can't recall if there are no critters in at the 10 second mark if it holds until they enter, or you gotta wait again.
Orc&Pie No.53230 There is an orc, and somehow, he got a pie. And you are hungry.
www.repeat-offenders.net
Negaduck: I see you found the crumb. I knew you'd never notice the huge flag.
Thanks, what if the proc is in a non-combat toggle like Combat Jumping or Maneuvers? Would those also require enemies to be activated? I assume not.
Edit: Not specifically, the proc I mentioned in Force Feedback, but let's assume some other proc, say in a Defense set based on my examples.
Thanks, what if the proc is in a non-combat toggle like Combat Jumping or Maneuvers? Would those also require enemies to be activated? I assume not.
Edit: Not specifically, the proc I mentioned in Force Feedback, but let's assume some other proc, say in a Defense set based on my examples. |
Orc&Pie No.53230 There is an orc, and somehow, he got a pie. And you are hungry.
www.repeat-offenders.net
Negaduck: I see you found the crumb. I knew you'd never notice the huge flag.
Force Feedback does not suppress itself any more. Since it would be in a toggle, it would only fire once every 10 seconds. Since it's in an enemy-affecting toggle, it would only fire if an enemy was in range. And since enemy toggles on stalkers suppress while you're hidden now, the toggle won't affect enemies while you're Hidden.
In other words, the proc will check once every 10 seconds, but only if there's an enemy in range and you're unhidden. If there's multiple enemies in range, it will proc on all of them at once, giving you a better chance of success, but it still doesn't stack with itself, so you'd only get at most one +recharge buff.
@Roderick
Thanks for the explanations.
Is Repulse supressed when Hide is toggled or only when in a Hidden status?
Example: Toggle Hide and Repulse. SS into a group of 8. Attack with Assassin Strike. After I attack and lose my hidden status, is Repulse now affecting enemies (thus also potentially triggering the proc)?
So, now a question of opinion. Is it useful you think if I only 1-2 slot Repulse to put a proc like that in it? Particularly if I anticipate being against +2-+4 with multiple foes around?
All enemy-affecting toggles suppress while you are Hidden. If Hide is on, but is itself suppressed, it doesn't suppress your toggles. Wow, that's awkward to explain.
In your example: Yes.
I personally wouldn't put Force Feedback in Repulse. It wouldn't fire nearly enough to be useful. Remember that in a toggle, it can only fire once per 10 seconds, and that it only has a 5 second duration.
@Roderick
Besides, you can't alter the endurance cost of Repulse. While you can slot for endurance redux which will lower the .40 END/sec cost to run the power, it will still drain 1 END per foe it hits every time the power tics. If you don't have anything else to slot and you were planning to pick up Repulse as a no-slot power to use when you get surrounded, I'd say go ahead and slot the +rech proc. However, I suggest not actually using it unless you're surrounded and you just want to get people out of your face. Repulse has a 10ft radius (I think) and a 16 target cap, so just activating the power will give you 16 chances for the buff.
However, I'm unsure how the suppression from hide works with procs. A good question is, if you're running the toggle while in a hidden state, and suddenly drop hide (from being hit or attacking), does the proc still only check 10sec suppressed or not? Or does unsuppressing count as 'activation' which would instantly check then?
The way the 10 second timer in toggles works is that the proc actually tries to trigger every time the power pulses, but once it checks it suppresses itself from checking for 10 seconds. So, while the Stalker is hidden, the power doesn't pulse, so no proc checks are made. If the stalker is surrounded, and gets hit, breaking hide, it will immediately fire on any enemies in range, restarting the 10 second timer.
@Roderick
I was recently looking into using a "chance to" proc in a crappy toggle power that I'd never normally take on my En/En Stalker until Fitness became inherent.
I was thinking of using Repulse, at least sometimes, like when I'm not in combat, something like a movement toggle. Not sure if it's worth it, but I was considering slotting it with the Force Feedback: Chance for +Recharge.
At: http://paragonwiki.com/wiki/Force_Fe...or_%2BRecharge, they still have text and a description of the suppression effects.
Does someone have a link to the change when that was fixed or was it done silently?
Two more clarifications, though.
1. I don't think it requires contact with an enemy to trigger, just for the toggle to be active. Similarly, even with a power like Footstomp, I would assume it only matters that the power was activated, not how many targets were in the radius of the attack. Can someone clarify that?
2. How often do Chance to powers activate on toggles? I was under the impression they check every ten seconds. Is the chance to trigger the same time for an auto and a toggle power?
Thanks, I'm sure these have been answered time and time again, but some people, like me, can't wrap our heads around them and paragonwiki I don't think has the info I need to understand how it's working.
BTW, this is a bit of a cross-post. I just replied to a thread in the search results that was similar to mine, but realized it was in the Controller forum.