Help withs Greenmachine
I've been using the basic macro for a while now, and I LOVE It!! I typically 3 box (monk/bst/cleric), and lately I've been joined by other players. I need some help tweaking the macro a bit to make this work when others join me.
1. is there a way to make the macro /if statement check the class before attempting to heal? if the other player says "heal" in grp, the bst will stop attacking and try to heal (and i don't want that). i send a tell to the cleric (via EQBC) to heal me to overcome this.
2. Is there a way to make the macro auto accept items in the trade window? I keep the monks weight down by passing loot to the cleric. this would keep me from constantly switching screens.
thanks in advance
Macro
Fri Jan 20, 2017 9:58 am
I'm not in front of the game and I'm rusty so this may not be right, try testing it with an /echo in game. Something like this though:
/if (${Me.Class.Name.NotEqual[Cleric]}) /return
/echo the variable from your cleric and from a non-cleric to make sure the syntax is right:
/echo ${Me.Class.Name.NotEqual[Cleric]}
It should say FALSE on your cleric and TRUE on a non cleric if it's right. For the trade accept thing, look to your resurrection code in the macro as an example. It would function very similar. The Rez code basically checks to see if the Rez window is open and then clicks the yes button if it is.
/if (${Me.Class.Name.NotEqual[Cleric]}) /return
/echo the variable from your cleric and from a non-cleric to make sure the syntax is right:
/echo ${Me.Class.Name.NotEqual[Cleric]}
It should say FALSE on your cleric and TRUE on a non cleric if it's right. For the trade accept thing, look to your resurrection code in the macro as an example. It would function very similar. The Rez code basically checks to see if the Rez window is open and then clicks the yes button if it is.
Last edited by Maudigan on Fri Jan 20, 2017 3:58 pm; edited 2 times in total
Fri Jan 20, 2017 3:52 pm
Project Lead
http://www.macroquest2.com/includes/wassup/manual.php#tlowindow
Check that out. It's the documentation on the Window TLO, also read about the /window command. It'll help identify the window names. I'm not 100% sure but you might be able to derive the window/button names from looking at the EQ user interface XML files... not positive on that but it would make a lot of sense, you could confirm it with the Rez window/button name first since you know them already.
Check that out. It's the documentation on the Window TLO, also read about the /window command. It'll help identify the window names. I'm not 100% sure but you might be able to derive the window/button names from looking at the EQ user interface XML files... not positive on that but it would make a lot of sense, you could confirm it with the Rez window/button name first since you know them already.
Fri Jan 20, 2017 3:55 pm
Project Lead