Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋
This is a great thing to check... particularly since I use the /mqpause on and /mqpause off commands to move and reset camps. It would keep something from firing when the toons are moving (although, honestly, I don't know if I ever ran into that issue before)
have a MQ2HUD line to show the name of the currently running macro. And if it is my usual macro, have another line to tell if it's pause function is engaged.
have a MQ2HUD line to show the name of the currently running macro. And if it is my usual macro, have another line to tell if it's pause function is engaged.
While I have this thread, how would I setup an if statement with ${Time}? to say /if ${Time} > 220000 || ${Time} < 100000 I want to set a condition that would work between 10 am and 10 pm, is that possible? I noticed ${Time} reports like 22:00:00 or 10:00:00
I believe I had tried to nest IF statements inside an IF statement (in an outer IF) in the true or false section before, and I think I had failed (can't remember entirely). However this thread made me want to try again. I had currently running mac already in my HUD, and I could have used a second line that took the same display space (as is customary) for PAUSED. But I hate incurring unnecessary tests, since I am already in a true/false defined decision branch. It just goes against efficient execution design.
This time around (again, fuzzy on the past details), this works:
This saves a decision path since the embedded IF only fires in the FALSE side of the outer IF. Now I have not only the mac running name, but whether it is paused (while still maintaining the mac name). This keeps me from having multiple HUD lines going to the same place and wasting execution overhead.
Thx for this thread, and making me revisit something I had previously succumbed to inefficiency before...
- - - Updated - - -
NOTE: I use a special HUD settings that not only allows me to have an extra position element, but also absolutely requires it. If your HUD is NOT setup this way, and you know who you are, then modify the positional/size/color etc portion to match your more normal HUD requirements. AGAIN, I have an extra positional element, count the commas in the beginning of the line. Mine will not work for you if you are not set up this way, so you must remove the extra element (easiest way is to copy in one of your line definitions over mine). The decision part will still work.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.