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

Post your completed (working) macros here. Only for macros using MQ2Data syntax!

Moderator: MacroQuest Developers

Jerle69
a hill giant
a hill giant
Posts: 263
Joined: Wed Apr 28, 2004 3:26 pm

Post by Jerle69 » Sat May 29, 2004 10:28 am

Dirx:

That's pretty interesting info there.

You mentioned that you can move and hide (successfully). Off the top of my head, I think I recall an AA skill or two that allows you to reduce the amount of time between your last movements and when you can push the hide button; something to that effect. I'll go back and look tonight--I know I never bought that one. Is that what you're referring to? I can probably check for the presense of the skill *OR* not moving before executing a hide (negating the need for an INI setting).

You also said you smack the master when you return to him. Is the master an NPC? Or do you play on a PvP server? If the master is an NPC, leashing can be sorta weird (I haven't seriously tested that a great deal). If you play on a PvP server, I imagine all KINDS of weird things could happen with leashing, especially if the master is wounded (below the assist percentage threshold, assuming you got /autoassist on). You would more than likely attack the master if it's hurt and it's an NPC or you're on a PvP server. The only thing I could do to prevent such behavior is check the target prior to engaging, and NOT engage if the target is the master (and leashing is on). That'd fix your problems for NPC masters (or if you're on a PvP server).
--Jerle

dirx
orc pawn
orc pawn
Posts: 21
Joined: Fri Dec 05, 2003 1:00 am
Location: orlando

Post by dirx » Sat May 29, 2004 6:04 pm

I have nimble evasion maxed so I can hide while moveing its a passive ability. I am on a pvp server so its a pc that I am hitting. Thanks for the response I have been using the new version all day its working great. I just turned off leash for now. I was haveing the problem in a confined area mostly like a ldon when your master is very close to the fight.

Thanks,

Dirx

Jerle69
a hill giant
a hill giant
Posts: 263
Joined: Wed Apr 28, 2004 3:26 pm

Post by Jerle69 » Sun May 30, 2004 10:10 am

I'll patch a fix for you for use of RH on PvP; I'll try to test it by dueling my other character :) Thanks for the feedback.
--Jerle

TrippyTom
a lesser mummy
a lesser mummy
Posts: 75
Joined: Sun May 30, 2004 10:18 am

Post by TrippyTom » Sun May 30, 2004 10:20 am

Can you explain exactly how the /drag command works? The info in the file doesn't really go into detail. Normally, on raids I use the overhead camera tilted slightly so i can get a better angle and just spam click corpses.

Would this make my life easier?
May the eclipse of your soul never fade to light!

A_Rogue00
orc pawn
orc pawn
Posts: 15
Joined: Mon May 31, 2004 6:03 am

Auto Hide/Sneak

Post by A_Rogue00 » Mon May 31, 2004 6:12 am

I decided to change this myself, but figured you might want to know about it so you can change it for the official one as well. When using this macro with auto hide/sneak enabled, it doesn't always work because it will hide first then sneak. This fails almost everytime with levitate and also when zoning into some zones (like BoT, where you fall a bit when you pop in). Swapping them greatly increases the chances of it working 99% or more of the time.

Also, can you make it so when you manually unhide it won't immediatly rehide? I like to unhide to make it do the clickie routine, but that doesn't work unless I disable autohs momentarily. That's all and thanks for this great macro! :D

Original code:

Code: Select all

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

     /if (${doHideSneak} && ${Me.AbilityReady["Hide"]} && !${Me.Casting.ID} && !${Me.Moving}) /doability "Hide"
     /if (${doHideSneak} && ${Me.AbilityReady["Sneak"]}  && !${Me.Casting.ID}) /doability "Sneak"
Swapped them:

Code: Select all

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

     /if (${doHideSneak} && ${Me.AbilityReady["Sneak"]}  && !${Me.Casting.ID}) /doability "Sneak"
     /if (${doHideSneak} && ${Me.AbilityReady["Hide"]} && !${Me.Casting.ID} && !${Me.Moving}) /doability "Hide"
A_Rogue00 says 'Stop Thief! <Sony>'

Jerle69
a hill giant
a hill giant
Posts: 263
Joined: Wed Apr 28, 2004 3:26 pm

Post by Jerle69 » Mon May 31, 2004 11:29 am

Sure, I can swap the hide and sneak code for the next release. You're certainly right, levitation tends to screw that up a bit.

As far as putting in a hide and sneak timer if manually disabling hide and sneak to execute a re-click, I've thought about that myself. However, all I have to do is hit my hide button once and it'll recast any spells that have fallen (if not in combat). It does so before the hide re-engages for me (with /autohs on). This doesn't work for you?
--Jerle

Jerle69
a hill giant
a hill giant
Posts: 263
Joined: Wed Apr 28, 2004 3:26 pm

Post by Jerle69 » Mon May 31, 2004 11:44 am

TrippyTom:

Drag is very dumb corpse dragging tool. While RH is running, you can type "/drag Playername Anotherplayer Someoneelse ..." and it will loop targetting all the corpses of those players in sequence and executing /corpse statements on each with a slightly less-than-half second delay between /corpse statement executions.

In other words, say Jim, Biff, and Mary are playing with you and all wipe out (you Escape of course) and consent you. You get near their bodies and type:

Code: Select all

/drag Jim Biff Mary
After you hit enter, you'll see RH targeting each of their corpses, and dragging them to you in sequence. You're free to move to the zone in or wherever they'll be rezzed. When you're at the location you want the corpses finally deposited, just hit F1 (or whatever your self-targeting key is) and you'll stop dragging their bodies around.

That's all there is to it.
--Jerle

Jerle69
a hill giant
a hill giant
Posts: 263
Joined: Wed Apr 28, 2004 3:26 pm

