UberGuy

Yep. It picks a random integer in the range 0 - (LIST_SIZE-1) and indexes into the array using that. And very welcome!

Yeah. Sidebar, but I remember testing it on the Paragon Training Room server before the shutdown announcement. My only high-level Blaster at the time had Hoarfrost, which used to be seriously truncated by the original caps. As a PvE-focused player, I was really jazzed about it, before, you know, it all shut down.

Have you met any Illusion Controllers? They'll still insist it's superior, even if it's the only one!

Yeah. I mean it does more stuff that its base stats, but it's very fiddly about doing so. If it's intended to be impossible to get those benefits in combat, it should probably cost as though it didn't have them, or maybe a bit more. (Note: I haven't run any math on its costs, so maybe the cost does somehow make sense. But based on quick mental analysis, it doesn't seem like it.)

He's saying the cancellation on action is intended. He should know - he added it. :P

Recovery Res is actually a different stat. But the fact that it's there probably means we should get End Drain res too, unless there's some technical limitation on it. (And there might be one - I remember some old talk about how updates to the things sent for the combat monitors cause networking code changes. But that was a long time ago.)

Um, no, that's not correct. This is from the JumpSpeed attribmod in Combat Jumping That means that powers with the "TravelBuff" stacking key will stack in a way where the highest value wins. This is the JumpSpeed attrbmod from Hurdle That's regular vanilla stacking almost every power in the game has. It means it stacks with other stuff that's not the same power cast by the same caster. So Hurdle stacks with whatever wins from the "TravelBuff" overlapping winner, as do other sources of +jumpspeed like Inertial Reduction.

Consume in Fiery Aura also grants this, and there's no way to check it there either. I have an FA brute and logged in to confirm I couldn't see it anywhere in the monitors - that I spotted at least.

Relatively simple test - try to find some Mu. They will sap both end (when their blasts hit) and depress your recovery. I guess it's hard to get a comparison since this is an auto, but you may be able to compare two different characters if end drain is logged.

Things like "was it that broken" or "it doesn't break the game" are strawman statements that don't have any objective basis. There are (admittedly not well documented for us) standards the devs try to follow for things. Why don't all attacks have some different range than they do now? I dunno, but they have pretty consistent standards*. A powers dev decided only "real" sniper mode attacks should exceed the now-standard ranges. I can see what they were going for, but they'd have to explain the "why". (I wouldn't mind knowing myself.) * If you were playing long enough, you may remember that stronger attacks actually used to have shorter ranges than "high" or "extreme" damage ones. So what we have now is way better, IMO.

Yeah. I mean, it certainly doesn't feel like that should be intended. I guess we'll have to see. 😒

The "fast" in combat snipe is no longer a sniper shot. It's just a high DPA attack. I mean, don't get me wrong. It's not like I'm excited about this change - I have quite a few characters with snipes. But I get that the "fast" version isn't following any of the rules that make the slow version different from other attacks - it has no interrupt window and a way slower overall cast time. It's basically a regular (though very good) attack. I don't see why it's either so terrible a change or so hard to grok the reasoning, even if I do understand that any downgrade is rarely enjoyed.

Wait, Corruptor. I looked at Defender stats. 🤦‍♂️ The base for Corrs is a whopping 1.192s. So even at ED "caps", you're looking at like 2.4s, so yeah, even even-level critters will wake up briefly.

So, I think the deal here is that the effect pulses every 2.5 seconds, but the sleep lasts a (base) of 1.49s. Against +3 critters, that's cut to 65% of base, so about 1s, which means you're never going to be able to keep +3s asleep. So yeah, it's basically impossible to keep things slept with that. No idea if that's intended - it seems kind of silly to me.

Based on its display in CoD, I think it should work. It also shows up in the detailed power info view in-game. I think the issue is that the combat attributes windows just don't have an entry for displaying endurance resistance as a stat at all.

Rather than berating others for lack of foresight, perhaps you should ask more players come join the testing. And join them. This is a bug that only appears in very specific circumstances - teleportation with a non-combat NPC targeted. That's something that people popping into Ouro to test teleporting around could easily miss. How likely was it that someone combine testing teleport with having clicked on a contact or open world civilian? As a reminder, this is a free game provided by volunteer effort, by people working on spaghetti code they didn't originally write without any documentation they didn't create themselves. There are only a handful of people working on code and powers (like ... maybe five?). They can't do that and test everything extensively while they have day jobs, families and other stuff in their lives. That's why there's a test server and a beta period. We have no choice but to test by throwing bodies at it - player bodies, because there aren't enough devs and no other QA department. So, in summary, be less of a dick about something you get for free from other people's labor.

As @Arbegla says, it's because the best power now wins. Remember, you could not run these together before. The intent is not to change them to be stackable when they weren't before - it's to let us get the bet of all of them at the same time when run together.

To be clear, no defense granted by any IOs is being stripped, at all. If you're just talking about these new-ish powers that give you defense but let you act, remember that what they're replacing prevented you affecting friends or foes, so the defense they granted came at a high functional price. That price has been removed - if we could fight while unconditionally keeping the full defense these new versions of old powers grant, the devs would just plain be giving us new sources of in-combat defense that we did not have before. I think a lot of us feel that the bonus defense in these powers is so trivially suppressed it might as well not be there, but let's see where things go.

The code for leveling up in the respec screens is apparently rather fragile (IMO) in the sense that it figures out what level you are based on how many powers you have that meet certain criteria. Powers in certain categories, like "temporary powers" and "inherent" don't count for this, nor do powers explicitly marked as "free" (that's a setting on the powers themselves). It looks like the "Momentum" power, which is in none of the "free" categories and not explicitly be flagged to be "free" may be the issue. If you turn of SS or let Momentum expire (it only lasts a few seconds) before you respec, the issue may not appear. The devs have this info, so hopefully it will be fixed soon, if the above is the actual/only issue.

Just based on the testing cycles we say for beta, it seems likely each patch is given a few days to be implemented / reviewed / tested before it goes to any of the test servers. Also, given that none of the bugs so far are causing "all hands on deck" issues like crashes or character corruption, waiting a few days to see what other issues players can find, so they can also be rolled into a patch would make sense, rather than pumping out a rapid sequence of small patches.

Out of curiosity, do the affected characters all have Super Speed?

If you disabled your popup tray, and didn't add Afterburrner to any other tray, then that is why. The "display name" only works if the power is in a tray, If the popup tray is disabled and the power is in no other tray, then it won't be found by display name.

Or you could read that (a) there's an extremely simple workaround and (b) a fix is inbound to boot.

It's not a programming thing. It's just how the power's settings were chosen, which is "just" a data thing. No one will have to make code changes to update this, nor is the code doing anything out of place. The settings for the power are, however, being questioned and, it seems, updated in the next patch.

What you are saying you tried and what I suggested you try are not the same. I know what I posted works, because I am using it successfully. My bind turns on Fly first if it is not already running. This enables the "Afterburner" power (display name), which puts it in a tray. Then, and only then will the "powexec_toggle Afterburner" be executed on the next press, which will work using that name because it is in a tray.