[TB 1.1] Attack ranged reduced?[Bug?]

Is it just mean or did the Torch Bearer's attack range get reduced. I just played a game and it seemed like my TB would get way to close to my enemy before he started attacking.

demigod

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

In Ice mode right? It's yet another of the autoattack bugs. Attacking something out of range causes ranged heroes to move up to the target instead of stopping at the limit of their attack range.

Successfully updated karma reason!

Quoting InfiniteVengeance,

reply 1

In Ice mode right? It's yet another of the autoattack bugs. Attacking something out of range causes ranged heroes to move up to the target instead of stopping at the limit of their attack range.

This is not a bad thing. Having him stop at the max range has its drawbacks also.

Getting up close: Pros- If the enimy runs, you are closer to start chasing. Con-you got close, and if you need to run that is bad.

Staying at a distance, just reverse the above. To me, micro is important. I would rather them close the distance and fire, and I can manualy stop my DG at max range, rather than he do it himself and me have to force it to close the distance.

Really this is not a "bug" really. Fire TB on the otherhand has a number of bugs that need fixed asap.

Successfully updated karma reason!

Yeah it's with ice mode. I could have sworn this never happend before 1.1 though.

To me, micro is important. I would rather them close the distance and fire, and I can manualy stop my DG at max range, rather than he do it himself and me have to force it to close the distance.

True, but how do you make him attack who you want when you are more worred about posistion?

Successfully updated karma reason!

This is not a bad thing. Having him stop at the max range has its drawbacks also.

Getting up close: Pros- If the enimy runs, you are closer to start chasing. Con-you got close, and if you need to run that is bad.

If I want to get closer I'll click closer. It's definitely a bad thing. If they start running you'll start chasing as soon as they leave your attack range which should be right away assuming you're standing at the max range.

Would you ever want to run up to a tower? A melee hero? Of course not. Fire and frost nova will even hit people from near max range anyways so it's not like you need it for those.

Successfully updated karma reason!

The default behavior should be to sit at max range and fire, if you want to move closer do it manually. Figuring out your char's max range is difficult, so to get a char to sit at max range manually would be nigh on imposible for shooting things like towers as Reg.

Successfully updated karma reason!

well i can appreciate the fact that they close in a bit then fire on a movable target. I hate it when I'm chasing at max range and my guy keeps ALMOST firing.

Does the default behavior make your DG close in a bit past max range to attack a tower with your ranged attack? That would be a bit silly. It's not about to run anywhere.

Successfully updated karma reason!

well i can appreciate the fact that they close in a bit then fire on a movable target. I hate it when I'm chasing at max range and my guy keeps ALMOST firing.

That's a bug with the attack animations, they could fix it if they wanted to (if you start the attack animation you finish it and launch the attack no matter what, kinda like casting a spell on someone who moves out of range)

Note that Regulus NEVER has this problem because he launches his bolts with no animation cool up time. TB and QoT are not so lucky.

Does the default behavior make your DG close in a bit past max range to attack a tower with your ranged attack? That would be a bit silly. It's not about to run anywhere.

Only if you issue the autoattack when you are outside your attack range. If they're in range already you just start firing, but if you're outside, they move towards the object even after reaching the range to start attacking.

Successfully updated karma reason!

I don't understand why this was changed, at all. Of course, unless it wasn't intended. But still a weird bug in that case.

Successfully updated karma reason!