Post by Jerle69 » Mon May 31, 2004 11:55 am

Dirx:

I put an attempted fix for your leash master issue on PvP server in the 4.6 version of RH. Let me know if it fixes the problem.

Version 4.6 posted. Details are in the main post.
--Jerle

peaches
orc pawn
orc pawn
Posts: 10
Joined: Tue Oct 07, 2003 10:24 pm

Post by peaches » Mon May 31, 2004 2:46 pm

I would consider not dragging more then 2 corpses past anyone especially other rogues (or gms heh) because they will invariably ask you how you are doing it.

btw this macro is really great! Thanks

Jerle69
a hill giant
a hill giant
Posts: 263
Joined: Wed Apr 28, 2004 3:26 pm

Post by Jerle69 » Mon May 31, 2004 3:20 pm

I partially agree with peaches here. Most people cannot drag more than one or two corpses without making many mistakes and leaving bodies behind. For this reason, if you decide to drag more than one body with the /drag command, do yourself a favor and at LEAST run backwards to wherever you're dragging the bodies. It is feasible to drag very many corpses by left clicking on them while running backwards (away from them), so at least you look like you're doing something legitimately.

Running forward, not facing the bodies, and dragging 72 of them behind you is awfully suspicious. Further, at one time, I didn't have a /delay statement in between /corpse and subsquent targeting of the corpse list. Oh boy, I'll tell you sucking up 20 bodies to you in one second sure sends a stupid-macro-user signal out fast (both to observers and the server itself), so I put that delay in there for your protection.

Thanks for enjoying it!
--Jerle

Jerle69
a hill giant
a hill giant
Posts: 263
Joined: Wed Apr 28, 2004 3:26 pm

Post by Jerle69 » Mon May 31, 2004 3:25 pm

Does anyone want or think they'd use an auto-duelist type feature if it were written? Also, should it use a different endurance floor than the percentage used for automatic strikes? If it were written, do you think there should be other mitigating circumstances in which you'd want the duelist disc to automatically execute. I'm leary of writing any auto-duelist because of the high reuse delay as well as the limited need for the autoexecution of something as "precious" as this burst of power. I feel this skill is a manual override for emergencies -- autopiloting and emergencies are, to me, opposites.

What do you think? I'm willing to go with popular opinion here and write it if people want it.

Thanks,
--Jerle

peaches
orc pawn
orc pawn
Posts: 10
Joined: Tue Oct 07, 2003 10:24 pm

Post by peaches » Mon May 31, 2004 4:50 pm

Personally I like to hold onto duellist until I know I can get full use out of the disc. Auto deadly precision might be better.

For some reason when using the macro I always take my assassin's strike attemp before I am at the mob so it always gets wasted... It doesn't wait for me to get in bs range. Am I using the macro wrong?

mystic
a lesser mummy
a lesser mummy
Posts: 33
Joined: Mon May 31, 2004 5:33 pm

Post by mystic » Mon May 31, 2004 5:36 pm

read the post before on this, but im still having the prob. when i type /autoassist tanknamehere 90 it still autoassists at 100%. the tanks name is correct, it's just not sticking through

Jerle69
a hill giant
a hill giant
Posts: 263
Joined: Wed Apr 28, 2004 3:26 pm

Post by Jerle69 » Mon May 31, 2004 6:11 pm

Peaches: I agree. At my stage of the game, if I'm behind a mob, I rarely miss anyway. The only discs I find useful are duelist, deadeye (massive AC mobs or fighting from front) and strike. The rest don't find much use. Are you sure you removed /attack on from your assist macro? If your assist hotkey reads something like this:

/assist whoever
/echo Seeking a Victim...

... you shouldn't have problems. If you have an /attack on statement in your macro, strike will be blown immediately or fail to fire due to not being in hide/sneak.

If that's not the case, make sure your "closeness" setting is low enough that you're in range before trying to backstab. Try /closeness of 30 to 50 and see if that fixes your problem (assuming you don't have /attack on in your assist hotkey).

Mystic: I can't imagine why the macro would autoassist at anything less than the assist percentage you specify. Here's the code that starts it all:

Code: Select all

         /if (${Target.ID} && ${Target.Type.Equal[NPC]} && (${Target.PctHPs}<=${assistpct})) { 
           /echo --> Assisting ${mainassist} on ${Target.CleanName} @ (${Target.PctHPs}%) HPs 
           /echo Seeking a Victim...       
         } 
From this, you can see it won't echo "Seeking a Victim..." unless you 1) have a target, 2) it's an NPC and 3) it's health is less than that which you specified in the autoassist. The only way that autoassist would trigger on a fully 100% health NPC is if you set the assist health percentage to 100, OR you actually mash a hotkey that echo's "Seeking a Victim..." If you're doing that, then yeah it'll autoassist immediately (that's a manual override or a manual assist). Other than that, I have NO idea why it'd fight before the mob getting to the assist percentage first. Do make sure you have the latest MQ2 installed; RH uses MANY of the newest features.
--Jerle

mystic
a lesser mummy
a lesser mummy
Posts: 33
Joined: Mon May 31, 2004 5:33 pm

Post by mystic » Mon May 31, 2004 6:18 pm

[General]
AutoAssist=TRUE
MainAssist=tanknamehere
AssistPercentage=90
AutoHideSneak=FALSE
Leashing=FALSE
DynamicAggro=TRUE
LeashHolder=Nobody
LeashLength=100

is what i have it set up as, but the second the specified tank targets something the rogue darts after it no matter where it is. i put a leash on so he would stop running into the middle of poearth, but it still auto attacks at 100%. exactly what i type in is /macro rogue, then /autoassist tank 90.
have the newest everything installed atm.