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

taylojl · Post by **taylojl** » Fri Sep 24, 2004 2:57 am

none of the /commands i can get to work. /autoassist says bad command, iclick crashed macro for me. Any advice?

OnyxSys · Post by **OnyxSys** » Fri Sep 24, 2004 3:09 am

problem is that i found out is that RH.MAC isnt adding the /aliases to the macroquest.ini... as before it actually rewrote it everytime it loaded up hence the delay when you loaded up.. now it check's version but this time it didnt add to the macroquest.ini file

loadingpleasewait · Post by **loadingpleasewait** » Fri Sep 24, 2004 8:05 am

macroquest.ini has all your personal macroquest settings in it. I dont know about you, but personally I dont want to reset my settings everytime I update MQ. Henceforth, I do NOT delete/overwrite my macroquest.ini with the one included in the zip, and I would suggest you not to either.

To fix this, simply open your RHSettings.ini and delete the line about the version number, then the next time you load up RH.mac it wont find the version, and will then reload the /aliases. Problem Solved..

Next time MQ is patched, dont overwrite your macroquest.ini. :)

Jerle69 · Post by **Jerle69** » Fri Sep 24, 2004 8:30 am

All,

I think we had a discussion like this on page 21 (version 5.9 loads faster, but you gotta be tricky if you overwrite your MacroQuest.ini as loadingpleasewait said).

I poured over the MQ2 documentation and didn't find any obvious TLO that could spew out the current version of MQ2--if anyone knows a way to query that information, I can fix this "bug."

Thanks,

escapegoat · Post by **escapegoat** » Fri Sep 24, 2004 8:54 am

Great continued work here Jerle. I'm personally not having any problems with the macro causing TLOs or anything so I can't give any feedback on that bug. The one thing I do have a question about though is the aggro detection system. Sometimes it seems to work fine, and other times my rogue just ends up running in circles around the mob trying to get behind it even after he's gotten aggro/hit which looks ridiculous. Any suggestions?

EG

Jerle69 · Post by **Jerle69** » Fri Sep 24, 2004 2:38 pm

escapegoat:

I've never seen the behavior you just described. Are you using MQ2MoveUtils also, or just raw RH? If it's having trouble getting behind the mob and you're not using MQ2MoveUtils, my guess is you're experiencing heavy graphic frame-lag. This is typical client behavior (crazy autofollow, or macro movement) as it's dependent on video speed.

loadingpleasewait · Post by **loadingpleasewait** » Fri Sep 24, 2004 6:08 pm

Jerl69:
I've also experienced this. I use mq2moveutils, sticking behind the mob works fine, its when you accidently get agro and the mob starts wanting to face you and mq2moveutils still has you trying to move behind the mob. So, basically you're spinning around a mob that you have agro of, trying to get behind it, which isnt possible cause you have agro. Comprende?

Jerle69 · Post by **Jerle69** » Sat Sep 25, 2004 9:56 am

Oh yes, I comprende. There's code in there to deal with it too, but you have to unfilter "attacker missing you" and "attacker hitting you" and let it go to some window somewhere. RH can detect either event and uses you being swung at as a means of disabling autosticking altogether. In retrospect, it should probably just drop the sticking *behind* the target instead of sticking completely (that just dawned on me), but RH does deal with it--I'll add smart rear maneuvering for the next release--currently it just stops sticking completely if you're tanking. FYI, if you have the Health of Target's Target group or raid AA, it can alternately use this to determine if you're "tanking." RH uses either this condition or actually being swung at (hit or miss) to determine if you're tanking.

Here again, be sure you toggle your filters off and on (and leave them on) for you getting hit or missed, and you should be good to go. Some user said to me (IRL) that they had activated /serverfilter on about 3 years ago, and it was adversely affecting them while they had aggro. May consider that too.

As I understand it, PuppetMaster doesn't deal with this at all yet. The check for it within RH must be pretty obscure if he hasn't injected it into his code yet, eh?

Hasta,

dariuslloyd · Post by **dariuslloyd** » Mon Sep 27, 2004 5:53 pm

How could I alter this to fire off the bard ability Fading Memories instead of Escape?

I was able to make it so deftdance would fire instead of nimble np, but changing the alt activate number in the macro to 212 (FM) still hasnt worked.

Thanks!

Libra · Post by **Libra** » Mon Sep 27, 2004 6:52 pm

Is there a way to echo settings to a chat channel?
I'm using this to let people remotely control me, and it would be nice if I could make it easier on them by having /rhhelp output into either a chat channel or cross-server tells for each line as well as MQ2 window if someone sends me a tell "soandso tells you, '/rhhelp'" for example.

