-
-
Notifications
You must be signed in to change notification settings - Fork 534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bunker Buster update #4090
Comments
The problem with the bunker buster is that it shoots at the nearest targets, not primarily buildings. This is not only a problem with this weapon, but it occurs more often on it, because the damage on non-construction targets is almost negligible. |
BB is something that always required some micro management to be useful but it's an highly rewarding nutcracker. |
Firebolt rocket sounds really cool, though I myself requested a twin bunker buster some years ago. I'd even go for a quad linked bunker buster ( higher firing rate ) variant. |
It could be done quite simply, take existing design and just copy then paste the barrels side by side. |
Describe the feature you'd like
A progression of upgrades from a mid-game rocket to a late game item specialized in fortess busting
Describe why do you think it is needed
Bunker buster is a mid-game favourite item to help against turtling and is a very good specialized weapon against defenses when introduced. However, late game fortresses are far more resistant to it and the attacks can be countered a lot more easily.
The following upgrade path seeks to keep such an hyper specialized weapon relevant:
Upgrade 1: Twin bunker buster
A simple upgrade that adds a 2nd shot (similar to Lancer). Double the firepower, higher cost, higher weight.
Upgrade 2: Firebolt rocket
Unlocked after incendiary mortar or howitzer, it basically works as a larger bunker buster that adds incendiary damage to a very small area. I'd see it as a larger twin bunker buster, so another firepower tradeoff VS cost and weight.
What do you guys think?
The text was updated successfully, but these errors were encountered: