|
On February 07 2012 18:57 Afterstar wrote: If blizzard removes this, then they should fix the bug with the snipe key.
The problem: After you select your ghosts,if you Hold "R" (Pressed) and start spamming left click immediately on one or more targets, only one ghost will get the command to snipe once,the system will deselect your group and select the enemy target.
Now do the following, select your ghosts, Hold "R"(Pressed), wait 1.5seconds with R pressed and then spam left click on multiple targets. The snipes will work correctly for all ghosts.
This is a bug,that forces you to have to wait 1.5seconds before being able to snipe fast or forces you having to hold SHIFT+R,where you are queueing commands.This method is risky because if one of the targets gets out of range your ghosts will try to reach it, also sometimes ghosts will fire normal shots,even further delaying your sniping.
If you Hold E(Pressed) for EMP and spam left click immediately,it will work correctly without the need of SHIFT or the 1.5second wait.Same for Infested Terrans,Fungal Growth,Storm. Why is Snipe punished,having to wait 1.5seconds before being able to snipe fast?
I don't see how it's a bug since every "one target" spell behave like this. Feedback and queen's heal just do exactly the same thing.
In fact, AoE spells do the same thing. But with these spell's, you don't "click" on a particular unit so you avoid this problem.
|
On February 07 2012 19:07 Liquid`TLO wrote:+ Show Spoiler +On February 07 2012 18:57 Afterstar wrote: If blizzard removes this, then they should fix the bug with the snipe key.
The problem: After you select your ghosts,if you Hold "R" (Pressed) and start spamming left click immediately on one or more targets, only one ghost will get the command to snipe once,the system will deselect your group and select the enemy target.
Now do the following, select your ghosts, Hold "R"(Pressed), wait 1.5seconds with R pressed and then spam left click on multiple targets. The snipes will work correctly for all ghosts.
This is a bug,that forces you to have to wait 1.5seconds before being able to snipe fast or forces you having to hold SHIFT+R,where you are queueing commands.This method is risky because if one of the targets gets out of range your ghosts will try to reach it, also sometimes ghosts will fire normal shots,even further delaying your sniping.
If you Hold E(Pressed) for EMP and spam left click immediately,it will work correctly without the need of SHIFT or the 1.5second wait.Same for Infested Terrans,Fungal Growth,Storm. Why is Snipe punished,having to wait 1.5seconds before being able to snipe fast? I don't think there is a problem with ghosts considering how strong ghosts are in the game. I haven`t met a progamer who complained about snipe being too bad to be honest. I admit snipe behaves a bit weird but you can master it nonetheless.
Just because no progamer complained before, that doesn't mean there isn't a problem or a potential bug with this. At the moment it feels very clunky. I hope blizzard can give us an answer as to why you have to wait 1.5seconds after Holding "R"(Snipe default key),before being able to snipe properly with multiple ghosts,when no other spell has this "limitation"(bug).
On February 07 2012 19:25 Magus.421 wrote:+ Show Spoiler +On February 07 2012 18:57 Afterstar wrote: If blizzard removes this, then they should fix the bug with the snipe key.
The problem: After you select your ghosts,if you Hold "R" (Pressed) and start spamming left click immediately on one or more targets, only one ghost will get the command to snipe once,the system will deselect your group and select the enemy target.
Now do the following, select your ghosts, Hold "R"(Pressed), wait 1.5seconds with R pressed and then spam left click on multiple targets. The snipes will work correctly for all ghosts.
This is a bug,that forces you to have to wait 1.5seconds before being able to snipe fast or forces you having to hold SHIFT+R,where you are queueing commands.This method is risky because if one of the targets gets out of range your ghosts will try to reach it, also sometimes ghosts will fire normal shots,even further delaying your sniping.
If you Hold E(Pressed) for EMP and spam left click immediately,it will work correctly without the need of SHIFT or the 1.5second wait.Same for Infested Terrans,Fungal Growth,Storm. Why is Snipe punished,having to wait 1.5seconds before being able to snipe fast? I don't see how it's a bug since every "one target" spell behave like this. Feedback and queen's heal just do exactly the same thing. In fact, AoE spells do the same thing. But with these spell's, you don't "click" on a particular unit so you avoid this problem. As you said AOE spells,(in fact any spell with no target requirement) do the same thing but you don't click on a unit and therefore there is no need to Hold the spell key and THEN wait 1.5seconds before start snipe spamming(Hold R + left click spam method). Feedback you only need to use it once per target and Queen's heal doesn't require crazy spamming to be effective,so the only spell affected is the Snipe.
|
On February 07 2012 19:26 Afterstar wrote:I hope blizzard can give us an answer as to why you have to wait 1.5seconds after Holding "R"(Snipe default key),before being able to snipe properly with multiple ghosts,when no other spell has this "limitation"(bug).
Because while you are "holding" a key, you use the "repeat key" function of your keyboard. When you type a text, just hold a key and you'll see the same behavior. You hold the key, and you must wait a little moment before your keyboard start to repeat the key. This "timer" can be modified in Windows keyboard settings (the minimum you can set is 0.5 real second).
In SC2, we use this "repeat key" for spells spamming. But it's a keyboard function, not SC2 function.
|
On February 07 2012 19:30 Magus.421 wrote:Show nested quote +On February 07 2012 19:26 Afterstar wrote:I hope blizzard can give us an answer as to why you have to wait 1.5seconds after Holding "R"(Snipe default key),before being able to snipe properly with multiple ghosts,when no other spell has this "limitation"(bug). Because while you are "holding" a key, you use the "repeat key" function of your keyboard. When you type a text, just hold a key and you'll see the same behavior. You hold the key, and you must wait a little moment before your keyboard start to repeat the key. This "timer" can be modified in Windows keyboard settings (the minimum you can set is 0.5 real second). In SC2, we use this "repeat key" for spells spamming. But it's a keyboard function, not SC2 function.
You sir may have found the problem/solution.  But why when you *hold* a key to queue up units or create zerg units,it does it immediately with no delay at all , or how about AOE spells?
|
On February 07 2012 19:36 Afterstar wrote:Show nested quote +On February 07 2012 19:30 Magus.421 wrote:On February 07 2012 19:26 Afterstar wrote:I hope blizzard can give us an answer as to why you have to wait 1.5seconds after Holding "R"(Snipe default key),before being able to snipe properly with multiple ghosts,when no other spell has this "limitation"(bug). Because while you are "holding" a key, you use the "repeat key" function of your keyboard. When you type a text, just hold a key and you'll see the same behavior. You hold the key, and you must wait a little moment before your keyboard start to repeat the key. This "timer" can be modified in Windows keyboard settings (the minimum you can set is 0.5 real second). In SC2, we use this "repeat key" for spells spamming. But it's a keyboard function, not SC2 function. You sir may have found the problem/solution.  But why when you spam a key to queue up units or create zerg units,it does it immediately with no delay at all , or how about AOE spells?
It does not do it immediatly. You create 1 drone then 1 sec later you create drones with rapid speed. If you set keyboard delay repeat to like 5ms you will almost use all your larva almost immediately, so adjusting repeat delay is a dobble edge sword.
EDIT: well ofc if you spam, you are not holding down the key, so thats why it does it immediately.
|
Thanks for the quick answers I appreciate it, now back to the "Snipe/Infested Terran-machinegun" topic.
|
On February 07 2012 19:44 RoyAlex wrote: It does not do it immediatly. You create 1 drone then 1 sec later you create drones with rapid speed. If you set keyboard delay repeat to like 5ms you will almost use all your larva almost immediately, so adjusting repeat delay is a dobble edge sword
My bad. 0.5 =/= 5ms. 0.5 is 0.5s ^^ That's the minimum value allowed by Windows. But maybe program or driver can override this.
|
|
On February 07 2012 17:23 PH wrote:Show nested quote +On February 07 2012 14:01 Keone wrote:On February 06 2012 15:23 Azzur wrote: For those that are questioning the validity / legality of this - I'm 100% sure that this would be allowed in the GSL - players are allowed to install their own mouse drivers and rebind keys as long as it's 1-to-1 key bind. For tournaments such as MLG, it "should" be allowed but time constraints may not allow for it.
For example, I'm using a Microsoft Intellimouse and the built-in drivers allow me to rebind keys. In World of Warcraft, doing such things are very common that gaming mice have been released to have many buttons on a mouse. Question, doesn't this count as NOT 1-to-1 key binding, and thus, illegal? Because this would technically be Many-to-1, because the left mouse button is still the Mouse1, and if you bind another key to Mouse1, that counts as Many-to-1. Just an honest question. No. You're simply mapping more than one key to one particular action. You're not mapping multiple actions to one key, which would be problematic. It'd be like having multiple keys build a probe, which isn't really bad. This is bad only 'cause the mouse scroll wheel can be triggered so quickly... I understand and understood before that 1-to-Many is bad; that wasn't part of my original question. My question is: is Many-to-1 legal? Your example with multiple keys mapped to a probe would count as a Many-to-1; is that legal within GSL rules? This is because someone originally said only 1-to-1 mappings are legal in GSL.
|
On February 07 2012 19:26 Afterstar wrote:Show nested quote +On February 07 2012 19:07 Liquid`TLO wrote:+ Show Spoiler +On February 07 2012 18:57 Afterstar wrote: If blizzard removes this, then they should fix the bug with the snipe key.
The problem: After you select your ghosts,if you Hold "R" (Pressed) and start spamming left click immediately on one or more targets, only one ghost will get the command to snipe once,the system will deselect your group and select the enemy target.
Now do the following, select your ghosts, Hold "R"(Pressed), wait 1.5seconds with R pressed and then spam left click on multiple targets. The snipes will work correctly for all ghosts.
This is a bug,that forces you to have to wait 1.5seconds before being able to snipe fast or forces you having to hold SHIFT+R,where you are queueing commands.This method is risky because if one of the targets gets out of range your ghosts will try to reach it, also sometimes ghosts will fire normal shots,even further delaying your sniping.
If you Hold E(Pressed) for EMP and spam left click immediately,it will work correctly without the need of SHIFT or the 1.5second wait.Same for Infested Terrans,Fungal Growth,Storm. Why is Snipe punished,having to wait 1.5seconds before being able to snipe fast? I don't think there is a problem with ghosts considering how strong ghosts are in the game. I haven`t met a progamer who complained about snipe being too bad to be honest. I admit snipe behaves a bit weird but you can master it nonetheless. Just because no progamer complained before, that doesn't mean there isn't a problem or a potential bug with this. At the moment it feels very clunky. I hope blizzard can give us an answer as to why you have to wait 1.5seconds after Holding "R"(Snipe default key),before being able to snipe properly with multiple ghosts,when no other spell has this "limitation"(bug). Show nested quote +On February 07 2012 19:25 Magus.421 wrote:+ Show Spoiler +On February 07 2012 18:57 Afterstar wrote: If blizzard removes this, then they should fix the bug with the snipe key.
The problem: After you select your ghosts,if you Hold "R" (Pressed) and start spamming left click immediately on one or more targets, only one ghost will get the command to snipe once,the system will deselect your group and select the enemy target.
Now do the following, select your ghosts, Hold "R"(Pressed), wait 1.5seconds with R pressed and then spam left click on multiple targets. The snipes will work correctly for all ghosts.
This is a bug,that forces you to have to wait 1.5seconds before being able to snipe fast or forces you having to hold SHIFT+R,where you are queueing commands.This method is risky because if one of the targets gets out of range your ghosts will try to reach it, also sometimes ghosts will fire normal shots,even further delaying your sniping.
If you Hold E(Pressed) for EMP and spam left click immediately,it will work correctly without the need of SHIFT or the 1.5second wait.Same for Infested Terrans,Fungal Growth,Storm. Why is Snipe punished,having to wait 1.5seconds before being able to snipe fast? I don't see how it's a bug since every "one target" spell behave like this. Feedback and queen's heal just do exactly the same thing. In fact, AoE spells do the same thing. But with these spell's, you don't "click" on a particular unit so you avoid this problem. As you said AOE spells,(in fact any spell with no target requirement) do the same thing but you don't click on a unit and therefore there is no need to Hold the spell key and THEN wait 1.5seconds before start snipe spamming(Hold R + left click spam method). Feedback you only need to use it once per target and Queen's heal doesn't require crazy spamming to be effective,so the only spell affected is the Snipe.
The reason for the 1.5 second delay is because the entire game has it, its basically the game accelerating the spam the longer you hold the button. Want to build zerglings? You hold z, one zergling builds, you wait 1.5 seconds, and then it starts mass building. Want to cast forcefields? You either hold the f button for 1.5 seconds before casting, or you do what any sane person would do and spam that button. Want to snipe or cast a million infested terrans at once (without binding scroll up and down) all you need to do is use that shift button and que them up.
The reason its not a problem is because you can work around it fairly easily.
|
On February 07 2012 20:22 Keone wrote:Show nested quote +On February 07 2012 17:23 PH wrote:On February 07 2012 14:01 Keone wrote:On February 06 2012 15:23 Azzur wrote: For those that are questioning the validity / legality of this - I'm 100% sure that this would be allowed in the GSL - players are allowed to install their own mouse drivers and rebind keys as long as it's 1-to-1 key bind. For tournaments such as MLG, it "should" be allowed but time constraints may not allow for it.
For example, I'm using a Microsoft Intellimouse and the built-in drivers allow me to rebind keys. In World of Warcraft, doing such things are very common that gaming mice have been released to have many buttons on a mouse. Question, doesn't this count as NOT 1-to-1 key binding, and thus, illegal? Because this would technically be Many-to-1, because the left mouse button is still the Mouse1, and if you bind another key to Mouse1, that counts as Many-to-1. Just an honest question. No. You're simply mapping more than one key to one particular action. You're not mapping multiple actions to one key, which would be problematic. It'd be like having multiple keys build a probe, which isn't really bad. This is bad only 'cause the mouse scroll wheel can be triggered so quickly... I understand and understood before that 1-to-Many is bad; that wasn't part of my original question. My question is: is Many-to-1 legal? Your example with multiple keys mapped to a probe would count as a Many-to-1; is that legal within GSL rules? This is because someone originally said only 1-to-1 mappings are legal in GSL.
Yes, of course its allowed. The game even has the option of doing it in the ingame hotkey system. Hell, if you want to bind the entire keyboard to "d" and faceroll your way to victory there is nothing stopping you. When people talk about 1-1 mapping they mean that you can only bind one key to do one "click". Which means you can't bind a button to hotkey queens, click c and inject for you in one click. You can only bind the key to do one of those things.
edit: should only clarify the button can't be "smart" either. So you can't have it do all of those 3 things in 3 clicks, even thought its technically one thing pr click, its still "one button doing many things".
|
I don't feel like this breaks the game beyond repair. Or that people won't figure out how to deal with it. As such, I don't think this needs to be patched. Idk. A lot of these posts to me seem like whiney kids who don't want to have to work to win and think it unfair that terran's don't have to work or some idiocracy. And btw, I play zerg so you can cut those stereotypical adhominem come backs. Maybe to take a page out of Sirlin's book, http://www.sirlin.net/ptw-book/what-should-be-banned.html
"How does one know if a bug destroys the game or even if a legitimate tactic destroys it? The rule of thumb is to assume it doesn’t and keep playing, because 99% of the time, as good as the tactic may be, there will either be a way to counter it or other even better tactics. Prematurely banning something is the scrub’s way. It prevents the scrub from ever discovering the counter to the Valle CC or the diamond trick. It also creates artificial rules that alter the game, when it’s entirely possible that the game was just fine the way it was. It also usually leads to an avalanche of bans in order to be consistent with the first. When players think they have found a game-breaking tactic, I advise them to go win some tournaments with it. If they can prove that the game really is reduced to just that tactic, then perhaps a ban is warranted. It’s extremely rare that a player is ever able to prove this though. In fact, I don’t even have any examples of it."
Further
"The only reasonable case to ban something because it is “too good” is when that tactic completely dominates the entire game, to the exclusion of other tactics. It is possible, though very rare, that removing an element of the game that is not only “the best” but also “ten times better than anything else in the game” results in a better game. I emphasize that is extremely rare. The most common case is that the player requesting the ban doesn’t fully grasp that the game is, in fact, not all about that one tactic. He should win several tournaments using mainly this tactic to prove his point. Another, far rarer possibility is that he’s right. The game really is shallow and centered on one thing (whether that one thing is a bug or by design is irrelevant). In that case, the best course of action is usually to abandon the game and play one of the hundreds of other readily available good games in the world."
And what's a soft ban?
"Japan, however, does not officially ban Akuma from tournaments! They have what is called a "soft ban." This is a tacit understanding amongst all top players that Akuma is too good to be played, and that he destroys an otherwise beautiful game, so they unofficially agree not to play him. There are always a very small number of people who do play him in tournaments, but never the top players. Usually a few poor players try their hand at the god-character and lose, which is utterly humiliating and crowd-pleasing. This is an interesting alternate take on the "hard ban" we have in America."
Original article: http://www.sirlin.net/ptw-book/what-should-be-banned.html
|
On February 07 2012 20:31 Aletheia27 wrote:... A lot of these posts to me seem like whiney kids who don't want to have to work to win and think it unfair that terran's don't have to work or some idiocracy. And btw, I play zerg so you can cut those stereotypical adhominem come backs. Maybe to take a page out of Sirlin's book, http://www.sirlin.net/ptw-book/what-should-be-banned.html
Do as I say, not as I do
|
Setting the scroll wheel to be right click instead of left click gives you and excellent fast way of deselcting units (like when you put workers on gas, and box 7 drones, just a few scrolls and your down to 3) - maybe this could be used for marine splitting and improved zergling micro as well...?
|
Guess its time to switch to terran ^^^^
|
On February 07 2012 20:31 Aletheia27 wrote:I don't feel like this breaks the game beyond repair. Or that people won't figure out how to deal with it. As such, I don't think this needs to be patched. Idk. A lot of these posts to me seem like whiney kids who don't want to have to work to win and think it unfair that terran's don't have to work or some idiocracy. And btw, I play zerg so you can cut those stereotypical adhominem come backs. Maybe to take a page out of Sirlin's book, http://www.sirlin.net/ptw-book/what-should-be-banned.html"How does one know if a bug destroys the game or even if a legitimate tactic destroys it? The rule of thumb is to assume it doesn’t and keep playing, because 99% of the time, as good as the tactic may be, there will either be a way to counter it or other even better tactics. Prematurely banning something is the scrub’s way. It prevents the scrub from ever discovering the counter to the Valle CC or the diamond trick. It also creates artificial rules that alter the game, when it’s entirely possible that the game was just fine the way it was. It also usually leads to an avalanche of bans in order to be consistent with the first. When players think they have found a game-breaking tactic, I advise them to go win some tournaments with it. If they can prove that the game really is reduced to just that tactic, then perhaps a ban is warranted. It’s extremely rare that a player is ever able to prove this though. In fact, I don’t even have any examples of it." Further "The only reasonable case to ban something because it is “too good” is when that tactic completely dominates the entire game, to the exclusion of other tactics. It is possible, though very rare, that removing an element of the game that is not only “the best” but also “ten times better than anything else in the game” results in a better game. I emphasize that is extremely rare. The most common case is that the player requesting the ban doesn’t fully grasp that the game is, in fact, not all about that one tactic. He should win several tournaments using mainly this tactic to prove his point. Another, far rarer possibility is that he’s right. The game really is shallow and centered on one thing (whether that one thing is a bug or by design is irrelevant). In that case, the best course of action is usually to abandon the game and play one of the hundreds of other readily available good games in the world." And what's a soft ban? "Japan, however, does not officially ban Akuma from tournaments! They have what is called a "soft ban." This is a tacit understanding amongst all top players that Akuma is too good to be played, and that he destroys an otherwise beautiful game, so they unofficially agree not to play him. There are always a very small number of people who do play him in tournaments, but never the top players. Usually a few poor players try their hand at the god-character and lose, which is utterly humiliating and crowd-pleasing. This is an interesting alternate take on the "hard ban" we have in America." Original article: http://www.sirlin.net/ptw-book/what-should-be-banned.html
It does break the game when the entire balance of it is based around not being able to do 20000 apm with a single unit and instakill an entire army. Not is it very interesting to watch as a spectator either. Watching a long TvZ game entierly without mutalisks, ultras, broodlords and hydras doesn't sound very interesting tbh.
|
LOL! I can't believe anyone is arguing that this ISN'T completely broken
|
This doesn't work for me. I get bluescreen when scrolling.
|
Bluescreen ? oO You must have a problem with your driver.
|
I would like to hear Blizzard's stance on this asap.
|
|
|
|