Broodlord extra range BUG

I don’t know how it works but it seems to chase the unit until it is close enough and if it doesn’t reach the target it goes back to the bl. Considering that projectiles chase units indefinitely in this game, I don’t consider it a problem.

The broodlord attack isn’t a projectile. It was never stopped by PDD for example.

But here is the thing, if it does get close enough and hits, we are talking about a 15+ range broodlord

Hmm. Well, I have never seen that happen, have you? Maybe your theorycrafting doesn’t quite line up with reality.

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

So what are you suggesting? Corruptors hard counter every flying unit terran has… Because of that, thors are the only option, and they suck as well. If at least they could move over the broodlings (would be good if blizzard made massive units unblockable by broodlings).

u

absolutely wrong. The bug will be a bug, even if the developers do not fix it. You must work hard on your argument.

1 Like

That’s not a bug - it’s how the unit’s mechanic is supposed to work.

It’s a similar story with carriers and interceptors… after being launched, interceptors can keep attacking while the carrier can move up to 14 range. This is 6 more than the carriers default attack range… and twice as much difference than with broodlords leash distance. And carriers can keep attacking from 14 range until their target is destroyed. That is not a bug either. It’s how the unit works.

1 Like

The brood lords can stay at 13 range while auto-attacking.
Changing the target for broodlings (so unit size doesn’t matter) would be a thing imo.
–> see video on reddit (I believe it’s still the same)

Edit: I wouldn’t change the range itself though - brood lords with 12 range should be ok/balanced for now, but not 13. Else we’d probably have a lot of problems as terran can just camp and zerg can’t attack (don’t want to overdue it here as with any balance suggestion).

TL;DR: The bug is not about the range but about where the broodlings will land/attack first.

A bug is someone’s mistake in some cases the mistake is very easy to explain. But in this case not, someone put a variable so that bl can do exactly that have more range when you micro. For you to say that this is a mistake and not intentional, you need great evidence because of the unlikely affirmation. It would be great evidence that this is not intentional if Blizzard said it is not. But until then you have no logic reason to think that it is a bug. Some people want to believe that this is actually a mistake, but there is nothing to indicate that.

1 Like

It doesn’t seem like it really extends the range of the broodlords, as broodlords needs to go to the nine range to trigger the attack, but the slow animation allow broodlords to back before it shoots.

The test should have been perform vs a thor to truly see if broodlords outrange it (9 range vs 10), but it was done vs a tank that can’t shoot back.

edit : I’ve done the test, and it actually extends the range of broodlords, if you put thor on hold position run back at the right moment, it shoot the thors and broodlords isn’t touched.

Not at all, BC cost like 2 corruptors. Do 2 corruptors beat 1 BC ? no.

And vikings are much more cost effective than corruptors, they’re cheaper and if you micro correctly they crush corruptors with hit and run and landing them when low hp.

Broodlords have 10 range, not 9

BC’s cost 400/300/6

Corruptors cost 150/100/2

2 Corruptors cost 300/200/4

1 Like

Ain’t vikings best counter for BL?

They would be except for fungal and parasitic bomb. But yes, if the Zerg player is polite enough to not use infestors, then sure.

4 Likes

Too bad Terran have a caster who instantly remove energy, but don’t use it

2 Likes

They use it all the time.

1 Like

It doesnt instantly remove energy HT style, it removes 100 energy with cap being 200. Meaning if Z has same reaction time as you and is looking, he lands fungal on your ghost and kills it easily with supporting units while its unable to cast snipe, cloak or move away thanks to effect of fungal.

EMP does not slow or reveal infestor in case it is hit. Also, even with upgrade, EMP still less range than fungal. By tiny margin but theorycrafting ppl on forums still think it makes difference so I include it.

3 Likes

Incorrect. It’s only a bug if the developers consider it a bug. Otherwise it’s safe to assume they know it’s there (as it’s been around for 4+ years functioning in this manner) and consider it intended. If it’s not listed as a bug by the devs/PM, it’s a feature.

1 Like

PDD was explicitly patched to prevent it from stopping Roach or Brood Lord projectiles.

From Terran yes, but Vikings are also extremely easy to counter or zone with Infestors, Vipers, and/or Corruptors–Technically, Vikings were always intended to counter Corruptors, but in practice the Corruptors win on equal supply after the supply counts pass a certain threshold.

In practice, Brood Lord + Infestor compositions are favored in every match-up. The Zerg player has make mistakes in order to lose.

1 Like

The role of Thor is designed to be anti-massive, as mentioned by bliz in their own patch notes. Hence, the best way forward would any 1 of these.

  1. Bliz include this mechanism where BL can target above its declared range in the tool tip so there is no ambiguity for new players coming in and learning the race. There should be no Stealth buff.

  2. Bliz remove this bug of BL to be in line with what is advertised. Allowing Thor, a ground based unit with poor movement speed and maneuverability, to serve its role better.

  3. Increase the range of Thor to cater for this intended ability of the BL. At the very least, allow Thor the ability to increase the range of its attack above tool tip, by focus targeting on the BL itself, just like how BL can increase its range.

In essence, Thor should always keep its range 1 above the BL both when focus targeting and not focus targeting.

  1. Thor is still anti-massive, it’s just not a-move anti-massive against BL
  2. It’s not a bug, no one has any evidence that it is a bug. In fact, the tethering setting on BL in the map editor shows this is intended. It’s not even a stealth buff
  3. Tethering range isn’t mentioned for any units in tooltips so this would be a first.
  4. Doesn’t makes since as the Thor has no tethering mechanic and still counters BLs; it just can’t a-move against microed BLs (as intended)