|
I realize right now that the Colossus is low on the priority list for both Blizzard and community. The impetus at Blizzard is to fix the Disruptor, the impetus for many of us is to substitute the Reaver and scrap the Disruptor. I just thought of something that might solve the current issues with the Colossus and make it a more fun unit to play with for all parties concerned.
As I see it, the main issue with the HotS Colossus is that it's a death-ball unit. Its range and its ability to walk over units, combined with the anti-air vulnerability, force it to sit in the middle of the stalker ball, laser-ing the enemy to death. LotV attempts to address this by nerfing the maximum range and damage of the Colossus. However, the effect is that Protoss' main source of continuous, reliable AoE damage is removed, which proves especially problematic in the late game.
Suggested Upgrade at Robo Bay: Hadronic (or whatever name Blizzard pleases) Protection Field
The Colossus gains an energy field that reduces any incoming attack damage from over 5 range by 50%. The field deactivates if any massive unit (friend or foe) enters the field, i.e. crosses within 5 range of the Colossus.
This upgrade has a passive effect that allows the Colossus to be more aggressive on the battlefield as long as it maintains the 5 range threshold. This could introduce a cool positioning battle as the Colossus edges up as far as it can to fire, while enemy Vikings, Corruptors, Marauders, etc. try to figure out when is a good time to jump within the 5 range and maximize their damage output against the Colossus. (Note that such units are not completely shut down; it simply takes longer for them to maintain poke range.) This upgrade also gives the Colossus a more viable escape option - most chasing units will have to run farther to enter the HPF and effectively snipe the Colossus.
The massive unit trigger to disrupt the field adds a further positioning element and limits the effectiveness of multiple Colossi. Colossi must be separated in order to maintain the HPF; unless the player is relying on the sheer damage output, there can be no more than two or three Colossi within the army. Archons would also have to maintain distance from the Colossus once the fight starts, forcing the deathball to further spread out. Opposing players can exploit the HPF if they can force the army to retreat into itself, i.e. balling up. The massive trigger also creates a list of hard-counter units that could charge the HPF to break it: Archons, Ultralisks, Thors (in Medivac). Compared to the Colossus' previous hard counters, this list would feel less gimmicky because the units are expensive and clunky on their own.
Because this upgrade favors using fewer, more spread out Colossi in an army, I would suggest buffing the damage (not the range) to compensate. I realize that my suggestion may appear gimmicky as it steers away from traditional unit design. However, I believe it is interesting enough and provides enough strategic thought on both sides that it would be worth testing in the LotV beta.
Thanks everyone for reading! Post thoughts, questions, suggestions below!
|
I would rather if Colossus left burning AOE lines (the same as they fire) that would damage units walking over for a few seconds. This way Colossus would maintain it's reliable AOE and you would be encouraged to have one or 2 in the army, because more would stack the burn and ofcourse the damage shouldn't stack so it would be no use.
For this to work, the impact damage would have to be lowered in favor of the damage over time burn.Would also encourage micro on the opponent's side - not standing in the lines.
It's not that I don't like your suggestion, but I'm afraid if would create clutter with a new type of forcefield or visual ring.
|
On July 25 2015 04:57 _indigo_ wrote:
I would rather if Colossus left burning AOE lines (the same as they fire) that would damage units walking over for a few seconds. This way Colossus would maintain it's reliable AOE and you would be encouraged to have one or 2 in the army, because more would stack the burn and ofcourse the damage shouldn't stack so it would be no use.
For this to work, the impact damage would have to be lowered in favor of the damage over time burn.Would also encourage micro on the opponent's side - not standing in the lines.
It's not that I don't like your suggestion, but I'm afraid if would create clutter with a new type of forcefield or visual ring.
I would be open to this suggestion as well; however I think the main issue is that it would begin to overlap with Psi Storm, which kinda does the same thing (AoE over time in an area, non-stacking).
I can also see the point about visual clutter. I would hope the clutter won't be too bad if only 2 or 3 Colossi take the field at a time. I imagine it would be like the Shield Generator in Star Wars V - strong on the outside, can be broken by heavy artillery charging inside.
|
On July 25 2015 04:47 starimk wrote:
I realize right now that the Colossus is low on the priority list for both Blizzard and community. The impetus at Blizzard is to fix the Disruptor, the impetus for many of us is to substitute the Reaver and scrap the Disruptor.
Whoa, speak for yourself. After trying out that Reaver mod, I most certainly do not want it back as a replacement for the Disruptor or the Colossus.
This is a pretty neat idea though. However, I feel that its "reliable, consistent splash damage" attack should be re-examined on a more fundamental level. One of the more interesting suggestions I've seen was to change the Colossus' attack to be similar to the OneGoal Void Ray's attack, seen here: + Show Spoiler +
|
On July 25 2015 05:30 Pontius Pirate wrote:Show nested quote +On July 25 2015 04:47 starimk wrote:
I realize right now that the Colossus is low on the priority list for both Blizzard and community. The impetus at Blizzard is to fix the Disruptor, the impetus for many of us is to substitute the Reaver and scrap the Disruptor. Whoa, speak for yourself. After trying out that Reaver mod, I most certainly do not want it back as a replacement for the Disruptor or the Colossus.
Whoa, what Reaver mod?
|
On July 25 2015 05:45 AmicusVenti wrote:Show nested quote +On July 25 2015 05:30 Pontius Pirate wrote:On July 25 2015 04:47 starimk wrote:
I realize right now that the Colossus is low on the priority list for both Blizzard and community. The impetus at Blizzard is to fix the Disruptor, the impetus for many of us is to substitute the Reaver and scrap the Disruptor. Whoa, speak for yourself. After trying out that Reaver mod, I most certainly do not want it back as a replacement for the Disruptor or the Colossus. Whoa, what Reaver mod?
Starbow probably, but trust me, he does not understand anything, Reaver is what Protoss needs.
|
On July 25 2015 05:52 cSc.Dav1oN wrote:Show nested quote +On July 25 2015 05:45 AmicusVenti wrote:On July 25 2015 05:30 Pontius Pirate wrote:On July 25 2015 04:47 starimk wrote:
I realize right now that the Colossus is low on the priority list for both Blizzard and community. The impetus at Blizzard is to fix the Disruptor, the impetus for many of us is to substitute the Reaver and scrap the Disruptor. Whoa, speak for yourself. After trying out that Reaver mod, I most certainly do not want it back as a replacement for the Disruptor or the Colossus. Whoa, what Reaver mod? Starbow probably, but trust me, he does not understand anything, Reaver is what Protoss needs.
Nah, protoss needs super fast storm drops. And super bad pathing AI.
|
On July 25 2015 05:45 AmicusVenti wrote:Show nested quote +On July 25 2015 05:30 Pontius Pirate wrote:On July 25 2015 04:47 starimk wrote:
I realize right now that the Colossus is low on the priority list for both Blizzard and community. The impetus at Blizzard is to fix the Disruptor, the impetus for many of us is to substitute the Reaver and scrap the Disruptor. Whoa, speak for yourself. After trying out that Reaver mod, I most certainly do not want it back as a replacement for the Disruptor or the Colossus. Whoa, what Reaver mod?
Yeah, could Pontius or anyone else post a link to further information about this Reaver mod? I've looked for it myself and came up dry.
Re Pontius: When I say "many of us", I'm referring to the high frequency of posts on the battle.net forums as well as several posts on the Team Liquid threads.
|
On July 25 2015 06:56 starimk wrote:Show nested quote +On July 25 2015 05:45 AmicusVenti wrote:On July 25 2015 05:30 Pontius Pirate wrote:On July 25 2015 04:47 starimk wrote:
I realize right now that the Colossus is low on the priority list for both Blizzard and community. The impetus at Blizzard is to fix the Disruptor, the impetus for many of us is to substitute the Reaver and scrap the Disruptor. Whoa, speak for yourself. After trying out that Reaver mod, I most certainly do not want it back as a replacement for the Disruptor or the Colossus. Whoa, what Reaver mod? Yeah, could Pontius or anyone else post a link to further information about this Reaver mod? I've looked for it myself and came up dry. Re Pontius: When I say "many of us", I'm referring to the high frequency of posts on the battle.net forums as well as several posts on the Team Liquid threads.
There's also a lot of people saying they prefer the disruptor over the reaver. Myself included.
A scarab that you can micro sounds way more interesting than a retarded scarab that doesn't go in the right direction.
|
I'll be happy to get rid of the collosus.
It's one of the reasons why Protoss is so boring to watch as a spectator. It instantly kills most things when stacked, yet takes no micro.
|
On July 25 2015 08:35 [UoN]Sentinel wrote:Show nested quote +On July 25 2015 06:56 starimk wrote:On July 25 2015 05:45 AmicusVenti wrote:On July 25 2015 05:30 Pontius Pirate wrote:On July 25 2015 04:47 starimk wrote:
I realize right now that the Colossus is low on the priority list for both Blizzard and community. The impetus at Blizzard is to fix the Disruptor, the impetus for many of us is to substitute the Reaver and scrap the Disruptor. Whoa, speak for yourself. After trying out that Reaver mod, I most certainly do not want it back as a replacement for the Disruptor or the Colossus. Whoa, what Reaver mod? Yeah, could Pontius or anyone else post a link to further information about this Reaver mod? I've looked for it myself and came up dry. Re Pontius: When I say "many of us", I'm referring to the high frequency of posts on the battle.net forums as well as several posts on the Team Liquid threads. There's also a lot of people saying they prefer the disruptor over the reaver. Myself included. A scarab that you can micro sounds way more interesting than a retarded scarab that doesn't go in the right direction.
My god, I thought I was the only one who felt icky about posts like this:
3) Starbow proved the Reaver can fit into Sc2
You can't deny this. Starbow is still superior compared to Starcraft 2 where deathballs do not exist anymore. They did not tweak the Reaver at all, comming to my point: Why does a untweaked Reaver work in Starbow but a tweaked Reaver does not work in Starcraft 2 ?
Sure Starbow is different but it still used the Starcraft 2 mechanics. If the Reaver work in Starbow why not TRY it out in Starcraft 2.
Source: http://us.battle.net/sc2/en/forum/topic/18300815152
|
You're looking at the wrong part of the problem. Colossus power is a side effect of the design of weak core units that relies heavily on force fields or imba damage units like colossus. There is no meaning in doing anything to the colossus if we're not redesigning gateway units inluding sentries.
|
On July 25 2015 08:35 [UoN]Sentinel wrote:Show nested quote +On July 25 2015 06:56 starimk wrote:On July 25 2015 05:45 AmicusVenti wrote:On July 25 2015 05:30 Pontius Pirate wrote:On July 25 2015 04:47 starimk wrote:
I realize right now that the Colossus is low on the priority list for both Blizzard and community. The impetus at Blizzard is to fix the Disruptor, the impetus for many of us is to substitute the Reaver and scrap the Disruptor. Whoa, speak for yourself. After trying out that Reaver mod, I most certainly do not want it back as a replacement for the Disruptor or the Colossus. Whoa, what Reaver mod? Yeah, could Pontius or anyone else post a link to further information about this Reaver mod? I've looked for it myself and came up dry. Re Pontius: When I say "many of us", I'm referring to the high frequency of posts on the battle.net forums as well as several posts on the Team Liquid threads. There's also a lot of people saying they prefer the disruptor over the reaver. Myself included. A scarab that you can micro sounds way more interesting than a retarded scarab that doesn't go in the right direction.
A scarab explodes at the end of its journey, I guess that's what the disruptor also does in your mind? Stop trying to equate a disruptor to a scarab, they're nothing alike.
Reavers are more interesting because they're just a solid unit with two core weaknesses, their mobility and fragility. Using speed shuttles solves both problems (whilst relying on skill) and creates another interesting dynamic especially in ZvP where you would have to dodge scourges.
The disruptor so far has required invulnerability, speed boosts and extended warp prism pick-up to walk a thin line between being OP or completely useless. What an amazingly designed unit /sarcasm.
|
On July 25 2015 10:21 B-royal wrote:Show nested quote +On July 25 2015 08:35 [UoN]Sentinel wrote:On July 25 2015 06:56 starimk wrote:On July 25 2015 05:45 AmicusVenti wrote:On July 25 2015 05:30 Pontius Pirate wrote:On July 25 2015 04:47 starimk wrote:
I realize right now that the Colossus is low on the priority list for both Blizzard and community. The impetus at Blizzard is to fix the Disruptor, the impetus for many of us is to substitute the Reaver and scrap the Disruptor. Whoa, speak for yourself. After trying out that Reaver mod, I most certainly do not want it back as a replacement for the Disruptor or the Colossus. Whoa, what Reaver mod? Yeah, could Pontius or anyone else post a link to further information about this Reaver mod? I've looked for it myself and came up dry. Re Pontius: When I say "many of us", I'm referring to the high frequency of posts on the battle.net forums as well as several posts on the Team Liquid threads. There's also a lot of people saying they prefer the disruptor over the reaver. Myself included. A scarab that you can micro sounds way more interesting than a retarded scarab that doesn't go in the right direction. A scarab explodes at the end of its journey, I guess that's what the disruptor also does in your mind? Stop trying to equate a disruptor to a scarab, they're nothing alike. Reavers are more interesting because they're just a solid unit with two core weaknesses, their mobility and fragility. Using speed shuttles solves both problems (whilst relying on skill) and creates another interesting dynamic especially in ZvP where you would have to dodge scourges. The disruptor so far has required invulnerability, speed boosts and extended warp prism pick-up to walk a thin line between being OP or completely useless. What an amazingly designed unit /sarcasm.
A scarab's weakness is that you're at the mercy of its shit AI. The projectile is also invulnerable, whereas the Disruptor is looking like it's going to get some sort of shield/speed buff to retreat to safety but make it killable. A scarab is a cheaper, suicidal disruptor.
I don't want to have to have my harass go wrong not because I misclicked or the enemy caught me in a trap, but because the conditions are the correct ones for the computer to turn on me. Or have a unit that's either too destructive (with fixed AI) or nerfed into oblivion to make it useless.
|
Oh Gosh, I loved the idea lol, passive ability, anti-deathballing with other units of same type... it is incredible interesting, and plays a lot with positioning the units.
But it is too good to be a possible thing Blizz is going to do hahaha, so sad tho...
|
Replace with Reaver. There, fixed.
|
On July 25 2015 09:41 i)awn wrote:
You're looking at the wrong part of the problem. Colossus power is a side effect of the design of weak core units that relies heavily on force fields or imba damage units like colossus. There is no meaning in doing anything to the colossus if we're not redesigning gateway units inluding sentries.
Perhaps. I think it's been made clear that sentries, at least, aren't up for a redesign any time soon. And I think whether or not Protoss armies are reliant on damage-dealers like the Colossus, my suggested changes would make the unit more interesting to play with and against. Even if the Protoss core does remain unchanged, would it not at least be more fun to see a Protoss deathball where the Colossi actively have to spread out?
It's true that a Colossus rework likely won't solve all the current issues with Protoss gameplay. My post was not intended to be a holistic fix to Protoss; it was intended to present the brainchild of a few hours of theorycrafting.
On July 25 2015 11:27 Sogetsu wrote:
Oh Gosh, I loved the idea lol, passive ability, anti-deathballing with other units of same type... it is incredible interesting, and plays a lot with positioning the units.
But it is too good to be a possible thing Blizz is going to do hahaha, so sad tho...
Here's hoping! 
|
edit: nevermind
Anyways I dont really like it. Too complicated and I dont think it really addresses the core problems with colossus.
|
On July 25 2015 16:26 alexanderzero wrote:
edit: nevermind
Anyways I dont really like it. Too complicated and I dont think it really addresses the core problems with colossus.
Sure it's complicated, but I feel that more simple suggestions may not cut it anymore. With the way unit formation and army engagements happen in SC2, I don't think we can expect effective unit design to be as simple as it was in BW. I did also put a lot of time to 1) make sure it was a passive ability that relies on positioning, and 2) encode more interesting counter-play than what it has currently.
Another thing is, of all the different abilities in this game, how many have an anti-stacking effect? We've had stacking abilities (Parasitic Bomb) and non-stacking abilities (Psi Storm), but I can't think of an ability that actively punishes you for clumping units or target areas.
|
Maybe instead of cancelling the effect when a friendly massive unit entering the field（which I think will be really difficult to avoid when you have the typical archon/colossus composition) just increase colossus's collision size when the skill is active
the effect would be like positioning FFs around colossus thus forcing the army to spread out.
Edit: this means this skill will simply increase colossus's survivability at the cost of de-deathballing the entire protoss army and causing trouble with units pathing. Potentially make it a interesting choice for Protoss player to decide whether to active it or not.
|
|
|
|
|
|
EPT