I'd like to let them see in a chat channel what is happening in my MQ2 window, basically. Chat channel would be ideal for that, could get spammy if xserver tells were used for that since so much scrolls through it -- would work fine for /rhhelp though.

Also, would there be a way to store an array of what to loot instead of just droppable or nodrop? For example -- I'd like to be able to loot every 6th corpse and only diamonds, or other droppable plat items.

Or, be able to use commands to loot certain items. Soandso tells you, '/itemloot "Glyphed Rune Word"' if I were to win, when Soandso tells you, '/random 500' for example. Would have to have a way to identify which corpse has the item as well, I found myself repeatedly looting a body with some nodrop item rotting on it where we were fighting instead of the mob we just killed, because it was closer to me.

Jerle69 · Post by **Jerle69** » Mon Sep 27, 2004 8:11 pm

dariuslloyd:

I'm not really sure. It's possible that fading memories is broken in MQ2? Can you get it to fire using manual /command activation? If you can, you can substitute that for the call to escape.

Libra:

That's all possible--some of it I even like. I'll see if I can redirect output to a variable location, be it a channel, echo, or perhaps even a tell (that I doubt). I'll see if I can make the autoninja smarter. If corpse ID's are somehow related to their respective target ID's, I can certainly do that. Right now, I don't know if that's true. This would take care of accidentally looting nearer "old" corpses when a new one lays on top. I could loot by corpse name, but that wouldn't solve the problem of repeat types of critters stacking up--only a unique ID would. I'll look into it.

Thanks for the suggestions!

Libra · Post by **Libra** » Mon Sep 27, 2004 11:31 pm

I'm glad you like the suggestions, I'll try to keep them coming as I continue using it.

Oskar · Post by **Oskar** » Tue Sep 28, 2004 11:16 am

I've been using this for kiting and I love it. I have a couple suggestions that I have noticed over time.

1) When a /iset buff expires during a fight, after the fight it will start to run back to it's leash point, stop, try to cast the item, get interrupted due to movement, run some more towards the leash, cast, etc. This oocurs until it gets back to the leash and is standing still, then casts.

2) A /assist max range would be nice. If the creature is 300' away and meets the requirements for health% assist, you go runing out to it, hit your max leash range, run back, run out to it. Over and over until it gets in range. I suggest an additional check to mack sure the mob is within XX amount of feet before attacking.

3) The ability to specify a buff that you don't want on you. A prime example would be bard speed. When kiting, it runs so fast that it can shoot you past the mob. I find myself always clicking this buff off when it pulses. A way to automate this would be nice.

4) A % to autoninja. When in groups, I like to get some loot but don't always want to loot every single corpse. I was thinking that you could add a random percentage that is would loot. I added this line into the macro in place of /call NinjaLoot... /if (${Math.Rand[100]}<35) /call NinjaLoot.

These are just suggestions to help make the awesome macro even bettter. :)

loadingpleasewait · Post by **loadingpleasewait** » Tue Sep 28, 2004 2:19 pm

Jerle,
About the detection of agro you mentioned to me a few posts up, you are currently using this:

Code: Select all

#Event GotHit          "#*#hits YOU#*#" 
#Event GotMissed       "#*#hit YOU#*#"

as your event/s, the problem is that the mob may hit/slash/bash/claw/pierce/etc/etc/etc not always hit, and as a matter of fact, they rarely "hit".

The events I'm currently using in arch.mac to detect agro for autojolt are:

Code: Select all

#Event GotMissed             "#*#YOU, but#*#" 
#Event GotHit              "#*#YOU for #*#"

and so far it appears to work perfectly. Maybe you should reconsider the events you're using.

Jerle69 · Post by **Jerle69** » Tue Sep 28, 2004 2:40 pm

True, I noticed this when I was getting clawed the other day. I'll use some other trigger text in the next version (something generic). Just as an FYI, I threw that aggro detector in a while ago when I was pissed off that Target of Target didn't work if you had fewer than four in your group or you didn't have the skill. It was a hack, but it could be a much better hack as you pointed out. I guess I played (and do play) alot in places where getting just "hit" is pretty common.

There's no reason why I shouldn't change the text to your suggestion as it's far more complete and would work in all other situations... Oversight/brainfart on my part. I have had TargetOfTarget since before I even wrote RH, so it was hard for me to actually see this behavior until I solo'ed during the Rogue Epic 1.5/2.0.

Thanks,

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

question

Output

Suggestions

A couple Suggestions...