Broodlord extra range BUG

https://www.reddit.com/r/starcraft/comments/ct1s5u/bug_broodlords_can_attack_from_up_to_13_range_away/ Found this burried reddit thread
And also this test, showing this bug has been since 4 years ago
https://www.reddit.com/r/starcraft/comments/2yqewu/broodlords_have_the_same_range_as_a_siege_tank/
I have tested in the actual game with my friend. If broodlord use the “hit and run” method the broodling will be launched at more than 11 range, before thor can shoot, which gives broodlords extremely long range.
I think this is more of a game breaking bug than anything, because this renders thor range buff completely useless and made broodlords offically outrange any ground units in the game.
I hope blizzard can see this problem and fix it before blizzcon. Hope.

16 Likes

4 years and still not fixed. You think they will fix it now?
Who knows.
But before this, Winlords officialy can be called ImbaLords.

Thors are supposed to counter broolords. With this bug 10 broodlords can kill 10 thors without even taking any damage.

It is broken and needs to be hotfixed.

4 Likes

If you can’t counter a slow unit that can’t shoot up, you need to seriously step up your play.

3 Likes

I will let people here think a bit about unit design, the many different stats that make up a unit and why it might be appropiate to have a temporary range of 13 on a 10 range unit. I’m curious to see if anyone reaches the same conclusion I did when thinking about this for more than 2 minutes. Will post when I get tired of people crying about things without considering factors. Think about the whole process of the broodlord engaging enemies and attacking them.

Oh, by the way, it has been a well known “bug” for a very long time and, if my explanation (which makes pretty good sense IMO) is actually correct, it is pretty much guaranteed that it is intentional. So… I wouldn’t get my hopes too high for it being changed any time soon XD.

1 Like

I don’t get it. You are saying that this bug should not be fixed? How I play has nothing to do with this bug, because Dark and Solar were using it in GSL, and they won.

1 Like

Liberators used to have extra range because siege liberators have collisions. They changed it and make liberators stack even while sieged. So I believe extra range is not intentional whatsoever, especially after they buffed thors’ range wanting them to counter BLs. If it is intentional, why didin’t they buff thors to 14?

I want to make something clear, the game does not belong to the crying terrans of the forum. Until blizzard doesn’t say this is a bug it isn’t no matter what you feel or believe is the right thing. It doesn’t matter how many threads you do repeating the same. If you want you can make a sect to talk about how op the bls are and how good you are in sc2 but the game is unfair for terran

It’s not a bug, it’s tacitly intentional by blizzard keeping it in the game. Feel free to die mad tho.

1 Like

This is just like how the IT damage was bugged.

How much Zerg late game dominance is because of bugged late game units working together?.

3 Likes

This isn’t like the Carriers leash range, this is something that isn’t supposed to happen.

It is not, in that case the balance team immediately said it was a bug

2 Likes

You have no clue if the devs intended that for some design reason or not. (and there are valid design reasons to have this occur, it is easy to think of a couple of them).

If you have any clue, prove it. I would ask you for a convenient video like you did, but because I’m feeling magnanimous I will settle for an official post by blizzard on the matter.

This “issue” has been known since quite a long time already, so blizzard have had time enough to adress the issue. So there, go and dig through their posts and find something. I will not listen to anything you say until you prove one thing, and neither should anyone else in these forums.

You have no credibility because you are always asking for other people to prove what they claim without you ever proving anything yourself being the huge hypocrite that you are, so there, go do it for once. Find one piece of evidence that proves it is unintended by blizzard. I don’t have to prove anything because even though it is a known situation for a very long time it has been left there still here htt p:/ /i. im gur. co m/43 ZkGl u.jp g (credit to eneyeseekay for the datamining 4 years ago), hence it is obviously willingfully featured. Also the team have had ample time to change it since then if they had wanted to. And while you are at it go prove that you play infestor-broodlord all the time. That should be an easy one right?

Either way, prove something. Do not adress me unless you have proof of any of the claims you make. I prefer not to talk to hypocrites who can’t adhere to their own standards, so do that or bugger off.

1 Like

It shows that you know a lot about the map editor, it only took me a few seconds to verify that this variable is the one that determines how far can go the broodlings why would anyone put that there?

1 Like

Broodlings are only supposed to go out 12, not 13. Which is what people are talking about.

I double checked this several times in the map editor previously and can’t figure out why they are going to 13 range at this point.

3 Likes

It is 12 the range but is measured from the outer circle of the target unit, broodlings are not left in the center of a unit

2 Likes

I’m aware of that. So what could be causing the broodlings to be launched at 13 or more range?

1 Like

What? I’m telling you that the range is 12. What evidence do you have to affirm that the range is 13 or more?

What happens when a broodlord tries to attack something fast moving on the ground. You will see the broodlings in the “ready to fire/drop” mode following the target.

Now I know why I always win with only BL against Carier Tempest and BC Viking comp. Okay lets nerf it

1 Like