Booper

It was outdated and no longer maintained. The OP told me to go ahead and unpin it.

This was brought up before, the most recently (that I recall) was when the NCSOFT Licence Agreement was announced. In the FAQs, the following was mentioned (see screenshot):

Can you double check that, because that would be a bug. The Stealth IO should always turn off when the power it's slotted in is toggled off. Edit: I see in the comments this got figured out. Disregard my redundancy.

That's a poorly written commit note by me. Sorry about that. It should read Slow (normal) Moonbeam now has a 100% chance to crit from Hide in PvP. Was 50% previously.

That doesn't sound very fun. Fun would be to start vector knocking squatters into oblivion, then having them drop into the pool. Now it's a pool party, and pool parties are fun.

Locked per OP's request.

Don't get your hopes up. Edit: In the mean time, take advantage. This is the first time players can see the pool in its original unfinished state.

Sleep.

Note to self: "My mom made me wear this" badge

The reason he is recommending -def is so it counteracts the to-hit debuff on the confused foes. You get far more impact converting their (let's say) 20% chance to-hit to a 50% chance to-hit after dropping a 30% defense debuff on all of them.

Signatures don't always show if you're looking on your phone. But this is where you can find it: https://www.shenanigunner.com/

Pinging for follow up. Is this still seen on beta, and is it also seen on Live?

The sleep Grenade bug should be fixed internally. As expected, there were remnants of when the power was foe-targeted causing the issue (location AoEs should have affected target be the caster, it was still set to foe). The disappearing act should not be seen in the next build, but if it is, let us know.

This is a good guess, and is the first thing I'd check. But I think the issue is something else. Should be a simple fix once we get a look at the details. In the meantime, maybe test blaster glue arrow and see if you see a similar bug. Glue arrow may not be a great example as the pet is autohit, but I'm blanking on foe targeted pseudopets that create a patch that isn't auto-hit. If you can think of one, do try it.

Nothing wrong with spreadsheets. It's data aggregation, and making sense of all the numbers. Too often it gets misconstrued as a calculator where you throw in inputs and get an output. It can be used for that, but it's a far cry from everything you can use spreadsheets for. Without spreadsheets, you're just working off memory, and that's typically faulty.

Thank you. This is a known issue, a previous fix attempt was missed in the merge request, but it is fixed internally and will be in the next build (probably Saturday).

Incorrect. This is a multi-page effort. There are a number of sets planned for future release. Some were held back for technical issues (a bummer, because we really would've liked it in this page for what will someday be for obvious reasons), while others just needed further development. Edit: I don't mean to reply to only a portion of your post to correct you. I will love to expand on my response to address many of your concerns that are valid. I will have to do so later when I have the time to type out my thoughts with better clarity. Right now, I would be rushing it, and I believe it would not be as helpful to you or the community. In short, this is phase 1. There are more phases to come. I'll explain more later.

Thank you, can you post this in the Beta Bug Report forums? If it's not already fixed internally, I'll make the change tonight.

Spoiler, it wasn't fixed...but now should be fixed internally? We'll see with next build.

I believe you mentioned in the Focused Feedback thread that you're still seeing this in RC2. @Captain Powerhouse, can you follow up on this?

Can you check to see if this is still an issue in RC2?

Known issue, there is no fix. A new attribute was added beneath the hood, but it has no player-facing impacts at this time...with the exception of causing some monitored attributes to shift by 1 index. I'm sorry for the inconvenience, but you'll have to fix your monitored attributes after this goes live.

I saw Dominators had it, but the others didn't. Fixed internally, will be in next build.

Should be fixed in RC2, but if you see it still happening, let us know.

Is this on Brainstorm? Are you seeing the same thing on Live?