End-To-End Macro: Taekwon Master

[kingkevz]

i like it ^_^

[sli]

Either way pepinows is a fucking NOOB. So this is for him:
WHY THE FUCK ARE YOU POSTING IN MY THREAD? GET THE FUCK OFF THESE BOARDS.

Well, sorry to tell u this, but the fucking NOOB is correct. You can't declare a variable in AUTOMACROS but, you can in MACROS. And automacros != macros.

That's called a BUG in the fucking MACRO PLUGIN. The problem with you nublets is that, unlike you, I can set variables in automacros. So excuse me for having a better Macro plugin than everyone else.

[Kafka]

He's lying. It's not true.

[sli]

Oh, btw, just to be sure. I tested a 100% stock macro plugin.

You can set variables in automacros, idiots.

[ 63/ 99] You attack Monster Skeleton (3) - Dmg: 379 (delay 17.7)
[macro] automacro lvl1 triggered.
[macro][log] "testvalue"
Exp gained: 54/0 (0.00%/0.00%)

Code: Select all

automacro lvl1 {
	console /.*?You attack Monster.*?/i
	call {
		$testvar = "testvalue"
		log $testvar
	}
}

Awesome job. I didn't have to humiliate you all myself, the macro plugin did it for me.

Also, updated the macro a tad. Still not finished, but more finished than it was originally.

[Mushroom]

From what I know, YOU CAN'T SET VARIABLES IN AUTOMACROS.

Code: Select all

automacro lvl1 { <--- Begin the automacro
   console /.*?You attack Monster.*?/i
   call { <--- Here the automacro calls the macros
      $testvar = "testvalue" <----- so this line is a macro, not a automacro
      log $testvar
   }
}

automacro lvl1 {
   console /.*?You attack Monster.*?/i
   call lvl 2
}
macro lvl 2 {
      $testvar = "testvalue" 
      log $testvar
   }

Both macros do the samething, but the first is a little bit shorter than the second.
So, as you can see, VARIABLES CAN ONLY BE DECLARED IN MACROS.

Code: Select all

Awesome job. I didn't have to humiliate you all myself, the macro plugin did it for me.

Hahahhaha, sorry to tell the truth, but you just humiliated yourself

This is what happens when you declare variables in AUTOMACROS.

Code: Select all

[console] control\macros.txt: ignoring '$teste = teste' (munch, munch, unknown automacro keyword)

And here is the macro:

Code: Select all

automacro teste {
  console /teste/i
  $teste = teste
  call {
		log $teste 
		}
}

Like I said automacros != macros.

You can set variables in automacros, idiots.

Now the idiot here is you --''

[Kafka]

Hey can everyone stop TALKING LIKE THIS.

It is really fucking obnoxious.

[Mushroom]

Well, I used it to call everybody's attention in some important words.
But it didn't worked, because sli still didn't understand what I wanted to show.
I just wanted to sorry if I offended somebody, just trying to help.
And i like to write like this. It's beautiful

[sli]

You guys are still retards: definition of specifics. Maybe next time instead of being brainless, you can point out an unintentional syntactical error? I don't use macros, so as far as I give a FUCK a call block in an automacro is still a fucking automacro. Just because it uses the macro parser doesn't change a damn thing, it's still a macro that's automatically triggered. Hence, automacro. So basically you successfully landed yourself a spot on my shitlist. Expect mod abuse.

Feel free to bitch. The rest of the team knows I abuse.

[Mushroom]

I just said that you can't declare variables in automacros because of this automacro here that u posted:

Code: Select all

automacro autolvl10 {
   job >= 10
   $target = $.joblvl + 1
   call {

Because this isn't going to work.
We are just reporting small bugs and what you did? started to swear.
So, unless u respect me, I won't respect you.

[sli]

You asshats fucking ruined my thread.