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

TrippyTom · Post by **TrippyTom** » Fri Oct 15, 2004 4:30 am

Jerle, I thought you were releasing an updated version of this when the new MQ was released....

/taps foot.

Bonehead · Post by **Bonehead** » Fri Oct 15, 2004 4:42 am

Anybody having problems with this after todays release?

Cr4zyb4rd · Post by **Cr4zyb4rd** » Fri Oct 15, 2004 4:51 am

I just used it for a few hours for out-of-group DPS with no problems...then again my MQ isn't exactly stock, so I guess there could be a change that didn't affect me.

Bonehead · Post by **Bonehead** » Fri Oct 15, 2004 5:31 am

Mines fairly stock with a few plugins, just learning to compile and get stuff going. It setup and ran fine but couldnt change mainassist or turn leashing/autoassist on. I will try a few things later.

Azum · Post by **Azum** » Fri Oct 15, 2004 5:41 am

sounds like you didn't save your macroquest.ini so the aliases arent there anymore.

Jerle69 · Post by **Jerle69** » Fri Oct 15, 2004 10:22 am

Beware your MacroQuest.ini being overwritten people. If you have issues since the new patch, edit your RHSettings.INI file and delete the "Version=XX" entry and reload the macro and it'll patch/fix your MacroQuest.ini.

Oh, and yes, I did promise a new release with the new release of MQ2; however, you'll notice in the code patch that the devs included a new TLO I requested (MacroQuest.BuildDate) but since the object was having compile issues on the old VB6 platforms, they had to yank that new code--THAT code was specifically what I needed to use to make RH not screw up when new patches were out (hence the first paragraph if this post). So I'm still going to wait until the BuildDate member is patched in and working before I cut loose another RH. Sorry!

Take care,

TrippyTom · Post by **TrippyTom** » Fri Oct 15, 2004 10:24 am

In RHSettings.ini, delete the line that says "Version .... "
Sometimes it forgets what version you're on and loses the pointers to the commands. I had to do this again last night (after installing the new patch) to get it to work.

:edit: .. er yeah, what he said

dman · Post by **dman** » Fri Oct 15, 2004 11:19 am

Have you considered using http://macroquest2.com/phpBB2/viewtopic.php?t=9603 for the aliases? While it would add another plugin that would be required, it seems to be a great concept.

Cr4zyb4rd · Post by **Cr4zyb4rd** » Fri Oct 15, 2004 1:23 pm

Why not just do something like

Code: Select all

/alias /rh /macro RogueHelper.mac v1.3

when you set up the aliases? Then if no param0, you could have the macro spew something like "please use '/rh' to start Rogue Helper, or '/macro RogueHelper.mac set' if running for the first time"

DrmChld · Post by **DrmChld** » Fri Oct 15, 2004 1:35 pm

I'm having problems crashing when using Moveutils on the new release.. Works fine with the MU plugin disabled.

MU has been rebuilt. Seems to always crash when it looks for the target

Jerle69 · Post by **Jerle69** » Fri Oct 15, 2004 2:38 pm

DrmChld:

I'll give it all a whirl when I get home tonight; I haven't had a chance to use the new MQ2+MU yet w/RH59.

Cr4zyb4rd + dman:

Amadeus wrote a new TLO for MQ2 called "BuildDate" as a sub object to MacroQuest. All of these suggestions are well and good, but when that TLO goes into the MQ2 baseline, I can fix all the alias business once and for all. Your workaround is just that, and it's a clever way of binding the Macroquest.INI to RH, but it's also not the most elegant solution. The real way of fixing the problem is interrogating MQ2 to see if it's a new release--when the MacroQuest.BuildDate object is in place, I can code this the right way (which'll be a day or so, I expect). Also, dman, with this TLO I won't need any alias plugin controls. I try to avoid leaning on plugins because I can't expect everyone to use all plugins (even MoveUtils is optional).

dman · Post by **dman** » Fri Oct 15, 2004 3:12 pm

editted for ramblings so no actual content

Cr4zyb4rd · Post by **Cr4zyb4rd** » Fri Oct 15, 2004 3:33 pm

*sigh*

Jerle69 · Post by **Jerle69** » Fri Oct 15, 2004 4:14 pm

All:

Well, I'm already ramping up 6.0. It's not going to be a major release, but will have a few of the suggestions discussed within the last 4 pages of the RH thread here.

Here's the running list of what's going in so far (and I'll edit this post as I keep changing/adding until I post 6.0)

Flebbit's code changes, including checking range between mainassist and target before engaging (you won't autoassist any more unless this distance is less than the target's MaxRangeTo value; Flebbit hard coded 35, but I check for the mobs ToHit radius instead (more flexible parameterized). Also added his changes for checking if a target is mezzed before attacking also. Further, I also integrated his check of sneak before hide so RH won't ever "double-hide" again after a fail).

Changed code to detect aggro when Target of Target is unavailable, which should work in all instances now, not just when the mob does "hit" damage (ie. claw, bite, whatever). The should end the "circle dance" around anything that's beating your ass.

Changed sticking code to continue to stick to a target that you have aggro from, but not to stay behind. In otherwords, you'll always stick, but you won't always seek the rear if you have aggro. You used to simply stop sticking while you were tanking--this is no longer the case!

Adding /output <channel> command, and you can set the channel to either echo (which is the deault or MQ2 window), or 1,2,3, etc. If you set it to one of those channels, all of MQ2's output will go there instead of the MQ2 window. Note, you should NOT set it to tells or guild or anything totally stupid for two reasons: one, you'd be obvious to MANY people that you're using a macro, and secondly, those channels have spam inhibitors that'd truncate most of the output info anyway).

Adding /verbosity 0|1|2 command. This will allow you to set the verbosity level of RH--0 will have VERY few outputs, 1 will have just the essentials, and 2 will be as it is now (the default).

**Will add MQ2 version checking prior to redefining aliases. I can't add this yet because it's not in the MQ2 baseline. When it is, I will, and I'll give you all this other stuff too.

Anyway, that's what's in the works. I'll have it out to you guys when it's tested and MQ2's BuildDate subobject is in the MQ2 baseline.

Jerle69 · Post by **Jerle69** » Fri Oct 15, 2004 7:43 pm

Coded everything above in 1 hour... Just waiting on the MQ2 TLO change for BuildDate in order to do the last one. Also, I'll take a look at the "horseback" situation too.