What causes double casting at kings?

[klvino]

white in my face,

And how often does this happen?

[Tubbers]

white in my face,

And how often does this happen?

KB POPPED WHITE, RIGHT IN MY FACE. >> *Clever shortening occurs* >>KB popped, white in my face.

Although now, it doesn't seem clever so much as really gay.

[Tricen]

white in my face,

And how often does this happen?

KB POPPED WHITE, RIGHT IN MY FACE. >> *Clever shortening occurs* >>KB popped, white in my face.

Although now, it doesn't seem clever so much as really gay.

Argh more dumbassess.

[Jhun]

Your target will be set on yourself if you were too fast on your 1st spell.
like:

1st claiming attempt
/ma Stun <t>
<t> will be on King Behemoth
-let's say you're fast you'll be interrupted or just unable to land your spell-

2nd claiming attempt
next stun macro you spam will be like this:
/ma Stun <t>
<t> will be on Tubbers and you will get the messege "you cannot attack that target"

[Tubbers]

Your target will be set on yourself if you were too fast on your 1st spell.
like:

1st claiming attempt
/ma Stun <t>
<t> will be on King Behemoth
-let's say you're fast you'll be interrupted or just unable to land your spell-

2nd claiming attempt
next stun macro you spam will be like this:
/ma Stun <t>
<t> will be on Tubbers and you will get the messege "you cannot attack that target"

I don't even really know what to say to this: is this just an informative thing, or are you agreeing with the implication? I already stated what my macro was, I use /targetnpc as the first line of my macro 90% of the time, this is the equivalent of spamming f8 on the keyboard. While I believe you are correct that too-fast claims target yourself, it is completely irrelevant given that I never stop spamming my macro until Dia (not Stun) actually lands on the mob, or it gives me a string of "You cannot attack that, target already claimed." It will target the mob, and not me, and the messages are different anyways. That's generally what I do unless it is Nid, in which case I wouldn't use Dia, probably stone/gravity or something else that is quick.

Argh more dumbassess.

Sorry, I'm still busy laughing at this whole thing, it was hard for me to make my first post as serious as it was. I was simply trying to show why'd I typed what I did. To actually answer the question: never has, never will.

[Takedown3]

why would u macro for claim? between macro lag and sending the /targetnpc command ur losing valuable microseconds

menu spam for the win, if u get claim delayed on the first attempt you wont win ur second attempt with macro spam. especially at high population camps

[Toonshady]

well, everything was already debunked. sorry tubbers if it caused you any headache. it just showed up on everyone's log and they got suspicious due to the recent double stun claiming blackmage from another linkshell.

why would u macro for claim? between macro lag and sending the /targetnpc command ur losing valuable microseconds

menu spam for the win, if u get claim delayed on the first attempt you wont win ur second attempt with macro spam. especially at high population camps

maybe his macro is really fast. it allowed him to the be the first one on everyone's log to cast on KB.. even before the people who spam a spell or /ja from menu in lego land resolution even before it rendered for tdizzle

[inafume]

I remember hearing a while back that some of the bots had built-in give-aways, where you'd say something absolutely retarded in shout if you were running the program and it activated, but I never actually say it happen to anyone so idk if it was anything more than a rumor.

]

[mandoo]

Question: If someone claims with a "ZOMG FLASH <t> LOLOLOLOL" macro, is that a big red flag for bot?

How so? I don't see how this has to be done by a bot. Its probably not the best claiming method possible, but seeing that in the party chat could mean a person is using something similar to this:

1. /target <stnpc>
2. /ma "Flash" <lastst>
3. /p ZOMG FLASH <lastst> LOLOLOL

Can be an ok claiming method if darters or other mobs are up in the way. Leave the blue arrow over w/e other mob is up, and try to tab onto the HNM and press enter as quickly as possible.

Then again, I've never claimed anything, so what do I know

Was just something I wondered.

I remember hearing a while back that some of the bots had built-in give-aways, where you'd say something absolutely retarded in shout if you were running the program and it activated, but I never actually say it happen to anyone so idk if it was anything more than a rumor.

WAIT 0, sry just wanted to contribute

[Appie]

Awoir, I remember Futrid having a picture of how he had 2 Chi Blasts on KB in his log shortly after each other (as in: no 3min cooldown), he might still have it. What it has to do with the topic? KB+Chatlog=messed up?

