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

episix · Post by **episix** » Thu Oct 28, 2004 10:17 pm

episix:

Back around version 4 or so, this was written this way (it used to not account for nimble evasion). If you don't have nimble evasion, I'm not sure why the code is trying to hide and sneak for you, unless paren parsing is somehow screwed up in MQ2.

Do me a favor and type this in, next time you're bored:
Code:
/echo ${Me.AltAbilityReady[Nimble Evasion]})

It should say FALSE for you. If it says NULL, let me know, please. If so, I may have to adjust some code in there, but last I checked NULLS were evaluated as a FALSE insofar as boolean comparators went, so even if it is a null, I'm not exactly sure why that expression doesn't perform correctly in your case--it's logically and syntactically correct.

The echo comes up TRUE...but I do not have the Alt Ability.

Dunno whos part the error is on.

Cr4zyb4rd · Post by **Cr4zyb4rd** » Fri Oct 29, 2004 2:23 am

I'll put this on my list of things to poke at tonight while I'm testing stuff. Not sure if my testing rogue has the ability or not.

Jerle69 · Post by **Jerle69** » Fri Oct 29, 2004 3:12 pm

episix:

That's not good. If that echo comes up TRUE, and you don't have the ability, it's bugged in MQ2. I'll see how my enchanter responds to the echo and see if he "has" nimble evasion also.

Cr4zyb4rd · Post by **Cr4zyb4rd** » Fri Oct 29, 2004 4:04 pm

Dunno...strictly speaking is the behavior defined for abilities you haven't bought yet? Maybe due to the way they're checked they appear "always ready". Maybe check with just ${Me.AltAbility[x]} first?

Jerle69 · Post by **Jerle69** » Fri Oct 29, 2004 5:33 pm

Cr4zyb4rd:

That's a valid philosophical view of something that's not defined, but I'm sure it used to return NULL if you didn't have the skill (or this would have appeared broken, long, long ago). I think perhaps something changed in MQ2 recently with the AltAbility revamp.

I'll try to address this one soon.

ALL:

Just as a heads up, I've already put in a few things for v6.1 including:

Loadingpleasewait's filter against pets, corpses, and other players when choosing a target via cascading assists.

A check against moving or casting before re-engaging stick, assuming autostick is on (this allows you to manually override stick movement instead of having RH rewrench control from you constantly.

A small iclick timer to indicate to RH that an iclick was just performed (this allows ibounce to differenciate between a bounced spell that *IT* encountered from a keepup item vs. you doing something stupid like manually click an item (or /cough /cough, for other's using RH's engine) it will protect them from casting spells that bounce off sending RH into a spiral of spam.

I'll keep tweaking the little 6.0 bugs out and turn out 6.1 in a bit... I'm secretly hoping for BuildDate to get stuck in MQ2 soon :) I also have to look into this AltAbilityReady business.

Cr4zyb4rd · Post by **Cr4zyb4rd** » Fri Oct 29, 2004 5:44 pm

Oh philisophically I'm firmly in the camp that it should return NULL or at least false if you don't have the ability. I just don't know if that's the case or not :)

MeGoober · Post by **MeGoober** » Fri Oct 29, 2004 7:50 pm

I was't quite sure how to implement the check for corpse, petc, etc. Once for each Assist? or before/after the assist selection? I know I would really like it now. It was @!#$ irritating last night when the stupid ma was not engaging but afk looking at the dead friggin mob, the SA was like..."you going to join the fight?". I just paused the macro and went on manual until ma returned.

I have also gotten hit running thru a zone when sneak/hide was up and I went to drag a body. At first it seemed it happened bacause the tank I was autoassist on attacked a mob while i was away, I got the target window for the mob, and I thought I might have gone into attack mode even though I was a long way off. But reading the thread it may have been because I only have one rank of evasion. Buying it up now. No...I have all 5 ranks. I confirmed last night: I am outside of the attack range - by a lot and pop, my strike ability pops on. I am losing sos halfway across the zone dragging bodies because the ma is still fighting.

Another issue. I was helping a cleric in AR with epic parts. I fell off the stairs...it would be nice if auto stick broke when you are no longer hitting the mobs; due to bad pathing, distance, stuck on the wrong side of the door, etc. Hmmm, that may be a moveutils issue?

Hmmm autopull could be useful. Then again it could get me dead or the group angry. I was just thinking if I took a bio break it wouldnt stop the group from continuing.

One last item? Anyone else having problems with the HUD since crayz's cleanup? BS is still working but the RH components are all red - wont go to green even though I confirmed RH is operated as designed and the component is enabled. (ie I turn on autohs - hud still has red autohs)

spitfire · Post by **spitfire** » Sat Oct 30, 2004 5:24 pm

for some reason i cant get it to auto backstab i have to manually do it. Also when it does assist it hits assassin strike but wont do anything else i have to manually backstab then hit attack. Anyway to have it auto backstab after assassin strik then turn auto attack? any help to fix my 2 problems would be great. thanks

edit: my noobness allowed me to figure it out all by my lonesome =)

Jerle69 · Post by **Jerle69** » Sat Oct 30, 2004 8:17 pm

I spent several hours writing the documentation :) The first couple of paragraphs in there under "IMPORTANT NOTICE" contained all the info you needed to get going right :)

DrmChld · Post by **DrmChld** » Sat Oct 30, 2004 9:17 pm

Ok... Got the autoclick to work... It wasn't in a bag. Who would have thought lol.

Ok... Now for a request :)

How hard would it to be to add something to make the rogue turn around and face away from the master/leash holder?

So it doesn't look like it is always springing back to the leash holder so obviously?

episix · Post by **episix** » Sat Oct 30, 2004 9:29 pm

For the not so smart of a macro coder, how would i modify this to NOT switch back to the beneficial weapon (Primal with avatar proc) if i have the spell Ferine Avatar on me.

Code: Select all

   /if (${doSwitch} && ${wstype.Equal[Beneficial]}) {
     /varset itemspellname ${FindItem[${weapon1}].Spell}
     /if (${itemspellname.NotEqual[${Me.Buff[${itemspellname}]}]} && !${FindItem[${weapon1}].InvSlot.Name.Equal[mainhand]} && !${FindItem[${weapon1}].InvSlot.Name.Equal[offhand]}) {
       /if (${verbosity}>=1) /${channel} ** Beneficial proc-weapon swapping...
       /call Weapon_Swap "${weapon1}" "${weapon2}"
     }
   }

Thanks in advance

loadingpleasewait · Post by **loadingpleasewait** » Sun Oct 31, 2004 12:52 am

is there any way to put a mezz check inside the fighting loop, so that if a mob you've already engaged gets mezzed, you'll stop attacking? I tried to do this myself, but failed miserably.. hehe

Ooh, and how bout some sort of autosit routine to help regain endurance..

And... just noticed this.. with leash set to a PlayerCharacter, if the leashholder has a corpse, sometimes it gets confused and leashes to the corpse.. trying to figure a way around this, while I have a test environment right now.. so far.. no luck.. (i need to read through yer macro more.. hehe)

MeGoober · Post by **MeGoober** » Sun Oct 31, 2004 5:27 am

Ok...I almost have the manual memorized word for word. I have reduced Stickdist to 50 100, even tried 25 75. I still get my Disc Activiation when I am way outside that range. Attack starts and SoS drops - no where near the mob. If I pause the macro when I intend to leave the proximity of the fight, I am ok. Just hard to remember sometimes.

With closeness set to 70 and stickdist set to 100 200. We engaged Rellos Zek in time and I went running right up his a...tail. I hit the back arrow key, nada, barely moving. I hit my pause macro hotkey...now I can quit attack and use the back arrow key to move out of the room. The moment I let go of the key...I go racing back to the fight. I try to sit down way on the other side of the big center room. Let go of the back arrow...I stand up and run. I try to turn autostick off but macro is paused. I reactivate the macro, type in autostick while holding the back arrow key. I stop trying to run in. I go back in..assume a close to max mellee range and cant tell if I am to far out now, so I expand my damage window to see if I have any OOR messages and sysem crashes. I log back in, dead. I only observe this occasionally, I don't usually try to back away from a mob, even manually unless its abnormal circumstances. Like when I fell of the steps and could not get the stick to break, it contantly pulled me back into a corner 30 feet below where the mob was - unable to hit it.

Still can't figure out why hud bs is working and simple colors wont register the RH status. Oh well.

-----------------

Ok...I am giving a shot at contibution. Don't laugh too much as I hurt myself...

Libra · Post by **Libra** » Mon Nov 01, 2004 6:48 am

Curious what changed with new version to make my computer freeze up while it is loading -- older RH (before the latest) would load up prettymuch instantly, this one takes around 10 seconds ( 10 seconds that my computer is frozen, and I'm unable to do anything )

loadingpleasewait · Post by **loadingpleasewait** » Mon Nov 01, 2004 8:21 am

its the version check that he jumps over during loading in hopes that the BuildDate TLO actually makes it into the source.

Pretty simple to put back in as he didnt actually referance the BuildDate TLO at all, but actually kept the version check the same as it has been, except that he jumps over it in the code.

To reduce loadtime, simply put a " | " before the /goto :BypassVCheck and the :BypassVCheck... Like so..

/declare rhversion string outer 6.0

| /goto :BypassVCheck
|- Check versions and load aliases if necessary
/if (${Ini[RHSettings.ini,General,Version].Equal[${rhversion}]}) /goto :EndAlias
| :BypassVCheck

/if (${verbosity}>=0) /${channel} Setting Aliases...
/squelch /alias /status /echo RH Status
/squelch /alias /rhhelp /echo RH Help
/squelch /alias /autoevade /echo Autoevade

Or, technically you could get rid of those two lines all together.