MacroQuest64

Posted: **Wed Nov 24, 2004 7:27 pm**

seem to be a little screwy now with the newest zip. None of my events that I pass variables to work right anymore. I verified the events are triggering, but in an event such as this:

Code: Select all

#event togglema          "[MQ2] ma #1#"

sub event_togglema(Line, Command) 
/e HI THERE - ${Command}
/if (!${Command.Length}) /return 
/ini "${IniFile}" Settings tankname ${Command} 
/ini "${IniFile}" Settings mainassist1 ${Command} 
/varset mainassist1 ${Command} 
/varset tankname ${Command} 
/echo Your Main Assist is ${tankname}

The echo displays 'HI THERE -'

Posted: **Thu Nov 25, 2004 4:01 am**

Command might be a reserved word, not sure. Try testing it with a different parameter name.

Posted: **Thu Nov 25, 2004 10:11 am**

Reverting back to the previous zip fixed all my problems. I don't think it matters what you name the parameter, its just not working properly with the latest zip.

Posted: **Thu Nov 25, 2004 12:39 pm**

You sure you did a FULL clean recompile? I haven't gotten to test this yet, but I can't imagine that Lax would release a blech change without testing it. (Well, ok, I can imagine it...) :)

Posted: **Thu Nov 25, 2004 1:28 pm**

overwrote everything except the .sln file and did a clean compile.

Posted: **Thu Nov 25, 2004 10:33 pm**

Definitely something fishy here. I'm whining at Lax about this on irc right this minute.

Posted: **Thu Nov 25, 2004 10:40 pm**

Fixed in MQ2-20041125.zip, enjoy

Posted: **Fri Nov 26, 2004 12:00 am**

Tested, and works well for the above case. I'm having some problems with macros that do #*# type events and handle their own argument parsing though...they either don't fire at all or fire multiple times.

I suspect some of this might be work-around from the bug that blech 1.6 fixes, but tonight's the first time I've ever fiddled with all but the most simple events, and the only ones giving me problems are huge ones like afknuke and roguehelper...probably best to give the latest zip a few days to percolate, and let the macro developers themselves pinpoint the issue.

I'll be watching this closely and keeping in touch with Lax (who doesn't read these boards much, these days) as we sort things out.

Posted: **Sat Nov 27, 2004 2:22 pm**

still bugged...

when using #include (e.g. spellcast.inc) in a macro, many events are missed... like fizzle, OoR, resist... etc.

Posted: **Sat Nov 27, 2004 10:42 pm**

My post mentioned that events are being skipped. Do you have anything more specific than "still bugged" to add?

Posted: **Sat Nov 27, 2004 11:39 pm**

Hm... alright. My current setup is like this:

myshm.mac <--- my shaman macro

In it I use spellcast.inc to handle spell casting stuff.

While the events in myshm.mac are doing fine, like chat, tell, group, etc., some events in spellcast.inc failed to trigger. (yes, SOME, not all. and I don't have time to test each of them however) Those I remembered are fizzle, resisted, and out of range.

The spellcast.inc is exactly the one from this forum.

Posted: **Sun Nov 28, 2004 9:56 pm**

After driving myself nuts for a while (could only get it to happen in huge macros with 50 events) I've managed to isolate 2 (probably related) problems, and Lax is looking into it.

Posted: **Sun Nov 28, 2004 11:20 pm**

Here's an example of a problem (not sure if it's the same one):

Code: Select all

#event Exp "You gain#*#"

matches: You can use the ability Fellstrike Discipline again in 20 minute(s) 19 seconds.

Changing the event to:

Code: Select all

#event Exp "You gain experience!!"

or

Code: Select all

#event Exp "You gain experience!!#*#"

seem to be a workaround (in the process of exhaustive testing).

Posted: **Mon Nov 29, 2004 12:14 am**

To test can we take the blech.h from the previous zip and compile it into the 1125 zip? I don't want to screw around and have it cause other issues that might side track my troubleshooting so I thought I'd ask before I step into that approach.

My experience so far is the same others... some events don't fire (even the most simplest of events with no parameters, etc) and some events fire double.

Posted: **Mon Nov 29, 2004 12:55 am**

Using and older blech.h shouldn't cause any other problems, as far as I can see. All it does is define a class that's then used by event handling.

As devNull indicated, doing a #*# match seems to make matching in general a little bit nutty. As for events not firing, I fiddled with an old rogue-helper enough to discover that

Code: Select all

#Event TogAuto "[MQ2] Autoassist#*#"
#Event TogTSwitch "[MQ2] AutoTargetSwitch#*#"
#Event TogTraps "[MQ2] AutoTraps#*#"

will cause the first event to not fire unless one of the other two are commented out. I'm almost sure that the problems are related, and it's probably a simple fix...I just hate to spend my time debugging it when I've put so many other MQ-related projects on the back-burner already. :/

MacroQuest64

Events

Events