UberGuy

That would be nice. However, currently you definitely can't.

No. He said what the functional effect of the issue was pretty clearly, I thought. The effect reapplies but in unexpected and undesirable ways. The additional stack causes you to rehide some time later after the first one expires.

What should happen: AS, hide, attack with crit+unhide, stuff, AS, hide, repeat.

What happens: AS, hide, attack with crit + unhide, stuff, AS, delay that depends on the last time you AS'd where you don't hide, seemingly random hide at a later time.

Edit: What you are probably seeing:

What we are describing:

See how in the second flow the HIDE events are not happening after the AS, but are happening in the middle of other attacks?

The forum editor stinks for letting us lay out text, but what is happening is that when you can attack fast enough to overlap the suppression, your hide starts happening at the end of the prior suppression, which is well after the AS. It should simply not hide you at all, not hide you at a time later that usually feels (but isn't actually) random.

I'm sorry, you know a lot of people who will cancel over that? I honestly don't believe you, or we have very different notions of "a lot".

I'm not pleased about this, but throwing a "I'm quiitting" tantrum over it is wildly childish.

How has this been determined? How do we know what that mechanism is or how it works?

And again your true colors shine through. You will fight to take options away from other players because you're put out that the devs took options away from you.

I'm someone that IOs 50s pretty heavily, and I'd be pretty surprised if that's the case. I've only ever seen players suggest that, not devs, and my personal opinion is that they're seeing the devs try to balance the content around the expectation of players having things like Destiny buffs and Judgement blasts. From my perspective, that would look a lot like the balancing of critters for the expectation of IOs.

That's good to know. I was going off of someone else's posted reports.

Agreed.

I suspect you're correct, but I also suspect that the SBE mechanic came first and was re-used for the Stalker AF mechanics. It's definitely a handy tool for them to have, though I think to be really complete it should include some account for power activation times as well as base recharge times.

Edit: According to this post, it actually does account for cast time.

By the way, I don't think this proc can reasonably be used as evidence that the devs hate Blasters, since Controllers and Corruptors got a PPM damage proc too.

But we do have evidence that it does do this, at least for some sets of conditions: the testing of PPM procs placed in "single-target" Tanker powers. In practice there are no single-target tanker powers, since even the ones that we think of that way have a target cap of five. 4-PPM procs slotted in powers with 15s or greater recharge are working out to 20% chance to proc ... which is 1/MaxTargets of what they "should" be if they really were single-target powers.

We know that area of effect should be factoring in somehow, but it's possible that area is somehow applied stepwise (e.g.: radius < 10' = no effect), which could explain why the Tanker attacks would be working out to exactly 1/MaxTargets instead of something else.

That would certainly suck. It doesn't seem to me like something they'd go to these levels to avoid, though. He's the only example of that I know of.

Nope. (I know you knew that answer.) However, I don't see that as a significant issue overall. Let me put that in perspective. I am in the process of leveling up an old Mind/Rad Controller heroside. She's currently 44. She's got very limited IOs, being mostly equipped with commons and cheap "frankenslotted" stuff in her mezzes. There are lots of AVs in the hero-side level 40+ story arcs, which I'm downgrading to EBs because I'm soloing.

While /Rad is very nice for soloing, Mind/Rad is doing very little to protect me against EBs with Purple Triangles of Doom. I can't meaningfully debuff their toHit, attack rate, or run speed, because the PToD give full-time, high resists to all that. Mind lacks an immobilize, so I can't get containment. I'm not using Shivans or Signature Summons or Backup Radios.

And I'm soloing them on +2.

So I'm not some wildly tricked out IO build, and I'm certainly not Incarnate. No level shifts, no Interface DoT, no Destiny buffs. And I'm soloing +2 EBs with a Mind/Rad. My Inspiration tray is my friend.

Sometimes I even die.

But even when I die, the ultimate outcome isn't really in doubt.

So, no, I really don't have much concern about getting these guys as EBs, even with PToDs. I really don't.

I actually tested that last Saturday, and that wasn't the case. I tried carefully adding the beacons to the room in the order that I wanted them to appear but it didn't affect the order, as far as I could tell.

Unless I missed a test case, I am thinking there is a fixed, internal ordering of beacons, and they will always appear in that order.

Standard inspirations would have to cost something like 1M apiece or more for me to consider buying them off of a store based on sheer availability. Store bought inspirations have benefits that in-game ones don't, like lasting five minutes and the ones with durations persisting across deaths. If there's anything to what you're saying, I would find it immensely ham-handedoverkill in trying to drive people to the market inspirations.

When a power is brokenly good, I think most people recognize it, even if all don't state it openly. When such a power subsequently changes, such people likely think of it exactly in the terms you're mentioning. I'm not seeing many people in this thread think this power was brokenly good. I find it hard to believe there was such a standard intended "from the start".

I used a bunch of respecs, but I certainly don't feel I wasted them. All of them weren't made to make urgent changes, but all did things I wanted to do for my characters (whether specific to this issue - like my Stalker - or not).

My only potential source of irritation about the topic depends on their reasoning for not offering one this round, which they might never tell us. Of course if they don't, folks' imaginations will provide one.

Yes. In fact, this was such a common and well-known player behavior that Community Reps have, in the past, set a convention of reminding people to do this. In fact, we once received an apology when one forgot to provide this reminder.

Based on what standard of "should"?

In a mission, there's no reason for him to be hard-coded at level 54. He should be your level, plus any increases set in your mission difficulty.

He should be an EB if you set him that way, or an AV if you set him that way.

The same with Reichsman. The one in the Kahn/Barracuda TFs is empowered by his dimensional power sucking device. The one in a mission need not have insane-o HP as an AV.

But that is not its design goal. Its design goal is to create a path which is not iTrials. That's a path you can solo. EBs are apparently assumed to be soloable. AVs that can be turned into EBs are therefore soloable. That remains a path you can solo. There is no issue here.