AFNuke mac (Wiz Bot Mac update: 12-02-04)

Kay7 · Post by **Kay7** » Wed Sep 22, 2004 5:08 pm

AE Snare brainstorm for you Azum. Sorry if it jumps around, but this is how my brain works...

Count the number of resist messages. If there is only one resist message, and you receive a "you resist the..." message, then don't recast. If there's more than one resist message, assume it resisted.

An even better, and possibly cleaner solution, would be to look for the success message (A Hynid is shackled to the ground) instead of the resist message. Of course, this would require the user enabling their own spell messages. It would also help if there are multiple mobs in range of the snare as long as they don't all have the same name.

Perhaps a combination of both? If there is a resist message, look for the target snare succes message?

Azum · Post by **Azum** » Wed Sep 22, 2004 6:36 pm

afnuke.mac (first post - updated 09/22)
afnuke.inc (third post - updated 09/22)
afnuke2.inc (seventh post - updated 09/22)

(09/22) - Mostly this is just the addition of Wrath of Xuzl to the macro. If you have Wrath of Xuzl, it will be used instead of Call of Xuzl. If you don't have Wrath of Xuzl, the macro will continue to use Call of Xuzl. Todo list includes addition of exodus/evac on command, more TL destinations, and possibly a snare overhaul. I'll also be updating the buffslot stuff to 20 and try to add OOW aa's as well.

Azum · Post by **Azum** » Wed Sep 22, 2004 6:38 pm

Kay7 wrote:AE Snare brainstorm for you Azum. Sorry if it jumps around, but this is how my brain works...

Count the number of resist messages. If there is only one resist message, and you receive a "you resist the..." message, then don't recast. If there's more than one resist message, assume it resisted.

An even better, and possibly cleaner solution, would be to look for the success message (A Hynid is shackled to the ground) instead of the resist message. Of course, this would require the user enabling their own spell messages. It would also help if there are multiple mobs in range of the snare as long as they don't all have the same name.

Perhaps a combination of both? If there is a resist message, look for the target snare succes message?

I appreciate the constructive feedback. I don't seem to get much in the way of helpful suggestions (I attribute this to the fact that most wizards are lazy bastards). I think the biggest obstacle for this is the event handling in MQ2. I'm not even sure if it's possible to count the number of resist messages. I like the idea of looking for the success message though. Will see what I can come up with.

eqaussie · Post by **eqaussie** » Wed Sep 22, 2004 11:31 pm

Something really bizarre been going on with this macro and mod rodding.

If my mod rod for instance gets stuck in a bag, it equips to primary, and 'seems' to destroy whatever item i have had there.

My TL Book has been destroyed twice as far as i can tell.

Azum · Post by **Azum** » Thu Sep 23, 2004 5:00 am

I'll see if I can reproduce the error, but I've never had a problem with the mod rodding, and mine is always bagged.

Kay7 · Post by **Kay7** » Thu Sep 23, 2004 3:08 pm

Wizards? Lazy? Not a chance!

Lazy doesn't even begin to describe us!

That's why there's such a huge interest in your jewel of a macro.

I've never had problems with the macro trashing an item to modrod... And it does tend to end up bagged (the spot normally reserved for the rod has been carrying phosphor powder on raids lately...)

Are you sure it trashed it twice? I mean, the TL book isn't exactly easy to come by. I've seen it drop once in quite a few Time clearings... Then again, I've also only seen one silk pant drop in as many clearings... Maybe the rng just hates the wizards in my guild...

Maybe there's just a bug that it wasn't displaying properly... Something to do with the UI.

In any case, it might be a good idea to add a short delay between equipping the rod, clicking it, and restoring the original item, in case there is an issue with lag destroying the wrong item when the rod is finished off. Just a short one, 1/10th of a second should do it.

Rusty~ · Post by **Rusty~** » Thu Sep 23, 2004 4:47 pm

Something really bizarre been going on with this macro and mod rodding.

If my mod rod for instance gets stuck in a bag, it equips to primary, and 'seems' to destroy whatever item i have had there.

My TL Book has been destroyed twice as far as i can tell.

this has been happening to me and someone else that uses one of my macros... it's been happening since OoW went live. for some reason, sometimes, when MQ clicks a rod, either through /cast item, or /itemnotify, the charges on it dont get updated, and when it's been clicked 3 times, it still shows charges even tho it should be gone. and then when it's placed somewhere, it overwrites the item. when you camp and come back the item is back though. it's really annoying

eqaussie · Post by **eqaussie** » Thu Sep 23, 2004 8:14 pm

I'd have to say too, its only been since OoW came out too

The other day, i had 2 rods in my backpack.

Waiting on a petition now to return item.

Going to disable rodding for now i think.

if i comment out the following lines in the main .mac file, is that going to be enough to disable modrodding?

Code: Select all

/if (${modrod}>0) /call ItemFinder "Rod of Mystical Transvergance" 
/if (${modrod}>0 && ${Me.PctMana}<=${rodpercent} && ${hasrod}>0 && !${rodtimer}) /call Modrod 
/if (${modrod}>0 && ${Me.PctMana}<=${rodpercent} && ${hasrod}>0 && !${rodtimer}) /call Modrod

Thanks Azum. This macro is just <3

peach · Post by **peach** » Thu Sep 23, 2004 9:13 pm

why not just do modrod=0 in AFNuke.txt?

eqaussie · Post by **eqaussie** » Thu Sep 23, 2004 9:25 pm

I looked in the macro looking for a toggle and didnt see it.. Forgot all about the ini file... somedays i really out do myself :)

peach · Post by **peach** » Fri Sep 24, 2004 11:43 pm

one problem i've found is that if you get aggro from a mob, it will eat through your rune, and the macro will immediately recast the rune. casting runes generates a lot of aggro, which usually gets the mob right back on ya. maybe have the macro cast concussion (or mind crash if its up, toggleable) if it senses you getting hit by a mob, and only cast rune when no mob is engaged.

Dadelot · Post by **Dadelot** » Sat Sep 25, 2004 8:37 am

Great idea. There could be an event that would make you cast concussion if you are getting hit then re cast rune.

Azum · Post by **Azum** » Sun Sep 26, 2004 2:51 pm

afnuke.mac (first post - updated 09/26)
afnuke.inc (third post - updated 09/26)
afnuke2.inc (seventh post - updated 09/26)
INI documentation (eighth post - updated 09/26)

(09/26) - Added new oow familiars, and support for up to 20 buffs. I know, I'm a slacker.

eqaussie · Post by **eqaussie** » Sun Sep 26, 2004 9:31 pm

Have you added 9th spell gem support out of curiosity?

Azum · Post by **Azum** » Mon Sep 27, 2004 7:51 pm

Grab the spellcast.inc from this thread, updated it so it can use the ninth spell gem now.

Edit: Okay, it will now mem the spell in the 9th gem, but it says "You do not have that spell memorized". Still working on figuring out why that is. ;p

Update: Try this, mem any spell in your 9th gem. Then type /cast "Name of spell", with no macro running. It says 'You do not seem to have that spell memorized'. Leads me to believe it's a problem in MQ2 or such.