medding
Posted: Tue Jun 01, 2004 3:27 pm
I am having an issue with medding. I am on a mount, I am lvl 42 when i run out of mana the macro crashes. Have not change the script at all yet still learning. anysuggestions BTW great script.
Need to talk about MacroQuest to other MacroQuest users?
https://mq64.org/phpBB3/
Yeah you're exactly right. The thing is, I did it like that because it also has to support using a time wand or wiz epic to refresh force shield/barrier of force when they get eaten by the manarobe. It's gonna have to stay like this until I find a prettier way of doing it.MagicMan wrote:That is:
It swaps the manarobe into the chest slot.
Puts ele robe in bag.
Clicks the robe.
Swaps the ele robe back into chest slot.
Puts mana robe into bag.
Puts mana robe back into chest slot
Puts ele into bag
clicks the robe
etc...
I had a similar issue with the flux staff if it wasn't in a general inventory slot.
Dangerous if your semi afk cause it screams "LOOK AT ME!! I'M MACRO'D"
Are you using a hack to use mounts without models? That's the only thing I can think of that might possibly make it crash based on what little information you provided.the_horror wrote:I am having an issue with medding. I am on a mount, I am lvl 42 when i run out of mana the macro crashes. Have not change the script at all yet still learning. anysuggestions BTW great script.
Added that and some other stuff..Just_Another wrote:Great Script Azum, I must say it's quite a nice piece of work
but I was wondering if you could add: Phylactery
to the script? and if it would work from inventory too it would rock
Thanks
My pet got tossed when it autocast last night. Either that or I did it without thinking cuz I've done it 4.2 bazillion timesk7 wrote:Also, if it isn't already, when the familiar is checked it should be gotten rid of it the spawn is still there (/pet get lost). A simple /if %M like "*familiar" should do the trick.
The Xuzl code is currently nothing but the AA. The GOD Xuzl AA is passive, so it's activated with this as well. The only thing it's not currently doing is actually casting the Xuzl spell. If you want an option to use a 10 second cast time Xuzl pet I guess I could put it in, seems like a waste of time you coulda been spending doing some real damage though.k7 wrote:I noticed there's an option for the Xuzl sword. Might be an idea to add support for the AA xuzl, as well as the clickie xuzl
http://lucy.allakhazam.com/item.html?id=28977
Also, if it isn't already, when the familiar is checked it should be gotten rid of it the spawn is still there (/pet get lost). A simple /if %M like "*familiar" should do the trick.
Yeah, an exclude list would be good. I just need to figure out how to implement one.k7 wrote:An exclude list would also help a lot. It's annoying having to keep moving back to camp everytime the puller brings a splitter... Plus you really don't want to be nuking certain named mobs on some encounters (like two certain decorins on the RZ script).
Been using the script for a while now, and it works great!
Edit: Is it possible to add a mez check that will interrupt the current spell and redo /assist?
Well, right now there's only variables for up to 3 assists. You can feed them all to the macro when you start it - like /mac afnuke tank1 tank2 tank3 - or /mac afnuke tank1, tank2 - or /mac afnuke tank1, etc. I'll throw in an echo toggle to change them while the macro is running though.sj_digriz wrote:Would it possible to have the 4 Assist names use a Set variable? So that during a raid as the target types change I can change all of the assists. We tend to plow with hybrid tanks, then switch to Warriors for the main named.
Would like to send something like
/afnuke ass1 newMA1name
/afnuke ass2 newMA2name
without having to stop the macro.
I'm a total newb with MQ. Hope this isn't a stupid request.
Ah, I see now...Azum wrote:Well, right now there's only variables for up to 3 assists. You can feed them all to the macro when you start it - like /mac afnuke tank1 tank2 tank3 - or /mac afnuke tank1, tank2 - or /mac afnuke tank1, etc. I'll throw in an echo toggle to change them while the macro is running though.
That's probably my fault, I chopped alot of the 'changelog' and 'instructions' out when the board started eating my post and I hadn't figured out there was a 60k limit in place. I can still see a good use for on the fly assistname switches though, so I'll probably add it in.sj_digriz wrote: Ah, I see now...
1st: Didn't see that you could pass more than the first tank on the command line.
2nd: Figured out that TankName is the same as mainassist1.
Thanks man, I don't really need it to be more complex than that. Unless of course you feel like it![]()
SJ