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

Jerle69 · Post by **Jerle69** » Sun Oct 17, 2004 9:40 am

Ferinus:

I just realized why I didn't add a mount check in the autohs routine originally (I had a horse back when I wrote that part). It's philosophical actually! If you turn on hide and sneak, but then you summon a horse, you're basically saying "Hi, I want to automatically hide and sneak." But then you make a horse, which won't allow you to hide and sneak. The question is this: do you know that horses and hide/sneak don't work together? If so, why didn't you deactivate hide and sneak? If NOT, RH better do something about it (like give you a repeated error about not being able to hide and sneak while on horseback). RH could behave differently, like turning off hide and sneak and telling you about it (if you have a horse). Or it could silently not bother to hide and sneak (even though it's ON, and you turned it on) because your on horseback.

It all boils down to the level of player knowledge. The catch-22 is, if you know that you can't hide and sneak while on horseback, why didn't you type /autohs before you started off on your hose. And if you DID NOT know this, it's best that RH behaves the way it does and spams some godawful stuff when you leave it on and mount a horse.

I guess I could have hide and sneak shut down by event if it gets horse warning text, and then give a similar warning in the MQ2 window. I think doing this passively will get some people dead (as they may assume hide/sneak is still working on horseback).

peaches · Post by **peaches** » Sun Oct 17, 2004 7:33 pm

14 October 2004 by Amadeus
- Removed the BuildData datatype for the moment. The code, as it was originally
conceived, was causing compile problems on Visual Studio 6.0. Moreover, it was
determined that it was not reliable on all partition types. It may be added
again at some point in the future after rigorous testing across different
partition types and both vs 6.0 and vs.net compilers.

Sounds like it could be a while for that change.

BrainDeath · Post by **BrainDeath** » Sun Oct 17, 2004 8:07 pm

tranze204: Highest Backstab? I like to see my backstabs without having to watch the battle spam, so here is some code you could start with:

Code: Select all

#Event BSDamage "You backstab #1# for #2# points of damage."
Sub Event_BSDamage(string Line,string Mob,string Damage)
   /popup Last Backstab: ${Damage}
   /echo Last Backstab: ${Damage}
/return

If you want to track highest backstab for that run of the macro it would be pretty simple to code. If you want it to show the highest backstab EVER, you are going to have to store it to an ini file, read it at the beginning of each run, and update it when a higher BS comes along.

DrmChld wrote: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.

I'll go one further. I've cleaned, and recompiled MQ and MU. If I have the MU plugin loaded, I crash a few seconds after I target a PC regardless of whether or not a macro is running. I haven't had time to take a look at it yet though.

Roodoodog · Post by **Roodoodog** » Sun Oct 17, 2004 8:09 pm

Wondering if anyone else is having a similar problem.

RH works as its meant too, to a certain point. The problem i'm having is it seems mq2 isnt reading something somewhere. If i try to type in a rh command I get the, is not a valid command, text. I.E /rhhelp, /autoassist etc etc. Until I get my new VS disc's I wont be able to tell for sure if my VS/puter is over it or something else. If anyone is having a similar prob, any help would be greatly appreciated.

Cheers

Roo

Jerle69 · Post by **Jerle69** » Sun Oct 17, 2004 8:36 pm

Come on people, read the last few pages of the thread... it's all in here.

Peaches:

Amadeus and some VC6++ folks already got the code working... now it's just a matter of when he'll put out another zip file.

GD · Post by GD » Mon Oct 18, 2004 2:26 am

* EDIT * Fixed a small bug, thanks to BrainDeath for showing me it.

Before you had to add the code to the RH.mac file, now it's just an include.

Notifiers can be used alone or together, such as echo+popup+speak to get all 3 alerts, or just speak to only have it spoken.

To use spoken notifiers, you must have the speech plugin compiled and loaded.

It also no longer allows FB/Assassination as max backstab, as they don't really count as a regular backstab.

RHBackStab.inc

Code: Select all

#Event TogBSAnnounce   "[MQ2] BSAnnounce#*#"
#Event SetBSNotifier   "[MQ2] BSNotifier#*#"
#Event TogBSTrack      "[MQ2] BSTrack#*#"
#Event BackStab        "You backstab #1# for #2# points of damage."

Sub InitRHBackStab
  /declare BSAnnounce bool outer TRUE
  /declare BSNotifier string outer echo
  /declare BSTrack bool outer TRUE
  /declare MaxBS int outer 0

  /if (${Ini[RHSettings.ini,General,BSAnnounce].NotEqual[NULL]}) /goto :Ini
  /squelch /alias /bstrack /echo BSTrack
  /squelch /alias /bsannounce /echo BSAnnounce
  /squelch /alias /bsnotifier /echo BSNotifier

  :Ini
  /if (${Ini[RHSettings.ini,General,BSAnnounce].NotEqual[NULL]}) /varset BSAnnounce ${Ini[RHSettings.ini,General,BSAnnounce]}
  /if (${Ini[RHSettings.ini,General,BSNotifier].NotEqual[NULL]}) /varset BSNotifier ${Ini[RHSettings.ini,General,BSNotifier]}
  /if (${Ini[RHSettings.ini,General,BSTrack].NotEqual[NULL]}) /varset BSTrack ${Ini[RHSettings.ini,General,BSTrack]}
  /if (${Ini[RHSettings.ini,General,MaxBS].NotEqual[NULL]}) /varset MaxBS ${Ini[RHSettings.ini,General,MaxBS]}

  /echo ** Announce Backstabs: ${BSAnnounce}, Notifier: ${BSNotifier}
  /echo ** Track Max Backstabs: ${BSTrack}, Current Max: ${MaxBS}
/return

Sub Event_Backstab
  /if (${BSAnnounce}) {
    /if (${BSNotifier.Find[echo]}) /echo ${Param0}
    /if (${BSNotifier.Find[popup]}) /popup ${Param0}
    /if (${BSNotifier.Find[speak]}) /speak ${Param0}
    /if (${Param2}>${MaxBS} && ${Param2}<32000 && ${BSTrack}) {
       /if (${BSNotifier.Find[echo]}) /echo New max Backstab of ${Param2}
       /if (${BSNotifier.Find[popup]}) /popup New max Backstab of ${Param2}
       /if (${BSNotifier.Find[speak]}) /speak New max Backstab of ${Param2}
       /ini "RHSettings.ini" "General" "MaxBS" "${Param2}"
       /varset MaxBS ${Param2}
    }
  }
/return

Sub Event_TogBSAnnounce
  /if (${BSAnnounce}) {
    /varset BSAnnounce FALSE
    /echo ** Backstab Announcing is now OFF!
  } else {
    /varset BSAnnounce TRUE
    /echo ** Backstab Announcing  is now ON!
  }
  /ini "RHSettings.ini" "General" "BSAnnounce" "${BSAnnounce}"
/return

Sub Event_TogBSTrack
  /if (${BSTrack}) {
    /varset BSTrack FALSE
    /echo ** Backstab Tracking is now OFF!
  } else {
    /varset BSTrack TRUE
    /echo ** Backstab Tracking  is now ON!
  }
  /ini "RHSettings.ini" "General" "BSTrack" "${BSTrack}"
/return

Sub Event_SetBSNotifier(string Line)
  /if (${Line.Arg[3].Length}) /varset BSNotifier ${Line.Arg[3]}
  /echo ** Backstab Notifier set to: "${BSNotifier}"
  /ini "RHSettings.ini" "General" "BSNotifier" "${BSNotifier}"
/return

Then, in RH.mac, add the following lines in red:

#Event StatInfo "[MQ2] -------=======(Current Status)=======--------"

#include RHBackstab.inc

Sub Main

/echo -------=======(Current Status)=======--------

/call InitRHBackStab

:ForeverLoop

Oskar · Post by **Oskar** » Mon Oct 18, 2004 1:27 pm

Another suggestion:

If you end up Facestabbing, have it continue to face the mob and check for distance. I was in a group where I was tanking for a bit and the mob kept getting pushed out of range and moving around.

BrainDeath · Post by **BrainDeath** » Mon Oct 18, 2004 2:08 pm

Thanks GD, I'm going to try it out :)

Cr4zyb4rd · Post by **Cr4zyb4rd** » Mon Oct 18, 2004 3:11 pm

If you end up Facestabbing, have it continue to face the mob and check for distance. I was in a group where I was tanking for a bit and the mob kept getting pushed out of range and moving around.

Under those conditions I'd probably just switch from "/stick behind" to "/stick", although I haven't really looked at the movement parts of RH enough to know if that's viable.

Jerle69 · Post by **Jerle69** » Tue Oct 19, 2004 1:26 am

Oskar:

That's in 6.0 (which you don't have yet). Thought I mentioned that? I guess it's already on the previous page on "things I'm sticking in there for the next version."

