MacroQuest64

I developed a Necro helper macro that includes a DoT spell set of timers and experience tracking. It was previously VIP-only (pending feedback and bug reports), but is now available to all. It is available in the Wiki - go to http://www.macroquest2.com/wiki/index.p ... st2:Macros and click the Necro Helper link.

[[Necro Helper]]
You can use wiki links from the forum as if they were in the wiki instead of linking the url

thanks! i usually start a stopwatch and watch it to see how long i have until cascading darkness wears out, this will help alot! thank you sir!
ill test it and hopefully love it immediatly.

True ... but my cunning plan was to encourage others to add their macros to that nice place-holder page you had created I'm loath to post other macros there that I happen to use as I didn't write them. Yafm and Kaladim fungi harvester for example.

The macro works good, but I'm unable to get the Hud to display... except in the case after you kill the mob, it displays the amount of xp you just received. I do have MQ2HUD plugin loaded, and I've created and inserted the text for the MQ2HUD.ini file. Anyone else have this happen? Seems to me I'm just doing some boneheaded thing here, probably a typo, I'll continue to look into it.

Thanks

Casper

Okay figured it out... I forgot to Turn on the Network Meter [F11]. DOH!

An updated version is in the WIKI: http://www.macroquest2.com/wiki/index.php/Necro_Helper

- Added some more spells
- Added an extra timer slot
- Added option to do a /gsay to tell your group what you're up to

Ok, wiki updated again as I had a couple of "features"

- gsay reporting was too fast, so I put a delay in so its not quite so obviously macroed. Could probably improve this to be a randomized delay, or omit on occasion.

- if battle spam was on, it would report other group member's casting hits ! Really obviously a macro I have added a check on the gsay reporting for each cast hit to make sure it relates to the spell you last cast.

- cleaned up the code indentation a bit too

where does this get it's value?

I am getting the wrong time for bond of death and only bond of death, so I can only guess that it's using the wrong value to calculate the time. I'm going to go mess with it a bit more in game. It shows me 18 seconds as the duration, and the value from echoing ^^ that up there is 3 (should be 9).

I'm pretty sure I spelled it correctly

guy wrote:where does this get it's value?

Code: Select all

${Spell[${DebuffSpell}].Duration}

I am getting the wrong time for bond of death and only bond of death, so I can only guess that it's using the wrong value to calculate the time. I'm going to go mess with it a bit more in game. It gives me 24 seconds as the duration.

I'm pretty sure I spelled it correctly

Code: Select all

/varset DebuffSpell Bond of Death

If you mis-spell the spell's name, you don't get any timer information - so you got it right in the macro.

There are a number of spells where the "Duration" property comes out at the wrong value, Saryrn's Kiss is another. I *think* its because the timer calculation is unknown in some cases, so the MQ2 code can't fill in the right value for it. These 2 particular spells don't really worry me as you can always see the recourse buff flashing when its about to expire. The timers are correct for the critical spells (snare !).

I would have reported it as a bug a while ago, but a bug report without specifying what the fix should be is pretty useless. IRL I'm a software developer, a bug report that says "Its broken, fix it" without saying what the expected result should be, ends up at the bottom of my todo list. As the MQ2 devs are not being paid to deal with crap, I didn't throw any their way.

I used to do a lot of C++ (switched to java about 8 years ago - lots more money !), perhaps its time to dust off that knowledge and go look at the MQ2 code and submit a patch.

thanks for the quick reply.
I know a little c++ so I'm trying to look through the source code now.

Wiki has been updated with the latest version of this. I fixed the bugs that showed up as a result of the change in MQ2 to stop abuse of the String TLO.

Thanks are due to "loadingpleasewait" in VIP for helping me understand string comparison syntax.

First off, I love this macro. It makes things so much easier in my playing. I have encountered a problem while using it in group mode, If the mob dies before the announcement in /gsay it will say "NULL" which is a dead giveaway that I'm using a macro(fortunetly only happend while grouped with close friends). So I would like to share my fix, not sure its the most elegant way of correcting issue, but if it is a kludge at least its a kludge that works.

Original Sub: My Fix: This has fixed the problem for me, if there is a better way by all means tell me, I'm very new to scripting MQ2 macros.

Thanx and happy hunting.

Hadn't seen that behaviour before, but your fix looks good to me. I usually save my mana and let those lazy tanks finish the mobs off

I've updated the Wiki version with it - and also with a small fix in SetupTimer that stops timers being kicked off for other people's casts.

Glad to know its not just me using it.