Captain Powerhouse

The extractions being summoned at -1 is a bug and just pushed a commit. Extractions before this being summoned at even level was an unnoticed bug, though. They were always intended to be tied stat wises to the henchmen they get summoned from.

Today's notes:

These changes are not out in beta yet but just in case the patch lands while im in lala land and no notes are posted, this is what SHOULD be on the next patch: Sonic Melee Attune Adjusted vfx Cast time reduced from 1.67s to 1s Range increased to 20ft

Here are as far as I know the last few patch notes, have not gone through all of it just grabbing them from a repo and newer ones iterate/change/fix things that were not right in the previous one. Sorry for the inconvenience.

I don't think you will have to (but not sure how much information the server saves to determine that so can't confirm it won't happen either).

It was changed to half a second recharge a few builds ago. Oh... .25? I thought it was half... hate being wrong (as many will attest) so going to nerf recharge and double it to 0.5s!!! (joking)

A single target aura would either hit a random thing around you or have a requirement that something set the flag on the target and we are back at square one PLUS any other sonic melee user could break the whole thing because now there are possibly multiple valid targets and the power starts randomly picking one. If it was possible to control such power's target to cooperate with the player, the power would had already be turned into a click power that pseudopet that effectively does the same without sacrificing the goal. Trying to jump into the spaghetti code to add something that lets me do something akin to that is one of my hopes during the downtime period.

A self aura would be a completely different thing that would likely force the entire set to be rebalanced as we are now talking about an AoE effect. It's not unlike asking for Disintegrate and Boggle to be AoE also. If you mean a toggle that simply enables the effect, again we entering similar situation of entirely tossing the concept of attunement against chosen targets and making it a second booster. And if you mean an aura with a single target, there is currently no reliable way in the game to make sure that single target is YOUR target. Especially if there was another Sonic Melee character around. Even if we considered any of these, keep in mind we are talking about post-launch adjustments, not any change before launch but it the first two options are entirely not within the scope of the set goals.

For what it's worth I do personally also have some issues with the toggle. I mentioned this just now in Discord but mainly my issues are two: Double tap accidental shutdown Hard-ish to decide to remove from one target and move to the next because it requires double tapping to turn off and on again, and that later can compound big time with the first point. As some have noted, I just tend to keep Attune in a separate bar (where I keep Build Up/aim/etc) where I only click with very intentional timing and rarely more than once (the game queues the attack so multi-tapping is not really needed... oddly if you a mouse clicker (the way I can be) not all mouse clicks register so I still have issues with that regardless unless I alt-num. The second I really have no easy solution unless I can come up with a scheme that lets me do what I want without a toggle. I still prefer the current implementation than the refreshing click as constantly refreshing on a hard target is even more annoying than the previous two issues for me. I detest that about Disintegration and Boogle. Plus I really like the dots go up with fury or with Boost Up or Inspiration usage without having to refresh Attune after a Boost Up use. Anyways all of this is saying, even if it's not entirely the same reasons some of you dislike it, I can sympathize on wanting a non-toggle solution. But honestly also feel the toggle is a way better state to roll out with than an awkward constant refreshing click [and making the state last forever as a click is not likely to fly as all it does is make players feel like they need to start clicking it on everything].

This is a fascinating example to use in this discussion, because listen to whom? There are players that begged for the power not to lose its existing functionality as they would use it for phase av in some content types. If we CAN retain such functionality and add a new feature, we will. But we won't listen to players telling us NOT to listen to another group of players. Especially when that other group are advocating for the state of the set/power, power that was not being changed due to over-performance issues. In the past we have changed some powers with the intent to improve, and sacrificed previous players attachments to said powers and not because they were overperforming. We considered that to be a mistake and try not to repeat it. The fact that the phase functionality remained is precisely proof that we listen to players and tried our best to deliver a middle ground. And funny enough, there are further tweaks in the queue for the test that have been tested in closed beta... or at least hit, not sure if some of the advocates for phase actually tested it, but in the time it was there we didn't hear complaints. Frustratingly, that change could not make the opening of the page due to merge conflicts as it was a very old branch. But do stay [a]tunned 🥁 (ok I'll walk myself out... a gain).

I wont lie... I did face palm 👀 (sorry @GM_GooglyMoogly)

If something like that was possible, it would already be in. There are some things I plan to play with in the coming months, some might need new code to work reliably, though. I also attempted using invisible pets but it's impossible to reliably control what they will target without running scripts, and I rather not be attaching scripts to a power that players will be activating rather regularly.

The fix for this did not go out until about 4 hours ago. Did you test after that? If so, you testing on stalkers, correct? Edit: found the issue (entirely different error this time, not repeating errors is good... maybe...) so that should go out next build.

They are different things. Easier: make the power info screen not mix them up. Also: i thought i added the clarification to the notes before going open beta? Did it not make it in?