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

Mesabo · Post by **Mesabo** » Tue Sep 28, 2004 5:08 pm

Link to download doesnt work anymore.

Lost mine and was gonna grab it from there.

Can still get the code from the post but just letting you know your link is busted.

loadingpleasewait · Post by **loadingpleasewait** » Tue Sep 28, 2004 5:14 pm

hehe, yeah, the first thing I tried for agro detection was TargetOfTarget and was also dissapointed when I realized how situational it was. Oh well, this works, its not great, but it works..

The downside is figuring out when you've actually lost agro, in my autojolt it doesnt matter as I dont stick behind or anything in my macro. But, in rh.mac you'll want to know when you've lost the agro.

My best suggestion is /assisting the mob when agro is detected then compare the target with your name and then return to the target you were attacking. Thats the only thing I can think of that would always work.

Jerle69 · Post by **Jerle69** » Tue Sep 28, 2004 11:22 pm

Yeah, the loss of aggro is the tough thing. I just assume if you got aggro, you'll have it for 5 seconds, minimum... after that clock expires, it resumes thinking you no longer have aggro. Of course, if you're whacked at any time, the clock resets. Basically, RH says "Hrmm, I haven't been hit for 5 seconds... I guess the coast is clear!" and wades back in.

Jerle69 · Post by **Jerle69** » Tue Sep 28, 2004 11:24 pm

I just tested the download link and it's working. I sure hope so many people haven't downloaded it that the public download bandwidth quota on sharemation is used up. Can someone else try and let me know? If I have to, I can host it somewhere else.

Mesabo · Post by **Mesabo** » Thu Sep 30, 2004 4:26 pm

It's working again.

Thanks !

Random() · Post by **Random()** » Fri Oct 01, 2004 3:02 am

IMO the Check_Behind sub looks too rigid. I haven't tried it but

Code: Select all

Edit - Did that wrong; will update.  Should teach me not to post crap at 3am without testing.

would seem a bit more natural by giving a 4 hour window of opportunity behind the victim instead of dead frigging on all the time. *I do not know what the window is, in EQ, for rogue BS's however - so that 4 hours might need tightened up.

DrmChld · Post by **DrmChld** » Fri Oct 01, 2004 11:24 am

Any way to stop the macro from circling around the mob like mad when it gets aggro?

Knight · Post by **Knight** » Fri Oct 01, 2004 8:47 pm

Any way to stop the macro from circling around the mob like mad when it gets aggro?

I could understand this question if the answers to the exact same question were buried in the thread somewhere...but when it's on the same page you posted on, with people discussing it...c'mon.

DrmChld · Post by **DrmChld** » Fri Oct 01, 2004 8:51 pm

Sorry... I see nothing regarding this except for checking the assist of the mob to see if it matches myself...

I checked back and read through the 22 pages.. Maybe I missed it... twice.

Only thing I found was regarding have the misses turn on...

GD · Post by GD » Fri Oct 01, 2004 10:48 pm

http://macroquest2.com/phpBB2/viewtopic ... &start=328

-------
Warning, use of logic may be habit forming.

DrmChld · Post by **DrmChld** » Fri Oct 01, 2004 11:10 pm

why thanks.. GD...

I had made this change... but after a few times of pounding my head against the kb I realized I had hitmodes turned on..

Jerle69 · Post by **Jerle69** » Sat Oct 02, 2004 12:42 am

Random():

Check_Behind uses a "four hour window of opportunity" as you phrased it. If you use a 6 hour window, backstab will fail quite a bit. 2 - (-2) = 4, and the loop checks from -2 hrs to +2 hrs sweep. If you make it -3 to 3, that's 180 degree arc, and as I mentioned, this doesn't work well in practice.

As far as Check_Behind being crude since it's based on clock headings instead of trigonometric degrees (that hasn't been brought up yet), I don't think I'll argue; however, much like the old issues of significant digits when caluclating floating point precision from input measurments that are very crude -- I'd say it doesn't mean shit in the long run... -2 to 2 does the trick pretty well, is as accurate as necessary I think, and as a bonus, it's easy to get your mind wrapped around it. /Shrug

Libra · Post by **Libra** » Sat Oct 02, 2004 6:51 pm

Fixed my problem by deleting RH files and downloading new versions, I probably fubared something by playing with settings.

For those of you having the problem with chat commands not working, do what I did. (Example: /mainassist not being recognized, and real EQ chat telling you to use /help)

Flebbit · Post by **Flebbit** » Thu Oct 07, 2004 9:46 am

Some stuff I add manually that I find useful, that more people may be able to get use out of.

/if (${doHideSneak} && ${Me.AbilityReady["Hide"]} && !${Me.Casting.ID} && ${Me.Sneaking} && (!${Me.Moving} || ${Me.AltAbilityReady[Nimble Evasion]}) && ${Me.State.NotEqual[BIND]} && !${Window[TradeWnd].Open} && !${Window[MerchantWnd].Open} && !${Window[BigBankWnd].Open}) /doability "Hide"

Without this change, when you are running it will send sneak and hide at the same time, which leads to hide being broken by movement so it actually takes two whole cycles of hide to automatically hide if you are moving, which makes for a big mess when pulling or training. With the addition it takes slightly longer to hide after sneaking but hide will never fail.

&& ${Target.Animation}!=32

I add this to the attack decision check - mezzed mobs are always in animation 32 whereas fighting mobs are constantly cycling different animations. This stops the problem where a mob that is below the assist threshold is mezzed, and once your current target is dead, the tank targets the mezzed mob to taunt and you immediately charge it and break mez.

${Math.Distance[${Target.Y},${Target.X}:${Spawn[pc ${mainassist}].Y},${Spawn[pc ${mainassist}].X}]}<35

I add this to the attack decision check as well - This says, if the mob is outside melee range of the main tank to hold off on attacking until the mob closes with the tank. This prevents the 'charge an incoming mob and end up tanking like a dork' problem. The 35 is a literal because I am too lazy to parameterize it.

The assist check also needs a !${strikeReady} on it, otherwise it reassists while you are moving into position, then checks strike timer and aborts strike because it's not ready. I think you already included that one though, I don't remember re-adding it to the latest version but figured I would include it just in case.

Random() · Post by **Random()** » Thu Oct 07, 2004 2:46 pm

Jerle69:

Yeh, saw that after I started checking it out. Only wrote it out on paper, handn't really attempted running it. Imo roguehelper is probably the best pre-packaged solution for any type of dps class, but it looks fishy if a zerker, bl, monk, etc is always dead on behind a mob.

Didn't know the 180~ arc would give trouble to a rogue. Tks for the heads up.

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

Spinning around mobs?

Some suggestions