GD:

Hey that's a nice include :) Hrmm... should I just stick it in there I wonder.

Cr4zyb4rd:

Not viable. RH controls the actual invocation of /stick commands and does conditional things with MQ2MoveUtils based on if you're in water, have aggro, etc.

DrmChld · Post by **DrmChld** » Tue Oct 19, 2004 11:54 am

Release 6.0beta already :)

fearless · Post by **fearless** » Tue Oct 19, 2004 12:14 pm

I'm thinking he will release it when he's good and ready. Whining / bitching, even with the best possible intentions, is not the way to get it done earlier.

Jerle69 · Post by **Jerle69** » Tue Oct 19, 2004 1:06 pm

Hey all,

I'll find out from Amadeus when the BuildDate subobject will be released. If it's a week or two, I'll go ahead and push out 6.0 w/o the MQ2 version check. I guess I'll just toss out 6.1 later when the code makes...

6.0 testing is done.... no bugs.

blueninja · Post by **blueninja** » Tue Oct 19, 2004 2:43 pm

Jerle69 wrote:6.0 testing is done.... no bugs.

Famous last words lol ..

DrmChld · Post by **DrmChld** » Tue Oct 19, 2004 6:01 pm

How about a auto-disarm when fighting option?

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

Revised Backstab Tracking