Broken Controls (Targeting)

The controls in this game are absolute garbage, broken to the point of being anti-intuitive. I have played many RTS, ARPG, and MOBAs; I have never once played one where the characters were so utterly retarded. /AFK is apparently the subtext of literally every button in this game, and the loss of visibility, and RNGesus deciding he hates you.

Moving to a location? Activate horse? Continue to your location? Nah, just /AFK

Use a targeted ability to dash to, pull to you, snipe, or otherwise nail a champion? Follow up by chasing them with auto attacks? Nah, just auto attack that minion next to them instead.

In the middle of combat, chasing an enemy with 1 HP? Activate whirlwind? Continue the chase for that last hit? Nah, just /AFK

How anyone on the dev team, or a single player even qualifies this as functional, no less playable, no less actually good; I’ll never know. Then again, I guess most of them don’t, considering this game has such a dead playerbase that even the developers abandoned it.

/ragequit

EDIT: I posted this further down, but I’ll add it up here too:

Did some super exciting testing in training mode to see exactly how/why this is so broken:

First off, every single stun/knockback in the game triggers /AFK mode on your character. Even instant effects like Lucio’s boop. As does losing visibility on the target, or the target going invincible.

Second, every(?) skillshot cancels your target. This means if you charge into an enemy with Diablo, and then launch fireballs, you’re now attacking a minion, instead of chasing your intended target. Seemingly, it used to work that way with any ability type, which is why the D3 monk was completely unplayable when he came out, but he actually seems quite sticky now.

Some champions seem further broken/bugged. If you right click a target with the D3 Barbarian, and then use whirlwind, it works as expected. However, if you acquired your target by smacking them with Seismic Slam, and then Whirlwind, you go /AFK.

Heals, (and maybe targeted damage abilities, if there are any), don’t negate your inputs. IE: If you tell your character to walk back to base, but heal a guy in the top lane first, you’ll walk to top lane, heal, then walk back to base. However, if you do the same with a damaging skillshot/ground targeted ability, then you’ll /AFK after the ability, and not walk back to base.

1 Like

6 Likes

The fact that you call heroes “Champion” just shows that this is a LoL player’s hatethread.

Goodbye.

3 Likes

Buy a new keyboard. I dont have that problem

If anything, I hate LoL even more than this game, so no.

You’re saying if you summon your horse while moving to a location, the movement resumes once you’ve horsed?

Yes. Do you use shift commands?

You know this is HEROES of the Storm right?

Yet you call heroes as CHAMPIONS, which is what they’re called in LoL?

You’re not very convincing.

Giving a command afterwards or using queued up commands is that hard for you? Sad

I don’t even know what you’re doing here aside from being a ranting loser.

1 Like

:salt: :vulcan_salute:

Did some super exciting testing in training mode to see exactly how/why this is so broken:

First off, every single stun/knockback in the game triggers /AFK mode on your character. Even instant effects like Lucio’s boop. As does losing visibility on the target, or the target going invincible.

Second, every(?) skillshot cancels your target. This means if you charge into an enemy with Diablo, and then launch fireballs, you’re now attacking a minion, instead of chasing your intended target. Seemingly, it used to work that way with any ability type, which is why the D3 monk was completely unplayable when he came out, but he actually seems quite sticky now.

Some champions seem further broken/bugged. If you right click a target with the D3 Barbarian, and then use whirlwind, it works as expected. However, if you acquired your target by smacking them with Seismic Slam, and then Whirlwind, you go /AFK.

Heals, (and maybe targeted damage abilities, if there are any), don’t negate your inputs. IE: If you tell your character to walk back to base, but heal a guy in the top lane first, you’ll walk to top lane, heal, then walk back to base. However, if you do the same with a damaging skillshot/ground targeted ability, then you’ll /AFK after the ability, and not walk back to base.

That doesn’t fix the problem, if anything it makes it even worse. Walk all the way to the target location and THEN get on your horse?

Utterly irrelevant nitpicking, because you know you can’t actually defend how bad this game is.

Yes, it is indeed quite hard (anti-intuitive, and harder than it needs to be, at the very least) to manually re-click on a specific target in a clusterF of moving targets multiple times per second just because the core gameplay in HOTS was designed and programmed by a monkey.

Pretty much just for that reason; to rant about this game being a loser.

I’ve never seen a game in this or similar genres so poorly designed, and apparently some other people have brains big enough to notice as well:

https://www.reddit.com/r/heroesofthestorm/comments/5a2v8d/lets_talk_about_auto_attacks_dropping_after_using/

https://www.reddit.com/r/heroesofthestorm/comments/48mi9v/whats_going_on_with_autoattack_targeting/

I do this anyway because I’m constantly readjusting my position so I’m not eating skillshots by moving in such a predictable manner. I think many do this too which is why it’s not really an issue for anyone else.

Depends heavily on your character type. If you’re a healer, then sure. If you’re a ranged DPS, then maybe. If you’re a melee, then probably not.

Even if I’m melee I do this so I can stutter step into creating a body block or I’m stutter stepping so that my back isn’t near a flanking bush to get hit by skillshots or just to bob and weave so anyone launching things at me won’t hit me because I’m already moving.

If you make a beeline for your target, you basically make it painfully easy for skillshot heroes to tear you apart.

I have never played a moba, or rts before this one. Never had any issues with controls. :woman_shrugging:

Sure, you don’t faceroll walk into them, but once you’re already engaged you generally stick to them, which this game goes out of its way to prevent. And most melee champions have some kind of dash to engage in the first place - which is when they acquire their target, and should keep it.

But then you have to body block to hinder their escape or they can just walk straight out. I will never NOT stutter step as a melee character.

  1. Stutter stepping was bug abuse in LoL, and should have been fixed, not developed into a core mechanic.
  2. If they don’t want auto attack targets to exist at all, then they should make them not exist at all, not have this utterly broken joke of a mechanic in its place.
  3. That’s relatively character specific. Diablo generally wants to be behind his target for grab slams. The D3 barbarian is generally in perma-chase mode while whirlwinding. The D3 monk attacks very quickly with his buff up, 4 times a second(?), you’re not making relevant use of stutter stepping there, unless you’re godtier APM. etc

As they (supposedly) say at Blizzard, “Better is better.”

Some dont, like maievs Q.

Wow this sounds horrible tbh

This sounds so inconsistent tbh, i am actually mad about this targeting thing too, to the point i almost made a post similar to yours.

I guess you havent played imperius yet, that is the worst designed hero in the game man.
It’s so bad, when you Q an enemy, you dont deal damage. You gotta trigger the damage with an auto attack, but since imperius stuns himself too when he uses Q, he goes AFK like you say and the next basic attack is against whatever minion or anything that is closest to him. Which means you are gonna lose a lot of kills.

I think you completely nailed the problem. I agree totally that this is detrimental to the game in a very stupid way.

Also if you are pissed about this, go check out how Medivh’s portal moves your camera around so you miss skillshots, that is just unbelievable.

2 Likes

Idk what’s the problem with people at the top of this thread, but controls in hots, let’s face it, aren’t perfect, they sometimes feel clunky and unnatural.
For example, Right Clicking enemy hero with Hanzo locks his AA on that specific target, but as soon as I cast Q then his target changes to the closest enemy, why? Nova, Cassia or Even Raynor doesn’t have the same issue. It feels weird, and out of place.

1 Like