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

TrippyTom · Post by **TrippyTom** » Sat Jun 12, 2004 3:57 am

Um... Tranze, just use /leash 500 (or any number) and it will go back to the spot you were at when you entered the command. It doesn't have to be a leash on a person.

tranze204 · Post by **tranze204** » Sat Jun 12, 2004 10:51 am

yea sorry bout that my macro wasnt working correctly...but it works now thanx...leashing has been having some errors every now and then..just giving ya a heads up on it to see if u can spot the problem

Jerle69 · Post by **Jerle69** » Sat Jun 12, 2004 11:03 am

Tranze204:

Hey i have another suggestion...not to sure if ya can do it or not but here it goes...a /anchor command so that it saves u current loc or something and will return to that spot...the /leash command is good but pisses people off alot, they think u are some kind of perv that needs to like breathe on them...just an idea

and...

yea sorry bout that my macro wasnt working correctly...but it works now thanx...leashing has been having some errors every now and then..just giving ya a heads up on it to see if u can spot the problem

I don't want to sound haughty, but in two weeks nobody has reported any leashing errors. You say you have some "errors now and then" (with no details that I could use to figure out how to track down and fix these errors); also, you didn't know about the leash staking when you made your original post. Appreciate the "heads up," but I'm going to assume user error unless you post some of the errors MQ2 is generating when RH is behaving poorly "now and then."

Thanks,

oorglebot6000 · Post by **oorglebot6000** » Sun Jun 13, 2004 1:08 pm

Heya Jerle69, excellent macro that you have here. I've been using it on my rogue since I saw the initial post (most likely the first version). Lately I have run into a few problems, namely with hide and sneak. I am not sure if it is due to my connection instability or something innate with the macro, but whenever it tries to hide or sneak, I frequently get a message related to the retimer on the server not being set yet for hide or just plain no message of sneak working (and thus it fails). I made a few changes to the code to fix this, and I have found that this works pretty smoothly for my purposes. Namely, the changes I made are that it doesn't do both hide and sneak at the same time, but it only hides after it sees a successful sneak.

Also, I am a rogue with nimble evasion 5, and I am able to hide while running,as long as sneak is on, and evade works while running regardless of sneak. I also changed the code to support this. The final change I made is so that the auto-evade stops working automatically when your target's health gets below 20% so that you are able to get to hide/sneak after the fight much quicker.

This is the nimble evasion and no evade below 20% health fix - changed this line

Code: Select all

