Hiyas. About the idea with a free account for testing... Never underestimate the other side. SoE aint stupid. When they see a lvl 1 char testing MQ on a trial-account... Maybe they just leave it alone because banning would be pointless anyway... Maybe they just lurk you into safety and wait till you...

As neither one still got a real clue, here a little hint:

Correct: /if n $v1==0

Incorrect: /if n $v1 ==0
Incorrect: /if n $v1== 0
Incorrect: /if n $v1 == 0


If you see the pattern, you got your bug. Its all over your code...

... B) If you run a macro unattended and an observant person like schue comes along and reports you. ... observant person, yes. reporting... no... dont get my name into a sentence like this, people might misunderstand that ;-) btw, another paranoid idea of mine: What if Verant intentionally impleme...

Well, I just asked myself what would I do if I were a Verant programmer with the job to detect Macroing... It would not be needed to log all actions over 24 hours I think. First I would do some monitoring about the speed of actions one account does. As a previous poster said, every combine is sent t...

Before I put down my thoughts I want to say that MQ is a very nice piece of work. I do not have problems with it beeing used at all. The basic question that drives us all nuts is, can we get caught? Can Verant detect what we are doing? Well, I have been visiting my hometown Kaladim alot since my cle...

L124RD wrote:Salutations,
on my client, the corpse isn't targetted when you kill something, so i don't have that problem...

It usually is not on mine either. It seems to be a very rare occasion, maybe one in hunderd kills or so. But if it happens, the script gets stuck there.

... /if "$target(id)"!="$v1" /goto :EndAF ... I found that sometimes at the end of fight the corpse of the dead mob gets targetted. This corpse seems to have the same id as the mob he was ;-)) So if this happens, the macro gets stuck here on a dead mob. To avoid the problem, /if...