Maybe Arrowny has it too, think he was at that KB when it happened, was back in Lemonade XD

First picture got frog'd

[Mathaios]

As per request of a friend--
So far, my one (and only) claim, was a Fafnir, with Carnage Elegy. ELEGY. Second proudest moment ever next to this thread.

lol My one and only claim when I played was also fafnir but with Finale. I was absolutly shocked to see it turn red, then I died in about 3 hits b/c nobody would voke or stun.

[savageboy]

http://i170.photobucket.com/albums/u...ner/BOTlol.jpg

[Jaffar]

Spam some dia on that shit

[Stellar]

Seem's like under normal circumstance, as i believe has been said previously in this thread, the only way that you would be allowed to cast two times consecutively is if there was either a really large amount of time between casts (which i doubt was the case here) or if your alliance claimed the mob. It seemingly cuts any claim based recast delays as soon as you have the claim. Provokes in the log always appear quite a bit below their action, so he probably didn't even start casting the second dia until after the mob was claimed with provoke.

As far as not getting the claim and casting twice.. It's always delayed me far too long after my first cast to even attempt a second cast. So in a different scenario, had someone else claimed, there might be more to the screen shot.

[Tubbers]

why would u macro for claim? between macro lag and sending the /targetnpc command ur losing valuable microseconds

menu spam for the win, if u get claim delayed on the first attempt you wont win ur second attempt with macro spam. especially at high population camps

Nobody has ever proven that it is faster to cast stuff from menu. For all you know the menu simply parses to a string and sends that to the buffer to determine an action, meaning the menu could in fact be slower than just sending the string (ie. Macro). I like having a macro because it is easier for me, never had any problems with it so I stick with it. It may be slower, it may not be, but I've been both too slow and too fast with it so who knows?

If such a proof does exist point me towards it and I'll change my claiming style right away.

well, everything was already debunked. sorry tubbers if it caused you any headache. it just showed up on everyone's log and they got suspicious due to the recent double stun claiming blackmage from another linkshell.

maybe his macro is really fast. it allowed him to the be the first one on everyone's log to cast on KB.. even before the people who spam a spell or /ja from menu in lego land resolution even before it rendered for tdizzle

Rendering time varies a lot. It's based on a few things like people present, and some random factor. That's why at Nid day 9 when there are 50 billion people there sometimes you can't even see what popped until 5 minutes after an LS has started killing it. There were what, 40 people at this KB? I'm on a T3 university connection, so that may have helped my rendering time, or I got lucky.
The accusation doesn't really bother me, if anything it allowed me a good long laugh, which I sort of needed considering this is finals week for me. The fact that it was Awoir who posted it, rather than someone in SF, really made all the difference. I've known Awoir and his brother Izembo for quite a while, and we don't get along very well to say the least.

Stellar, as I already said, and as I think you mentioned in your post, the mob was purple (other party alliance claim) before I started casting again, I decided it would be quicker to just keep spamming macro and see what the result was, either it would allow me to cast, meaning we got the claim, or it would say right away the target had been claimed by someone else.

[Xavier]

Seem's like under normal circumstance, as i believe has been said previously in this thread, the only way that you would be allowed to cast two times consecutively is if there was either a really large amount of time between casts (which i doubt was the case here) or if your alliance claimed the mob. It seemingly cuts any claim based recast delays as soon as you have the claim. Provokes in the log always appear quite a bit below their action, so he probably didn't even start casting the second dia until after the mob was claimed with provoke.

Apparently the first SS is gone now, but it showed things a little differently than the second. If you looked closely, whoever took the SS got the message "Cannot attack, target already claimed" before the second Dia started casting, and before the actual provoke message appeared in log. Its hard to know exactly because of the nature of lag in the log, but the first picture was really obvious about it being a denied Dia, followed by a Dia after claim.

[Stellar]

I have little doubt pulling from the menu is a bit faster than pulling from a macro, but with claim delays, there's not necessarily an advantage in acting faster. Of course you can say, just wait a second after pop to spam from the menu, but it's pretty difficult to wait when a yellow king pops infront of your face.

As far as the defensive responses to the thread, maybe i'm reading into it wrong, but I was under the impression Awoir was more curious about the claiming mechanics than making botting accusations..

[Priran]

HOW U WS 5 TIMES IN A ROW U FUKING HACKER

[Sonomaa]

locked because of rollback