MacroQuest64

well, I have noticed what you are talking about but only when the rogue is way out of range WHEN the npc's health was low enough to start the fight. So when the rogue was out of range of the target when the health was low, it would just sit there even when I pulled the mob back. A little movement would restart the macro like you said. I just increased my leash range and I've never had that problem since

everything seems normal - except my rh mac

My leash is long enough and the target is right beside the the rogue - no autoassist nor leashing without manual movement

daveryann wrote:everything seems normal - except my rh mac

My leash is long enough and the target is right beside the the rogue - no autoassist nor leashing without manual movement

My point is this.

You are complaining that a macro is not working. Today. There is no released zip today. So you must have changed SOMETHING. This change most likely included the last available zip and some other updates.

In the patch notes for the last available zip there were some changes to else that are quite important and is quite possibly the source of your issue.

Sneak is on... but rogue does not hide...
Does not assist mainassist anymore
leash is all messed up

Was working fine up until the last update 7/15/05 patch... not sure what happened... any suggestions, ideas, comments? I cant 2box my rogue any longer =(

do you have hide on your rogues skill tab?

yea nothing was changed... it used to work fine... but since later eq patch and new Mq2 version.. its not working...

redownload the macro and redo your ini file. Did you compile the most recent mq2? The problem is something you've changed cause I've been having no problems and the only things I've changed are the ini files. The macro works perfect with the current eq/mq so what did you change?

skyler wrote:redownload the macro and redo your ini file. Did you compile the most recent mq2? The problem is something you've changed cause I've been having no problems and the only things I've changed are the ini files. The macro works perfect with the current eq/mq so what did you change?

skyler: $1 says you are not running latest zip from today.

Another tip:

You can write protect your ini file and type /macro rh whenever you zone. It might save a few keystrokes. (This will also lock in the settings just the way you like them.)

As a newb to the macro, I spent a while being stuped about why backstab wasn't working for me after I leveled my rogues to the point where they had the ability. It took a bit of reading to find what I was doing wrong. (Needed to go to the abilities page of my "Actions" panel, click on an emty spot, and add in the skill 'backstab' I think that detail might be a good thing to throw into the guide. (It was embedded about 20 pages into the thread, hehe)

I must join the masses in saying that this macro is absolutely amazing. The only time I need to touch one of my rogues is when I zone -and for playing 7 accounts at once... well, I wouldn't have rogues in my party if not for a script like this.

At the moment, I'm even using it for nonrogue classes. It's that good. If it were changed to do a regular stick instead of a stickbehind, it could be a godsend for just about any class. It's not surprising that RH has spinoffs. I see 'melee version of advbot'

Since the latest version of MQ2 came out... its not working im having same problems as many people in the last few pages of posts... leashing is not working... it wont assist, it sneaks but it wont hide... its all messed up... maybe something in the new Mq2 changed and now the code isnt working the right way??

In order to fix the RH.mac you need to go in and change all the
To a format that will work with the current version of MQ2, Like this
I am working on editing my RH.mac right now. I am only halfway done editing it but have most of the fuctions working just fine again. Including Autoassist, Hide, Sneak, BS. When i am done I will post what i have.

edit:

I stand corrected, a bug has been fixed which will change how /if { } else {} is handled.

Sorry... i dont understand... i went into the macro and i see what u want me to change... but i dont know exactly how to change it and not screw up the macro worse then it already is... real sorry

edit:

I stand corrected, a bug has been fixed which will change how /if { } else {} is handled.

Well too late, I read your flame :p. I'm curious though, did rh macro really run without making above mentioned changes? The melee macro I'm using had only one false else line and this was enough to malfunction it.

I actually don't run the stock zip anyway

I just updated to it and talked with dkaa in IRC, bug has been fixed, a number of macros are going to need worked on, but its minor.