Rogue Helper v6.0 [Complete Rogue Macro] (Updated: 10-26-04)

burdsjm · Post by **burdsjm** » Wed Jul 21, 2004 6:43 pm

Cool Jerle. Looking forward to the next update.

OnyxSys · Post by **OnyxSys** » Thu Jul 22, 2004 4:25 am

The Absolute best Rogue Macro ever! Keep it up this rocks!

spida · Post by **spida** » Fri Jul 23, 2004 3:08 pm

On the dragging idea:

Considering the proposed upcomming addition of "/consent raid", maybe looking through the current raid for players in raid and dragging only the valid corpses might be one idea. Maybe /drag raid in addition to being able to list single corpses.

I would love that I am sure.. :) Just throwing out one idea...

thanks
spida--

Jerle69 · Post by **Jerle69** » Sat Jul 24, 2004 8:55 am

I may wait to enhance /drag until those changes are live. They could implement mass dragging for rogues as part of the normal client, invalidating any work I may do now.

Knight · Post by **Knight** » Sun Jul 25, 2004 10:09 pm

On line 843 the code is:

Code: Select all

 /if (${Ini[RHSettings.ini,General,TargetSwitching].NotEqual[NULL]}) /varset doTSwitch ${Ini[RHSettings.ini,General,TargetSwitching]}

However, on line 1639 the code is:

Code: Select all

/ini "RHSettings.ini" "General" "AutoTargetSwitch" "${doTSwitch}"

In other words, the Target Switch setting is not reading in correctly. To keep in line with the rest of the code replace "TargetSwitching" in line 843 with "AutoTargetSwitch" such that line 843 is:

Code: Select all

/if (${Ini[RHSettings.ini,General,AutoTargetSwitch].NotEqual[NULL]}) /varset doTSwitch ${Ini[RHSettings.ini,General,AutoTargetSwitch]}

p.s. Great macro

Jerle69 · Post by **Jerle69** » Tue Jul 27, 2004 1:52 am

Oh shit, good catch! I thought I noticed it not keeping the target switching state settings from execution of RH to subsequent execution. Good bug catch man... I'll fix that in the next release.

FYI, I can't do the next release until MQ2 is fixed. Right now AltAbilityReady TLO is non-functional, and half of the new changes involve this object =(. When that's working, I'll do the new stuff.

Oskar · Post by **Oskar** » Tue Jul 27, 2004 12:28 pm

I was trying to use this to Kite in Fire and it kept stopping the follow routine. Is this due to the problems with MQ2 not working or some other issue?

NM - I figured it out. I had to employ the /stickdist command.

Jerle69 · Post by **Jerle69** » Sat Aug 07, 2004 8:31 am

Just as an FYI, I'm not dead. Also, the AltAbility TLOs aren't working yet (last comment implied they may never work again). Since the AltAbility features are disabled, the new stuff can't be implemented (and the NimbleEvasion code is blithly ignorant now too, so you won't autohide while moving if you have Nimble Evasion -- /sigh).

We'll just wait and see what happens. If the devs see fit to repair the AltAbility stuff, I can press forward with the additional features.

Hasta,

Knight · Post by **Knight** » Sat Aug 07, 2004 9:18 am

Well, they are working on it...but the AA change was such a major revamp that it's going to be a bit of time. Magelo's having the same issues.

cybersnac · Post by **cybersnac** » Sat Aug 07, 2004 4:22 pm

I've just recently starting having problems with the command

/autoassist <mainassist> <percentage>

It seems that no matter if I type it in game or specify it in the .ini file it always attempts to run out and assist at 100%.

This wasn't happening in the past, is anyone else having this problem?

Any suggestions? There are no error messages to post and the macro continues to do everything else completely normal.

Buuford · Post by **Buuford** » Sat Aug 07, 2004 7:19 pm

dude, cybersnac, sorry, but you have to read the entire thread if you're going to continue to use these forums. Otherwise people will seriously bust on you.

Here's your sign

cybersnac · Post by **cybersnac** » Sat Aug 07, 2004 10:24 pm

Thanks for the subtle warning, dude. Actually, I've already read that part of the thread and have already tried that, no go.

Any other suggestions, anyone?

escapegoat · Post by **escapegoat** » Mon Aug 09, 2004 10:34 am

Heyas,

This continues to be the best rogue macro out there and I've been using it to bot my rogue for dps for a while now without any real issues. Today however I was in Kael helping someone do factioning and the rogue seemed to be having a problem with range/distance from the giants there. Closeness is set to default of 70% (as it always has been) and I tried using rh.mac version 5.6 (with and without MQ2Moveutils loaded) as well as version 5.4. In each scenario rogue would auto assist correctly but then position himself behind the mob too far away to actually hit it but continue with strike/autoattack as if it thought it were in range. Anyone else have any problems with certain mobs/zones? This is the first time I've noticed anything of the sort. Afterwards I went to some other zones and killed other stuff and it functioned perfectly fine again. Any guesses as to what the problem might be?

EG

Jerle69 · Post by **Jerle69** » Mon Aug 09, 2004 11:53 am

cybersnac:

Please double-check your /assist command. You must manually enter /assist off at least once before using RH, or it'll charge off at 100% all the time (exactly as you describe). The reason for this is you must still close in on a mob when activating a strike disc, and RH doesn't know if it's about to strike or if it's actively in combat. One this is sure, once you have autoattack on, it WILL close in on a target, regardless of it's health.

Depending on your UI, the clue here to look for is the flashing red box around your player info window. If it's flashing and the mob is healthier than your percent health setting for /autoassist, you don't have the EQ "/assist off" setting set. It's either that, or you're hitting your attack key ("a" by default, or whatever you've rebound it to).

Also, don't confuse /assist off with /autoassist off. /assist is an EQ command... /autoassist is an RH command, and they have nothing to do with each other.

If you go back and make sure you have your /assist set to off, and you still have this behavior, I'd recompile MQ2 and get a new copy of RH, and then post back with some more details.

escapegoat:

Yeah actually I think the Kael giants issue was posted in this thread once. For Kael, the "within range to hit" distance for giants as reported by MQ2 is not the same as the actual range you must be from a giant to hit it. RH uses the information provided by MQ2 to acquire the proper range, so if the value according to MQ2 is wrong, so it will be with RH. The only workaround for this is to set your /closeness to a smaller value.

For Kael, people have said (I think) that /closeness 30 works nice there. Just toy around with that value (smaller for Kael, larger for other places) until it's working for you.

A_Druid_00 · Post by **A_Druid_00** » Mon Aug 09, 2004 12:55 pm

Jerle, alternatively, you could have RH turn off attack on assist when it is first activated. I know that Vexix does this with Genbot. At the very least it will save you the trouble of having to answer questions like this!

Rogue Helper v6.0 [Complete Rogue Macro] (Updated: 10-26-04)

autoassist percentage problems