The reason you put a comma at the end of /castrandom is so that there's a chance to do nothing
e.g.
/castrandom lighting bolt, chain lightning,
means
1/3rd chance LB
1/3rd chance for CL
1/3rd chance for nothing - the ","
/castrandom lightning bolt, chain lighting
would be 50/50 on either one
Sweet* teams - <unGankable> - Kil'Jaeden US Alliance - 10x Shamans, 9x DKs 1x Pally, 10x Drews
I thinks it so you dont get wierd result if neither are up.
No, Kicksome has it exactly right. /castrandom DOES NOT CARE ABOUT COOLDOWNS. If you have the following:
/castrandom Lava Burst, Flame Shock
When you press it once you have a 50% chance of casting either. When you press it again, YOU HAVE THE SAME 50% CHANCE. It doesn't care that Lava Burst was just cast and is on cooldown, if its random roll determines Lava Burst should be cast again it'll try and the engine will return the error Spell Not Ready (or whatever). A comma just means "do nothing", its a way to "drop down" to the next line:
/castrandom Flame Shock, Lava Burst,
/cast Lightning Bolt
for example will cast FS or LV or nothing (33% chance of any), if nothing casts it will cast LB. If either Flame Shock or Lava Burst cast, then Lightning Bolt will not be cast. If both FS and LV are on cooldown it'll try, fail, and then drop down to cast Lightning Bolt.
The problem with any of these macros is that you really, really, really want Flame Shock to be cast before Lava Burst -- otherwise 50% of the time Lava Burst will be cast first, and you will not get the crit guarantee. I use this currently as my PVE spam macro (I have seperate buttons for everything for PVP, or complex boss fights):
#showtooltip Lava Burst
/use 13
/use 14
/cast Elemental Mastery
/castsequence [target=focustarget,harm][] reset=target/combat/8 Flame Shock,Lava Burst,Lightning Bolt,Lightning Bolt,Lightning Bolt
As you get more haste you may need more LBs, keep an eye on the c/d for FS and LV on your bars and you can add more -- I actually could do with just 2 LBs, but I prefer the 3d one since FS staying a few seconds extra is nice for mana. I do chain lightning seperately since its a high mana spell and not needed for most bosses.
The nice thing about the macro above is that I can just spam that key as much as I want and it works fine, since /castsequence will wait patiently for the spell to complete before moving to the next one.
Sounds like a couple of times to me. Notice that I didn't say "the average tapping rate of a healthy teenager is 5 Hz" or something similar - I left it vague because I didn't feel it was essential to the point. But if you want to get all precise and sciencey...Originally Posted by 'Maxion',index.php?page=Thread&postID=154955#post1 54955
If you need it to be that precise, it's not that hard to design a test get a more specific answer, or there are several good ones in use. Don't forget to take several trials to get better data. Here's some data from a research study by Cousins, Corrow, Finn, and Salamone in 1997. These are from 10-second trials, so 55 total taps is only 5.5 Hz (5.5 taps per second).
Let me know what method you and your friends are using to obtain and calculate almost four times the maximum rate this study observed. A 20Hz repeated keypress rate seems rather impressive, even allowing for potential differences in stroke length and so forth introduced by choice of testing methodology.
Yeah, that's a good start.
It wouldn't be too hard to code something from scratch either for someone with coding experience. For a naive method, record the start time and check the system clock until it's N seconds later. Meanwhile append the key presses to a string. At the end, report string length divided by time elapsed.
One other thing I have to worry about is the up and down signals and Keyclone's latency. It's slow enough that key mashing isn't always a great idea. Maybe I'll get a hardware mux eventually.
I'm a little curious about this now. Maybe I'll whip up a quick VI...really the reason I didn't yet is that it only runs on my laptop, not the nice mechanical keyboard I use to play on.
Counter-edit edit:
Cool. Sounds more believable than the 20+ he was claiming. It sounds in line with the research paper I found - I think they were using a telegraph key or something like that, so the shorter stroke length of a keyboard would speed it up a little.
If you really, really need it to go faster, you could always get a mouse with a loose wheel...still a technically legal method, although it might give you a high enough rate to seem suspicious.
Another edit:
Acoustic analysis might be the most effective. And you could do it with a decent microphone and free sound editing software (although you'd want more for a less simple analysis).
Also, lest there be any further confusion about my initial claim, let me clarify a point of semantics:
couple, n. 4: Informal. A few; several: a couple of days.
maybe im missing it... but why not use the old and simple proven setup
i use a [target=focusttarget] system in all of my other spells. but had to revert to basic for this
/assist focus
/castsequence reset=target/17 Flame Shock, Lava Burst, Lava Burst, Lava Burst, Lava Burst, Lava Burst, Lava Burst,
the reset target works, due to the assist part, the reset 17 works (with glyph flameshock lasts 18 seconds for me) and will reapply flameshock if a boss encounter lasts more than 20 seconds
downside to this is... in pvp, the people will see who the main target is gonna be due to the assist part....
but dont you think that if a warrior see's 4 flameshocks on him, he's gonna know that anyway
I gang, I just got lava burst (omfg wowwowowow) and tried some of the macros here and couldn't get it to work properly. Finally I had to take the reset=target out (left reset=17) and it started working. The problem is I lose my target each time (using the FTL setup). Does anyone have any suggestions on how I can get this to work properly and be able to switch targets to make it reset?
Macro for current main
Macro for non-mainsCode:/console Sound_EnableSFX 0 /use Mendicant's Charm /cast Elemental Mastery /console Sound_EnableSFX 1 /castsequence reset=target/17 Flame Shock, Lava Burst, Lava Burst, Lava Burst, Lava Burst, Lava Burst, Lava Burst,
So, if I put 'target' in the reset variable only the current main can follow up the shock with a lava burst. The others just stand there.Code:/stopmacro [nomod] /console Sound_EnableSFX 0 /use Mendicant's Charm /cast Elemental Mastery /console Sound_EnableSFX 1 /target [mod:SHIFT,nomod:alt,nomod:ctrl,target=Shâm][mod:CTRL,nomod:alt,nomod:shift,target=Shăm][mod:SHIFT,mod:CTRL,nomod:alt,target=Shäm][mod:ALT,nomod:ctrl,nomod:shift,target=Shám][mod:SHIFT,mod:ALT,nomod:ctrl,target=Shàm] /assist /castsequence reset=17 Flame Shock, Lava Burst, Lava Burst, Lava Burst, Lava Burst, Lava Burst, Lava Burst, /targetlasttarget
Dana Pain
Legion of BoomKil'Jaeden
instead of first targetting the group member and THAN assisting (targeting) the mobCode:/stopmacro [nomod] /console Sound_EnableSFX 0 /use Mendicant's Charm /cast Elemental Mastery /console Sound_EnableSFX 1 /assist [mod:SHIFT,nomod:alt,nomod:ctrl,target=Shâm][mod:CTRL,nomod:alt,nomod:shift,target=Shăm][mod:SHIFT,mod:CTRL,nomod:alt,target=Shäm][mod:ALT,nomod:ctrl,nomod:shift,target=Shám][mod:SHIFT,mod:ALT,nomod:ctrl,target=Shàm] /castsequence reset=17 Flame Shock, Lava Burst, Lava Burst, Lava Burst, Lava Burst, Lava Burst, Lava Burst, /targetlasttarget
this should target the mob immediatly, and not screw up the reset=target
but i dont know if /assist can be used with conditions
so please try it out, and let us know if that works
Posting Rules
Reply With Quote
Connect With Us