Well after 17 years of using MQ2, I finally broke down and jumped into RedGuides. I created my account here in 2005, but I continued to hang out in the MQ2 forums all these years. Anyway, after perusing the RedGuides forms, I found this fantast macro and like how the code was structured. Very nice work GoldenFrog /salute.
To your question Gator, it's pretty easy to adjust this macro to be called by a more "passive" macro like a Buff Bot or a Bazaar macro. You probably don't want to be calling this macro from a more active macro that you may be using to help assist your hunting. Overall, you are on the right track that you need to adjust this macro turning it into an include (.inc), there may be other techniques, but I found this worked for me.
1) Change the macro from Overseer.mac to Overseer.inc
2) Comment out #turbo 50 and #warning at the top of Overseer.inc. I am assuming you may already have this in what will be your calling macro (i.e., the macro that is going to call Overseer).
3) In Overseer.inc, rename Sub Main to Sub Overseer (or some subroutine name you prefer)
4) Comment out the countdownLoop (from the tag :countdownLoop all the way to /goto :countdownLoop). You want this macro (now a subroutine) to release (/return) control back to your calling macro and not sit there looping over and over waiting to run again.
5) Change all occurrences of /endmac and /endmacro to /return. You don't want Overseer to "end" but return control to your calling macro. Personally I don't generally place /endmac commands throughout a macro but instead I create an endmac type subroutine (i.e., an error and/or exit routine). If I want to end the macro or do something else if a significant problem occurs, I /call my exit routine which might address the error or simply /endmac.
6) Create a calling routine in your calling macro's "main loop" (i.e., /call Overseer). Now you can (should) be smart (elegant) about it and include some kind of timer so you don't end up calling Overseer over and over. You want Overseer to run through all its steps then return control back to your calling program. One method is to use a countdown timer to call Overseer every xx minutes. To give you an idea, here is a little snippet assuming a 12 hour (plus 10 minute) countdown (this assumes /declare overseerTimer timer outer 0).
INI:
/if ( !${overseerTimer} ) {
/echo Calling Overseer
/call Overseer
/varset overseerTimer 730m
/echo Returned from Overseer
}
Last edited:
