- Misha, Attacca! (D) / Misha, Segui! (D)
- Misha, Vai! (1)
- Spostato sul pulsante del tratto (predefinito: D)
- Attivare Misha, Vai! su di sé richiama Misha verso Rexxar. Una volta raggiunto Rexxar, tornerà in stato neutrale.
Questo cambiamento è stato accolto positivamente da alcuni giocatori, ma molto negativamente da altri che segnalano una notevole perdita di precisione nel controllo dell'orsa. In molti hanno segnalato che per migliorare la situazione occorre mettere il lancio del tratto (la D) su "quick cast".
Il Game Designer Adam Z. Jackson è intervenuto su reddit per spiegare che nemmeno il team è soddisfatto della situazione e stanno cercando una soluzione elegante al problema che non richieda configurazioni personalizzate dei comandi.
BlizzAZJackson ha scritto
I've been keeping an eye on these threads and wanted to give some insight into Rexxar's control changes, as it's obviously something that is controversial in the community (and rightly so). What makes this difficult to evaluate on our side is that no matter which scheme we've gone with, there have been many responses from people who feel both negatively and positively about how he feels to control.
These changes were not easy to make, and we knew going in that out of everything in his rework it was moving his Misha controls to one button that was going to be his riskiest adjustment. Modifying his control scheme was not meant to "dumb down" the character for higher skilled players in favor of newer ones as much as to make it easier for everyone to have more control over Rexxar and Misha. We felt that it was better design to have everything related to his controls be on one button instead of two as long as he didn't lose any major functionality in the process. Between the two control schemes, the only thing that Rexxar truly lost was the ability to have Misha passively follow him around and not attack enemies for an extended period of time. I am also a huge Rexxar player personally, and found that the idea of having this functionality was more attractive than it actually being useful in my normal gameplay. With the new scheme, it's also easy to just move Misha behind Rexxar and she will stay there while she gets healed up if it is that necessary to take her out of the fight.
I will say that the one thing that we're not completely happy with is how often Alt + D is necessary to press to bring Misha back to Rexxar, as that is a fairly common and necessary command to use that isn't completely intuitive. However at this time we haven't found a clean solution that doesn't involve having 2 buttons again.
We've seen mention of Misha's AI being broken often enough to be concerned, however after playing him a bunch and testing specifically around the AI, I haven't been able to reproduce any glaring issues with Misha not following Rexxar's commands properly. I've currently asked a few of our QA guys to see if they can find anything, but without better direction then "people have been saying that Misha doesn't always do what they think she should", it's going to be hard to narrow down specific issues. If anyone could post reproducible steps or specific scenarios where Misha is not behaving properly, that would greatly help with narrowing this down for us so that we can make fixes or improvements to her AI.
As always, thanks for your passion for Rexxar. I hope that this gives some insight into our thought process and why we decided to go through with modifying his control scheme despite the risks.
Hello, level 20 Rexxard reporting in.
I believe the main issue people are having, without realizing it, is that when you changed the controls people were probably using quickcast on "Misha focus!", but when it got moved to the trait key it may have been using their default control scheme (On Release for me).
It took me a day to figure out why the controls felt so sluggish, but after I put the trait on quickcast it felt very good to me (I have a control profile that mimics the old scheme too with "D" being set to quickcast "alt+D" and a mouse button being set to "D" itself).
Simple solution for Blizzard:
Make the trait an instant cast ability
Allow people to order Misha outside of leash range
Constantly show leash range for Rexxar
I agree about Quick Cast. I personally think it's the only way to play him, and when my sister picked him up the other day the first thing I told her was to put commanding Misha on Quick Cast.
However, as a general rule we don't force Quick Cast on certain abilities/players, as there are always many who do not like a specific method of control, and keeping the default always being "not" Quick Cast makes it all consistent (how weird/confusing would it be if you were new to the game and it arbitrarily had different things on auto-quick cast and others not?).
Constantly showing the leash range for Rexxar is a dicey proposition, but I'll make a note to see if we can do something here (maybe something like Sgt. Hammer's siege mode range). The thing about showing ranges of everything is that while it's somewhat useful, it adds a lot of clutter to the screen, and readability is one of those often underrated things that can have a huge negative impact for many users.
I've seen this kind of feedback on Lucio's aura as well. The fact of the matter is that if everyone saw it all the time on his/the enemy team, it would add a ton of clutter to everyone's screen for a relatively small gain (most of the gameplay should be on the Lucio player to be in range of his allies).