I just wish I could convince people that the word "I" is capitalized.
At least its not as bad as: ur, your instead of you're, pwned, and other leet speak. I play a paladin now and ive added /stopcasting to FoL and Holy light, i really notice the differences with flash of light in instances. Its saved the tanks life many a time. I really wish there was a way to fix the lag when pressing instant spells, Often i have to press the button 2 times to set off the instant spell. I don't know if this is due to lag or some other factor.
So 'ur' is unacceptable, but 'ive' is perfectly OK.
You're pretty dumb.
pwned?
I kid, I kid.
I have also run into some odd lag displays using Quartz, where the lag will sometimes display as some unhealthy number wildly different than the norm, such as 600 or 800ms. In these cases I assume it's an interface bug, something client-side corrupting information or an unintended mod interaction, and I simply ignore it and proceed to wait until the casting bar gets to approximately where it usually is before hitting my /stopcasting macro. It is irritating to be sure, but the outliers are fairly apparent as they are usually clearly distinct from your standard lag. I cary between 90ms and 200ms almost every night, so if I see a 500ms lag displayed on Quartz, it's safe to assume it's incorrect and just wait for the cast bar to approach the end.
I have also run into some odd lag displays using Quartz, where the lag will sometimes display as some unhealthy number wildly different than the norm, such as 600 or 800ms. In these cases I assume it's an interface bug, something client-side corrupting information or an unintended mod interaction, and I simply ignore it and proceed to wait until the casting bar gets to approximately where it usually is before hitting my /stopcasting macro. It is irritating to be sure, but the outliers are fairly apparent as they are usually clearly distinct from your standard lag. I cary between 90ms and 200ms almost every night, so if I see a 500ms lag displayed on Quartz, it's safe to assume it's incorrect and just wait for the cast bar to approach the end.
Actually, to be quite fair, I used to think the exact same thing as you. But I have actually tried and do stopcasting even when theres some retarded lag being shown in quartz, and to my great surprise, more often than not, it works. I even tried once to stopcast a fireball with 1200ms lag, and it worked.
<Eej> YOU"RE GONNA PULL
<Eej> IF YOU SQUEEZE OFF ANOTHER ARCANE BLAST
<Spectear> You've obviously never played with Manly.
<Spectear> That's hardly a reason to stop DPS. Very Manly Staff
I have also run into some odd lag displays using Quartz, where the lag will sometimes display as some unhealthy number wildly different than the norm, such as 600 or 800ms. In these cases I assume it's an interface bug, something client-side corrupting information or an unintended mod interaction, and I simply ignore it and proceed to wait until the casting bar gets to approximately where it usually is before hitting my /stopcasting macro. It is irritating to be sure, but the outliers are fairly apparent as they are usually clearly distinct from your standard lag. I cary between 90ms and 200ms almost every night, so if I see a 500ms lag displayed on Quartz, it's safe to assume it's incorrect and just wait for the cast bar to approach the end.
I've seen this as well, but it's typically ACCURATE. It means you just cast the spell during a lag spike, and I've had all my stop casting macros work fine when I use them in the lag part of the bar. Maybe it's the version your running?
I've seen this as well, but it's typically ACCURATE. It means you just cast the spell during a lag spike, and I've had all my stop casting macros work fine when I use them in the lag part of the bar. Maybe it's the version your running?
I update daily. It could be interface lag of some sort I suppose?
Someone earlier asked if there was a way to use stopcasting as a rogue. A reply to that post included a comment that all of a rogue's abilities are instant, so stopcasting can't help.
Actually, as has been previously stated in this thread, stopcasting can be used to chain together abilities that do not trigger the GCD. As a mutilate rogue (with cold blood), I have a series of macros that look like this:
This macro will cast mutilate if left clicked. If right clicked, it will cast cold blood and then immediately cast mutilate, removing the need to click cold blood separately when you want to use it. I have one of these for mutilate, SS, evis, envenom, and ambush. The macro casts the two spells much faster than a human ever could, making for much more efficient button clicking.
Similar macros could be written for subtlety rogues, as I believe (but am not 100% certain) that shadowstep and premed also do not trigger the GCD. You might try something like:
In this case, left clicking would cast shadowstep and then ambush, while right clicking would tack premed on if it were available. I'm not sure about the last two lines, since when I was sub, I seem to recall there being a slight delay during that actual "step through the shadows". This macro would at least, however, allow you to add premed to your shadowstep with only one click.
There may be more macros like this that could benefit rogues, but as far as I know, we don't have very many abilities that don't trigger the GCD. Anyway, if you're muti or sub, have fun with these!
I've been experimenting with /spellstopcasting for a while now and I like to bounce an idea off the community. When I'm raiding, my ping is ~150-200ms and stays that way for the entire time I'm raiding, with optimal spellstopcasting, I should be able to shave .15-.2s off my cast time for Lightning Bolt but I haven't been able to do it because of slow reflexes/mental fatigue. This brings me to my question. I recently discovered that my Nostromo gamepad's software allows me to make a macro that can precisely hit my LB button every 2.0 seconds. IF my lag is constant, would I be able to put /spellstopcasting into my cast macro, have the software hit the LB button exactly every 2s and get the reduced casttime?
After giving it a lot of thought, it seems like it should work given my latency is constant, because Quartz etc. shade the bar based on the latency of the previous cast. The software should be doing what we do manually, stopping the first cast and starting the next ~150-200ms before the client normally allows, which will reach the server right as the first has finished casting. Will this work, or have I made a wrong assumption about how /stopspellcasting and Quartz work?
I've been experimenting with /spellstopcasting for a while now and I like to bounce an idea off the community. When I'm raiding, my ping is ~150-200ms and stays that way for the entire time I'm raiding, with optimal spellstopcasting, I should be able to shave .15-.2s off my cast time for Lightning Bolt but I haven't been able to do it because of slow reflexes/mental fatigue. This brings me to my question. I recently discovered that my Nostromo gamepad's software allows me to make a macro that can precisely hit my LB button every 2.0 seconds. IF my lag is constant, would I be able to put /spellstopcasting into my cast macro, have the software hit the LB button exactly every 2s and get the reduced casttime?
After giving it a lot of thought, it seems like it should work given my latency is constant, because Quartz etc. shade the bar based on the latency of the previous cast. The software should be doing what we do manually, stopping the first cast and starting the next ~150-200ms before the client normally allows, which will reach the server right as the first has finished casting. Will this work, or have I made a wrong assumption about how /stopspellcasting and Quartz work?
Using an external program (which includes the Nostromo) add a timing to casting is against the ToS.
Why do I have to repeat this each time? Unattended play is bannable. Having a macro that would kill mobs while running in circle is bannable, yes. But doing a macro that spams your key every set interval is not unattended play.
And BTW, I tried doing that myself using a G15 keyboard. It doesn't work. You will get 100% of your spells cancelled and its going to tell you 'spell is not ready'.
<Eej> YOU"RE GONNA PULL
<Eej> IF YOU SQUEEZE OFF ANOTHER ARCANE BLAST
<Spectear> You've obviously never played with Manly.
<Spectear> That's hardly a reason to stop DPS. Very Manly Staff
Why do I have to repeat this each time? Unattended play is bannable. Having a macro that would kill mobs while running in circle is bannable, yes. But doing a macro that spams your key every set interval is not unattended play.
And BTW, I tried doing that myself using a G15 keyboard. It doesn't work. You will get 100% of your spells cancelled and its going to tell you 'spell is not ready'.
It's AUTOMATED play, which is also against the ToS. It's repeating an action without human input for each spell. This is a bannable offense, and if you don't believe me there are several blue posts about it.
In fact it's safer to assume that if you cannot do it with an ingame macro it's against the ToS. You cannot pause ingame macros, thus using a g15 to do it would be against the ToS.
Originally Posted by Berghe
To put it simply, stay away from fully auto-mated game play and you should be fine...
A human is not providing a click action for each button press in the macro you suggested, and thus it's considered 'key spoofing' which falls under automated play.
If only you read the thread you linked, there is no actual information besides someone that claims that warden disables G15 macros. I never had my macros behave erratically, so I can assume that warden never did such thing during the time I used mine. I can assure you I ran exactly the macros you described for months -- almost 1 year now -- and never got in trouble. I don't use them anymore, granted, since I was getting a DPS loss out of trying to lazy-out stopcasting, but still, your statement is just as baseless as the thread you linked.
The only thing your second link points is:
Originally Posted by blue
We do not close accounts simply due to the hardware being used. When it comes to hardware with such capabilities as the G15 we have no policy that prohibits its use as long as our Terms of Use (WoW -> Legal) are not violated by taking advantage of the features this particular piece of hardware has to provide. To put it simply, stay away from fully auto-mated game play and you should be fine, Ilikepotions.
Which says nothing really besides don't run unattended play macros.
EDIT: with all this said, I don't advocate the use of such macro, since I found that, for me, they are less efficient than straight out in-game macro. But I see this being repeated a lot around, and nobody ever got banned save 1 guy that used it to automate levelling.
<Eej> YOU"RE GONNA PULL
<Eej> IF YOU SQUEEZE OFF ANOTHER ARCANE BLAST
<Spectear> You've obviously never played with Manly.
<Spectear> That's hardly a reason to stop DPS. Very Manly Staff
If only you read the thread you linked, there is no actual information besides someone that claims that warden disables G15 macros. I never had my macros behave erratically, so I can assume that warden never did such thing during the time I used mine. I can assure you I ran exactly the macros you described for months -- almost 1 year now -- and never got in trouble. I don't use them anymore, granted, since I was getting a DPS loss out of trying to lazy-out stopcasting, but still, your statement is just as baseless as the thread you linked.
Except the person I quoted is Cogwheel, and is almost on 'Iriel' level status.
Originally Posted by manly
The only thing your second link points is:
Which says nothing really besides don't run unattended play macros.
EDIT: with all this said, I don't advocate the use of such macro, since I found that, for me, they are less efficient than straight out in-game macro. But I see this being repeated a lot around, and nobody ever got banned save 1 guy that used it to automate levelling.
Except that is exactly what automated play means. You're not making the decisions, or hitting the buttons. The macro is.
Will you get banned for it? most likely not, but is it against the ToS, yes.
How are you not making the decisions? You have a macro that repeats one spell every set interval for as long as you press it. You clearly indicate that you intend to cast said spell for as long as you press the key down.
We're not talking here of some spell rotation all programmed into one macro. Were speaking of casting one spell at every set interval.
Of course if you use it to macro-in a full set of spell rotation, I guess the area just gets less and less obvious where the lines are.
<Eej> YOU"RE GONNA PULL
<Eej> IF YOU SQUEEZE OFF ANOTHER ARCANE BLAST
<Spectear> You've obviously never played with Manly.
<Spectear> That's hardly a reason to stop DPS. Very Manly Staff
Actually, to be quite fair, I used to think the exact same thing as you. But I have actually tried and do stopcasting even when theres some retarded lag being shown in quartz, and to my great surprise, more often than not, it works. I even tried once to stopcast a fireball with 1200ms lag, and it worked.
Yeah, more often than not, the absurdly early cancel actually gets your spell off anyway.
Things to note:
Quartz and the like calculate the duration of the "red zone" by measuring the difference between the input to start the spellcast on the client side, and the receipt of UNIT_SPELLCAST_START from the server. If you're in the midst of a little latency spike right as you start a cast, Quartz will measure a huge gap, and you'll a get a large red bar. As long as that high latency lasts for at least 3 seconds, you can take the red bar as accurate and cancel early. If your latency is varying widely on a time scale shorter than a single cast time, however, this will get you into trouble.
How are you not making the decisions? You have a macro that repeats one spell every set interval for as long as you press it. You clearly indicate that you intend to cast said spell for as long as you press the key down.
We're not talking here of some spell rotation all programmed into one macro. Were speaking of casting one spell at every set interval.
Of course if you use it to macro-in a full set of spell rotation, I guess the area just gets less and less obvious where the lines are.
Because you're inputing one key press to do multiple (although the same) action. It doesn't matter. YOU only generated one key event, the macro is generating multiple events. This is key spoofing, and against the ToS, hence why Warden filters macros like it, and why afk botters get banned.
And if you want to get into semantics, both things are identical.
A spell rotation is, by definition, spells cast in sequence. Is casting the same spell multiple times not 'spells cast in sequence' ?
Anyway, this is going really off topic, so I'll leave it at that.
Yeah, more often than not, the absurdly early cancel actually gets your spell off anyway.
Things to note:
Quartz and the like calculate the duration of the "red zone" by measuring the difference between the input to start the spellcast on the client side, and the receipt of UNIT_SPELLCAST_START from the server. If you're in the midst of a little latency spike right as you start a cast, Quartz will measure a huge gap, and you'll a get a large red bar. As long as that high latency lasts for at least 3 seconds, you can take the red bar as accurate and cancel early. If your latency is varying widely on a time scale shorter than a single cast time, however, this will get you into trouble.
It's the duration of the spell your casting, not 3 seconds. All that needs to happen is for you to maintain casting client side until the server finishes the cast :P
It's the duration of the spell your casting, not 3 seconds. All that needs to happen is for you to maintain casting client side until the server finishes the cast :P
Has anyone else experienced problems trying to use stopcasting macros on spells that are hasted faster than 1.5s? I realize most haste will still be limited by the GCD, but it was my understanding that heroism/bloodlust would actually lower the GCD. Trying to spam a fully stacked AB using a stopcast macro with heroism running just seems to give me all kinds of fits. Basically what I am seeing is that when I press the macro, the existing cast goest off but a new spell is not cast. No error message is given and my character just sits there until I recast the spell. I end up loosing a lot of dps in the process. Without heroism, my stopcasting macros seem to work just fine on 1.5s spells.
Has anyone else experienced problems trying to use stopcasting macros on spells that are hasted faster than 1.5s? I realize most haste will still be limited by the GCD, but it was my understanding that heroism/bloodlust would actually lower the GCD. Trying to spam a fully stacked AB using a stopcast macro with heroism running just seems to give me all kinds of fits. Basically what I am seeing is that when I press the macro, the existing cast goest off but a new spell is not cast. No error message is given and my character just sits there until I recast the spell. I end up loosing a lot of dps in the process. Without heroism, my stopcasting macros seem to work just fine on 1.5s spells.
I have the same problem, and I'm not really sure whether it supports BL lowering the GCD or not. I just know that when I have to stack scorches my mental timer doesn't work when I'm bloodlusted, I always end up with spell not ready. I have to cast scorch, pause, scorch, pause, etc.
Originally Posted by Bekah
Then go put your dick in a car door and slam it a couple of times to finish proving how awesome you are and report back to the IMANG thread.
The main issue I find when using a stopcasting macro and Quartz is extremely problematic. Many times, for reasons I do not know, when I initiate the stopcast the spell cast immediately after the spell that has been "stopcasted" fails to show a castbar at all. The only thing I will have displayed is a "spark bar". The spell does indeed fire off, however its extremely frustrating to not be able to use the stopcasting macro on every spell due to this quirk.
The difference, however, is that I don't just get this "once a night" or rarely, but about every 10-15seconds, rendering the option almost completely useless. Any new insight on the topic?
Last edited by CHeeSY-CrAfT : 08/24/07 at 8:16 PM.
07/25/07, 10:49 AM
Similar Threads
