Yea, i've been trying to figure out wtf is happening...but can't put my finger on it. It's causing all sorts of crashes in various places.. It looks like the stack is not getting set back correctly almost, becuase variables inside a proc, that it's been using, it all the sudden will start complainin...

grrr

as of today's patch... I"m getting some really odd behavior. my macro for getting behind a mob for instance will make me run the opposite direction, and i'm crashing so much i've turned it off at this point. Is this something anyone else is experiencing? I'm positive it's in my movement section...

Ok, got it now :) Basicly this is what's happening.... The MQ2HUD.DLL is not clearing the elemtent list. What i did to get around this is... Use Element2 ( or what ever ) as the section name in the .INI ( do not use elment, it's the default acording to the .cpp file ) So what you have now, is a blan...

Skip that... It started flaking out on me now using just the spaces also, so that's not a fix as it first appearted to be.

There is..change this line /ini "../MQ2HUD.INI" "Elements" "RADARTarget${nCount}" "" to this /ini "../MQ2HUD.INI" "Elements" "RADARTarget${nCount}" " " The only diffrence is between the LAST set of quotes, i added a spac...

Wow... as simple as pressing F11.... I havn't looked at that in so long iI forget the key existed

Thanks.. It was all about the f11

I have tried to modify the mq2hud.ini file, inserted elements, etc... and I can't get anything to show up on the screen.. When I do a /plugin list, it's loaded. Is there some secret trick to getting this stuff to show on screen? Basicly, my mq2hud.ini looks like this... [Elements] Blah=3,512,384,255...

It changed..

You need to include more then the word "sorry" now in the event.

Something LIKE

#Event BlaBlah "Sorry, you dont have enough of this item in your #*#"

The #*# is just a wildcard saying.. anything here ( basicly ).

It does however report a line number error during executing. That's what i was trying no get rid of, not the ""xxxxxxx : (0-100) any" message.

I just re-tested and no.. it's not doing a fatal. My mistake there. Was another line actually that i had typed in while the macro was running in order to see what was causing it


/squelch. though.. perfect. Thanks.

I have noticed, that when you /face nolook..... and you do not have a target. it Just says the little msg , " There were no matches for: (0-100) any" fine. So now I have a macro running .. and I typ in /face fast nolook with NO targett. And an error is reported in my script at what ever li...

I use this from an alias...... they both work.. the first is for draggin a single corpse, the second is for dragin any you target.. then target yourself, and it will begin. Target yourself again and it will end. I have drug up to 12 corpses at 1x, at a full run, and never droped 1. I added this to m...

YOU FUCKING IDIOT!!!



There.. I've been verbally abused for that...... damn

When was this changed? I don't see anything in changes.txt. I have a script I've been working on for a while now, and as of today, events require EXACTLY the text.. ie Including the [MQ2] part in the front.. My events that were firing off yesterday , are no longer working with the 2nd build from 5/1...