/if (${doEvade} && !${Me.Moving} && ${Target.ID} && ${Me.AbilityReady["Hide"]}) {

to this

Code: Select all

/if (${doEvade} && ${Target.ID} && ${Target.PctHPs}>=20 && ${Me.AbilityReady["Hide"]}) {

For the sneak/hide bug fix, I added this event to the current list,

Code: Select all

#Event Sneak	       "#*#are as quiet as a cat stalking its prey#*#"

with this variable near the top of the main.

Code: Select all

  /declare temp int outer

and this code at the very bottom.

Code: Select all

Sub Event_Sneak
	/varset temp 1
/return

Then go to the top and search for

Code: Select all

     |- Lets hide and sneak if not already and we're set to do so **

and replace these lines:

Code: Select all

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

with these:

Code: Select all

     /if (${doHideSneak} && ${Me.AbilityReady["Sneak"]} && !${Me.Casting.ID} && ${Me.State.NotEqual[BIND]} && !${Window[TradeWnd].Open} && !${Window[MerchantWnd].Open} && !${Window[BigBankWnd].Open}) {
	/delay 2
	/doability "Sneak"
	}
     /if (${doHideSneak} && ${Me.AbilityReady["Hide"]} && !${Me.Casting.ID} && ${Me.State.NotEqual[BIND]} && !${Window[TradeWnd].Open} && !${Window[MerchantWnd].Open} && !${Window[BigBankWnd].Open} && ${temp} == 1) {
	/doability "Hide"
	/varset temp 0
	}

Notice I have the /delay 2 before sneak, this was kinda key in preventing sneak from failing for no apparent reason. I know it wasn't the server timer issue because it was failing for me after battles as it would try to use it after a minute of no use. You can try to remove it to see if you get this issue.

I ran into problems where the mob would enrage, the macro would turn on sneak and set the temp var to 1 but not be able to hide due to the timer not being met... then I would turn on attack before it would hide me and after the fight was over, it would still have the var set to 1 and try to hide without sneaking first. I think the best way to prevent this would be to make it not sneak on enrage, but I hadn't thought of that until now when I questioned why the following code was here, and I wouldn't want to post any changes to code that I hadn't tested myself. Anyway, my fix was to make it cancel the queued up hide upon attack being turned on, so find the lines with

Code: Select all

Sub Event_AttackOn
  /echo Autoattack activated! Target: ${Target.CleanName}
/return

and add

Code: Select all

	/varset temp 0

just below the echo

P.S. This is my first change to a macro other than deleting all of the parts that I never needed, if you can think of a better or more efficient way to do what I did, please tell me how.

Jerle69 · Post by **Jerle69** » Mon Jun 14, 2004 5:38 pm

oorglebot6000:

Just a couple of inputs. I like your "stop evading if target is below 20%" code so that you can get off hide and sneak faster after a fight. I suppose that makes you "safer quicker." I'll put that in the baseline tonight if I can remember to do so.

As far as only hiding while successfully sneaking, and creating an event condition based on a successful sneak, I'm not sure why you have to do this. You're very right that you will hide if your sneak is on, and you can pretty much sneak whenever it's available. If you're experiencing a bit of lag, the delay between sneak and hide should be all that's needed to force a sneak success prior to hide; however, to be totally honest, I'm not sure why you'd want to or have to have sneak on to hide--they're really mutually exclusive skills that work together for a rogue to allow you to move while invisible, but one doesn't mandate the use of the other, really.

I'll do some testing with it tonight (if I get a chance) and see what I can do to make it better.

oorglebot6000 · Post by **oorglebot6000** » Mon Jun 14, 2004 11:06 pm

You don't have nimble evasion, do ya? :)

With nimble evasion, you can turn on hide whenever you are moving, but it only works if you are sneaking. I find it is very helpful, because if I just finish fighting a mob, I can immediately start running off and expect both to work. If I hit hide, then sneak, or both at the same time, the server doesn't think that you were sneaking, so it fails on the hide unless I stand still. It is also helpful on zoning in when you are slightly raised above the ground, because it will wait until the server recognizes you are sneaking, which is usually enough time to land to the ground for non-nimble evasion rogues. Maybe it should be an option for rogues with nimble evasion? I dunno... see if anyone else says if it helps or is annoying - I'll be adding the code to any version you release regardless.

Jerle69 · Post by **Jerle69** » Mon Jun 14, 2004 11:20 pm

I don't have nimble evasion, but I do understand how it works. The reason I don't have it is because I didn't think it'd be very useful--I could be wrong. It's just that I don't really find myself needing to "hide right now now now.. the mob is dead.. move move move!" It just never seems to be an issue for me, so I never bothered. Your code mods are certainly useful in the situation you describe--I just never seem to actually *be* in that situation.

Just curious, when exactly do you find that you need to immediately motor post combat and still require hide and sneak? Or is this just a convenience issue that you wish guaranteed hide/sneak regardless of situation immediately... I'm guessing the latter.

oorglebot6000 · Post by **oorglebot6000** » Mon Jun 14, 2004 11:53 pm

Well, I added this in mainly because I'm still an active player that moves frequently (FPS gamer as well... hehe) . Since I had nimble evasion 5, I may as well have made it so it would turn on hide/sneak while running, and this was the best way I could think to implement it. One of the main reasons though, is that I am frequently in fast-paced groups that pull quickly, and being hiden quickly means being able to use AS quickly.

Either way, I highly recommend getting nimble evasion soon. I got it when I was about 80 some AA's and I just broke 200 the other day - still havn't regretted getting it that early.

Jerle69 · Post by **Jerle69** » Tue Jun 15, 2004 10:19 am

I got a couple hundred and still don't have it

I'll look into it.

Programmer · Post by **Programmer** » Tue Jun 15, 2004 12:12 pm

I've got nimble evasion 5, but haven't paid attention to this theory I've got. I'm sure every experienced rogue has had evade faulires because the server complained you could not hide while you were moving, right? I theorize that nimble evasion can put an end to that. I don't know, but it makes sense to me.

oorglebot6000 · Post by **oorglebot6000** » Tue Jun 15, 2004 12:15 pm

In reality, nimble evasion does have a chance to fail whenever you are sneaking+moving and press hide... that chance is extremely small. I see it happen like once every 3-7 days.

dirx · Post by **dirx** » Tue Jun 15, 2004 6:22 pm

I love nimble evasion most of the advantages are in combat. If you get jostled around or you are in water you wont fail your evade due to movement. Plus after you have it for a while and get used to hideing while moveing it makes you feel very ninja like hehe. I just yank out the movement checks in the script each update and it works fine. With the movement checks in place the macro almost never evades when you are fighting in the plane of water. I also waited a long time to get that one but its only 5 aa and it almost never fails. I wish I had gotten it earlier as well.

Thanks,

Dirx

Jerle69 · Post by **Jerle69** » Wed Jun 16, 2004 2:20 pm

Everyone:

Yep, I agree. I did some more testing and tossed 5 points into Nimble Evasion. You're right, it's very helpful. I'm going to augment RH to do a couple of things in the next little patch:

All evade and hide checks will fire if you have Nimble Evasion OR you're not moving (instead of just checking to see if you're standing still). This should accomodate those that have NE and want hide and evade to work while moving around (or swimming, bobbing, levitating, etc.) and those who don't have NE yet, and can only evade/hide while still.

When swimming, I'll have a conditional insertion of actually looking at the target you're trying to strafe around to engage; this should allow for RH to autostick correctly while you're in water (a.k.a. 3D combat abilities). Currently you can easily be wrong in the Z-Axis, but this little patch should fix 3D combat.

Look for it in the next day or so, or perhaps even tonight. These are minor upgrades.

Later,

TrippyTom · Post by **TrippyTom** » Thu Jun 17, 2004 11:27 am

strange... RH.mac is making me LD when it reaches the part "seeking a victim..."

I didn't change anything! Just not working with new patch for some reason.

blaham · Post by **blaham** » Thu Jun 17, 2004 11:42 am

TrippyTom wrote:strange... RH.mac is making me LD when it reaches the part "seeking a victim..."

I didn't change anything! Just not working with new patch for some reason.

it's doing the same thing for me.