Roach/Colossus Glitch - Page 5
Forum Index > SC2 General |
ArvickHero
10387 Posts
| ||
Blisse
Canada3710 Posts
On August 08 2010 10:24 Half wrote: Yes you don't need to utilize this at all. Like, when they see the shadows cast by burrowed roaches in front of their choke, and they try to move their collosus out, they be completely baffled and stare at their screen in complete awe for twenty minutes, allowing you to score an easy win. They won't move their collosus around it, or build observers, or anything. A special few may even get seizures from intense bafflement. Thus, we have to remove this trick. Just like we removed Fazing and Burrowed movement. All micro tricks have to be intentionally design lols. What do you think this is 1998?. And don't worry about lack of micro tactics, they'll develop over time you noob. Starcraft 2 is the best. Yes, because calling me a noob and using sarcasm adds to your argument. See what I did there? 'What do you think this is 1998?' What kind of attitude is that. I thought we would have a nice argument, but it seems like you would rather insult my intelligence than provide some discussion. Obviously I have not said anything close to removing Fazing nor Burrowed Casting, but only that this should be. How does that represent the attitude of someone playing Starcraft in 1998. You just sound ridiculous. Burrowed units don't make shadows unless their moving? And I actually wonder how many players will stare at their screen in awe trying to figure out what is going on when their Colossi starts glitching out because Blizzard didn't do their pathing properly? Quite a bit I believe. It's not everyone's instinctive reaction to get an Observer out to scout it. And as you see in the videos, Colossi don't walk around it. They walk into it and get stuck. If you have burrow move, you could burrow move around it, and it would get stuck their forever. Do you realize how important Colossi are in many match ups? Do you realize that if a Protoss is unable to get them out, how much of a problem that causes? Burial Ground, Kulas Ravine, Abyss. All three have small chokes that you could abuse by placing several Roaches outside. Now no Colossi, except for maybe on Kulas, can enter or leave by the cliff mechanic. None of the examples you have given have in any way proven this is not a glitch. All you have proven is that this can be used in some ways. I don't see anything to prove this is not a glitch. Again, I will say this. What if every unit, or maybe other units, like Siege Tanks, or Zerglings were unable to move over burrowed Roaches and Infestors. Would it still be considered a neat trick? Fazing, is again, part of the Void Ray design, not a bug or a glitch. It was intentional, but no one realized it. I'm not sure about Burrowed casting, but it becomes pretty obvious that it is Infestor handiwork once you see the spine sticking out of the ground. Only problem is that you need detection, and this is ridiculously difficult and unnecessary in a fight. I'm sure that in Starcraft, there were many glitches that people found, but Blizzard decided that it shouldn't exist. Anyways, Blizzard's decision is final, and if they decide to keep this, I will let it go, but until they make that decision, I will not accept this as a micro trick. | ||
Synwave
United States2803 Posts
| ||
TitleRug
United States651 Posts
On August 08 2010 11:02 ArvickHero wrote: Why not keep it in for now, it's not like its broken or anything. Keeps Protoss honest and force him to have an obs w/ his army if he's going for a Collosus-centric play. Exactly. Now Protoss actually have to do something besides cast forcefields and spam zealots, colossus, sentries, and stalkers. Now they have to keep their observers in the right place, and prevent them from getting sniped. | ||
Sanguinarius
United States3427 Posts
| ||
asdfjh
Canada230 Posts
On August 08 2010 11:05 vica wrote: Yes, because calling me a noob and using sarcasm adds to your argument. See what I did there? 'What do you think this is 1998?' What kind of attitude is that. I thought we would have a nice argument, but it seems like you would rather insult my intelligence than provide some discussion. Obviously I have not said anything close to removing Fazing nor Burrowed Casting, but only that this should be. How does that represent the attitude of someone playing Starcraft in 1998. You just sound ridiculous. Burrowed units don't make shadows unless their moving? And I actually wonder how many players will stare at their screen in awe trying to figure out what is going on when their Colossi starts glitching out because Blizzard didn't do their pathing properly? Quite a bit I believe. It's not everyone's instinctive reaction to get an Observer out to scout it. And as you see in the videos, Colossi don't walk around it. They walk into it and get stuck. If you have burrow move, you could burrow move around it, and it would get stuck their forever. Do you realize how important Colossi are in many match ups? Do you realize that if a Protoss is unable to get them out, how much of a problem that causes? Burial Ground, Kulas Ravine, Abyss. All three have small chokes that you could abuse by placing several Roaches outside. Now no Colossi, except for maybe on Kulas, can enter or leave by the cliff mechanic. None of the examples you have given have in any way proven this is not a glitch. All you have proven is that this can be used in some ways. I don't see anything to prove this is not a glitch. Again, I will say this. What if every unit, or maybe other units, like Siege Tanks, or Zerglings were unable to move over burrowed Roaches and Infestors. Would it still be considered a neat trick? Fazing, is again, part of the Void Ray design, not a bug or a glitch. It was intentional, but no one realized it. I'm not sure about Burrowed casting, but it becomes pretty obvious that it is Infestor handiwork once you see the spine sticking out of the ground. Only problem is that you need detection, and this is ridiculously difficult and unnecessary in a fight. I'm sure that in Starcraft, there were many glitches that people found, but Blizzard decided that it shouldn't exist. Anyways, Blizzard's decision is final, and if they decide to keep this, I will let it go, but until they make that decision, I will not accept this as a micro trick. just consider this the zerg equivalent of DTs or cloaked banshees - they severely punish the opponent if they dont have any observers. burrow and claws such against anything else due to the cost and time of both upgrades. chokes also favor protoss since they can easily storm or FF, this should help even it up. as for other units not getting stuck, keep in mind that colossi are not tanks, lings, nor any other unit. they can also move over other ground units and cliffs. using burrowed roaches to stop colossi also require skill, unlike what some may believe because keep in mind that for every roach burrowed you have one less fighting unit, and precise positioning is required. you can't just burrow a roach anywhere on the map and instantly stop all colossi or anything like that. you have to actually move the roaches in a way that they block the colossi while also making sure you have enough units left over to kill whatever the protoss has. finally, there is no clear distinction between glitch and trick but the general consensus seems to be that if blizzard has not officially announced whether something was intended or not, it would be judged by its effects. if the move in question was game breaking, it would be a glitch. otherwise, a trick. i personally think that it's not game breaking enough to be called a glitch, but frankly, it doesn't matter what anyone ASSUMES. why don't we just wait a while for the trick to be used, and then lets judge whether or not its broken? | ||
Blisse
Canada3710 Posts
On August 08 2010 11:48 asdfjh wrote: just consider this the zerg equivalent of DTs or cloaked banshees - they severely punish the opponent if they dont have any observers. burrow and claws such against anything else due to the cost and time of both upgrades. chokes also favor protoss since they can easily storm or FF, this should help even it up. as for other units not getting stuck, keep in mind that colossi are not tanks, lings, nor any other unit. they can also move over other ground units and cliffs. using burrowed roaches to stop colossi also require skill, unlike what some may believe because keep in mind that for every roach burrowed you have one less fighting unit, and precise positioning is required. you can't just burrow a roach anywhere on the map and instantly stop all colossi or anything like that. you have to actually move the roaches in a way that they block the colossi while also making sure you have enough units left over to kill whatever the protoss has. finally, there is no clear distinction between glitch and trick but the general consensus seems to be that if blizzard has not officially announced whether something was intended or not, it would be judged by its effects. if the move in question was game breaking, it would be a glitch. otherwise, a trick. i personally think that it's not game breaking enough to be called a glitch, but frankly, it doesn't matter what anyone ASSUMES. why don't we just wait a while for the trick to be used, and then lets judge whether or not its broken? I hadn't thought about that. Yes, it requires some level skill to get it in position. I just dislike how in order to achieve this level of harass, we get a specific unit, whose sole purpose is to block this other specific unit. And on some maps, you can actually block all Colossi. It's more like the Colossi hit an invisible wall, and that other burrowed units block pathing. I believe that just because a 'trick' is nice, has many possibilities, and could be used to great effect, doesn't mean it should exist. | ||
intrigue
Washington, D.C9931 Posts
i was waiting eagerly for threads like this one! i renamed your thread, because i suspect that this is more a straight up error instead of a unintended game-enhancing nuance. | ||
SnakeChomp
Canada125 Posts
On August 08 2010 11:05 vica wrote: Fazing, is again, part of the Void Ray design, not a bug or a glitch. It was intentional, but no one realized it. Since when did Blizzard say it was intentional? They specifically said they were going to fix it. My take on fazing is that it's an unintended side effect of the implementation of their weapon; namely the fact that it does damage in ticks and also immediately when it begins to fire. The person who implemented the weapon simply neglected to account for the fact that rapidly switching targets can bypass the natural delay of each tick of damage. | ||
Blisse
Canada3710 Posts
On August 08 2010 12:25 SnakeChomp wrote: Since when did Blizzard say it was intentional? They specifically said they were going to fix it. My take on fazing is that it's an unintended side effect of the implementation of their weapon; namely the fact that it does damage in ticks and also immediately when it begins to fire. The person who implemented the weapon simply neglected to account for the fact that rapidly switching targets can bypass the natural delay of each tick of damage. I thought the design was intentional when they made it so that it doesn't lose as much of its charge when switching from building to building and they didn't think of quickly switching targets. I never saw where they said they were going to fix it though, so I may be mistaken. | ||
TheYango
United States47024 Posts
Not terribly useful all the time, but maybe it'll be a little useful like obs over turret in BW. | ||
Railxp
Hong Kong1313 Posts
| ||
xbayrockx
Australia4 Posts
why do people make guides to exploit bugs? do they not see how this is a horrible idea. You are a moron. Your statement is equivalent to an employee holding knowledge of an exploitable bug in windows but not publicly announcing it - keeping it well hidden, however still exploitable and hence multiple times more dangerous to it's users. | ||
RageOverdose
United States690 Posts
Based on that alone I'd say it doesn't need to be patched out. For every situation where it seems OP, there may be one where it doesn't and it's kind of cool, and funny. | ||
kzn
United States1218 Posts
And I'm absolutely sure muta stacking and similar "tricks" in scbw were not intended. That is all. | ||
sLiniss
United States849 Posts
| ||
emperorchampion
Canada9495 Posts
| ||
virgozero
Canada412 Posts
On August 08 2010 09:15 Qikz wrote: It's a glitch as it wasn't in the game before last patch. so your assuming blizz tells us everything with every patch >.> | ||
Arnu
Canada96 Posts
If the zerg player wasnt paying full attention to the protoss force while it was moving out the zerg player could lose a lot of roaches before he has time to react. If this were to happen to me i'd just sit right there until i got an obs with my army if i didnt already. | ||
Synwave
United States2803 Posts
On August 08 2010 12:05 intrigue wrote: nice post =] i was waiting eagerly for threads like this one! i renamed your thread, because i suspect that this is more a straight up error instead of a unintended game-enhancing nuance. Bless you for the crap that people spew "working as intended" when anything but what they want works. Maybe it will be patched, maybe it won't. But working as intended posts really need the fricken hammer. | ||
| ||