MacroQuest64

Hey guys,

I'm not sure how it got posted, but you got a copy of 5.0 that had a scoping bug in it (mismatched {}'s that I fixed prior to posting it here in the forums). I'll quickly put up the correct code as 5.1, even though I'm not sure how I got the WRONG 5.0 code posted.

As far as the other suggestions in this thread, I'll see what I can whip up soon. Thanks again for all the compliments :)

Found the problem. WHOOOPS... It was a duplicated error I found earlier... Damn code cut and paste. On the bright side, I found a way to make the weaponswitch stuff into a more generic subroutine which will actually shorten RH for the next release (assuming I don't eat up the saved resources with more code).

5.1 is posted.... It should fix that crash bug. I did NOT test this as I'm using a laptop and I'm not home.

I got a version of 4.7? or 6 whatever the letest one was that has those things in it mostly working if you want to save the typing and want me to paste it up i'd be happy to.

Being a monk i've of course had to bastardize your code to get it to work right for me heh

I've got include files with the monk specific stuff in them that i been working on.

Works pretty well, just add the #includes in the right places.


Could Backstab be made into a variable? Which would allow someone to say replace it once with Flying Kick, or kick or whatever and would allow your macro to be a bit more generic.

I've played with all of the autofight macro's, and so far this is the best that i've played with. Keep up the good work.

o, 2 more things i added tonight(don't think i got the delegate working yet, never saw the msg after i did it to test)

MQ_420:

You can if you like, but if you make this into something more generic or something monk-specific, it may be best to start a new thread for a different macro project. I'd prefer this incarnation of the code to remain rogue-oriented (after all, Genbot is out there), and I think folks would get confused.

Right now all the code that is posted as part of RH I've written personally, and I try to make it as comprehensive as possible both in quality and functionality. Up until 5.0, there never were any major errors and this one was a cut-and-paste issue--real sorry about that too, by the way. Thanks for the input, and I'll look into the Infuration/GoD business. My silly guild is just now to PoTime so we haven't done all the GoD goodness yet.

Love your work,

i've noticed since the latest patch i haven't been able to get the macro to recast my "fallen" clickies, is there something i'm doing wrong?

i can get the items to cast using /iclick, just can't get it to cast them when they're down. I used to be able to just unhide, let the macro reclick the items then let autohs reactivate hide, but its not working for me atm

i've tried both this latest version 5.1 and the original version it worked for me (4.6)

Not sure if this is enough to help you figure out the problem, but i'll keep an eye on this post as i always do.

again, love your work!

Ya, that's why i'm using your code and don't want to branch off of it Jerle. Your code is so well tested and works so well to do what i want i wouldn't want to branch off and not get your new features


Again, great work love the macro.

hmm... do you have to be in the group to use /drag command? I was adding dps outside of a group today and the command didn't seem to work.

OMG!!! nevermind. I win the stupid ass award this morning. I need coffee! (macro wasn't running, duh)

I had a question about dragging bodies:

Does it automatically put you into hide/sneak mode before dragging? I looked at the code, but since i'm pretty new to this, I wasn't sure if it's set to do that.

If not, can you incorporate that into the macro? It would make me feel a lot safer since i have SoS. :)

Have been running 5.1 all day long and its working really really well. Thanks again man you rock.

Dirx

MyS_T_Kal:

Thanks for the kudos! About that fallen clickies business--you're not doing anything wrong, sorta. The fallen clickies code does work (and hasn't changed since it was written); however, there was a small bug in String.Arg[] parsing with non-space delimiters introduced into the 0602 version of MQ2. As such, any macros using INI files (with pipe "|" delimeters) were broken. The String.Arg[] bug was fixed (stealth-fixed) in version 0604 of MQ2. Download the newest version of MQ2, recompile, and the clicky keep-up code will work again.

MQ_420:

Coolness. I'll work on that Infuriate business this week if I'm lucky.

TrippyTom:

Hahaha... Yeah, those alias commands can be misleading if you unload a macro that uses them (and RH uses them heavily). You'll think the macro is busted when the aliases just have no events to hook into :)

Thanks Jerle,

Looking forward to seeing the "Primal" weapon code added :)

Rasthan:

I haven't forgotten about you. I think I have a way of implementing a target-only enrage detection. I was lazy when I wrote that (or rather, a little MQ2 stupid). I know better how to implement target-enrage detection and it will be in the next release. It happened to me too and I lived with it, but now that it bothers someone else, I'll go ahead and make it work better :)

The new "I am being hit" detection code doesn't seem to work. Was grouping with some guildies today and someone rooted a mob and I got some weird questions when I was circling the mob while the tank stood at max range haha.