Problem - /noparse not working the same as pre-patch

[vsab]

Before the last patch the following hotbutton line worked. It would run KA on all but beserkers, rogues or beastlords in group. I issue the command from my SK:-

/noparse /squelch /dgge /if (!${Select[${Me.Class.ShortName},BER,ROG,BST]}) /mac kissassist assist ${Group.MainTank} 98

After the patch, it seems like the /if statement evaluates as true (e.g. ignores /noparse), as it runs KA on all toons, regardless of class.

Any ideas?

 

[jande]

Remove /squelch that was the previous culprit.

 

[Knightly]

This is a bug in the parser version 2 that I haven't had time to go back and fix yet. As jande said, you can remove /squelch or the other option is to use the version 1 parser. Lastly, you can change the hotkey to:

/squelch /dgge /if (!${Parse[0,${Select[${Me.Class.ShortName},BER,ROG,BST]})]} /mac kissassist assist ${Parse,0[${Group.MainTank}]} 98

 

[ctaylor22]

Kissassist 11.005 turns on version 2 of the parser because it is needed for what we are doing with DanNet.

 

[vsab]

Is there a TLO to check which parse you're using? This may well get very confusing! I know on one setup I run KA manual *then* issue that hotbutton from that character. But I'm pretty sure on the other set up I run KA on the driving toon *after* that line.

 

[Knightly]

Is there a TLO to check which parse you're using? This may well get very confusing! I know on one setup I run KA manual *then* issue that hotbutton from that character. But I'm pretty sure on the other set up I run KA on the driving toon *after* that line.

${MacroQuest.Parser}

 

[Dozecar]

How do we unload the parser 2? I see it being loaded by KA. And how do we load 1 back? Lots of misc errors since last patch, perhaps related.

 

[Knightly]

Assuming kiss is setting the parser to 2 using the #engine command it will automatically get set back to whatever you had it set to when the macro ends.

You can check the TLO above to know for sure which parser you're using at any given time. Alternatively, your default parser is stored in your macroquest.ini file under ParserEngine=.

Finally, you can change the parser default with /engine parser 1 (or 2) and if you just want to change it to test something but not change your ini you can use /engine parser 2 noauto.

What is the context on those screenshots? Is it during a macro?

 

[ctaylor22]

@Dozecar, If you really think the Parser is the issue, then go into the Macro and rem out the #engine parser 2 line at the top of the macro and TURN OFF CURES OR THE MACRO WILL BLOW UP. The only place that uses the Parse[] command is in cures. If you continue to get the NULL errors than it isn't the Parser engine change.

 

[Dozecar]

I was just asking. I have no clue what is causing all these issues. I know that prior to the last EQ patch, MQ worked. Since that patch, there are all sorts of issues. It may be that I'm just noticing them more since I am also having issues, but I see a lot of posts with problems. So I'm assuming there are lots of issues.

KA had a bunch of changes made to it. Parser 2 began being used. I'm just throwing ideas out there. When something works, then stops working after a change, I assume the change cause it to break. However in this case there appear to have been multiple changes made, so I'm just throwing ideas out there because I'd like to help get it working again. I have almost zero interest in playing eq without MQ. Even when I am just soloing an epic or tradeskilling, or whatnot, I rely on mq for easy movement, etc. EQ without it sucks balls.

The thing that sucks most, is the issues are not full time. So I can't just grab you a debug log.

When you lose your keys, they are always the last place you look. I'm just suggesting or trying to look in different places. Once, I found mine in the refrigerator. I must have dropped them in there when I put the milk away. I had given up looking for them at that point and grabbed my spares because who looks in the fridge for their keys?

 

[ctaylor22]

@Dozecar, I don't want you to get the wrong idea, I am very appreciative of your help. I am thankful for you posting the issues you are having. You are doing what I would expect from a user wanting to resolve these issues.

I have taken into consideration everything you have mentioned above and even more. What frustrates me the most, is when I try to replicate the issue and I can't. That doesn't mean I think there is something wrong with the way others are doing things, it just means I will have a harder time figuring out what could be the issue and fix it.

So trust me when I say Thank You. I truly mean it.

 

[jande]

This resonates with me strongly. If I cannot get it replicated I do get frustrated not with the user but with my own inability to grasp what is going wrong. At time is may come across as being unfriendly/mean/not wanting to help. Everyone please believe any dev wants to get the problems solved.

My standard responses on a problem that I can replicate is it will be solved, if I cannot replicate then this is going to take time.

 

[Dozecar]

@Dozecar, I don't want you to get the wrong idea, I am very appreciative of your help. I am thankful for you posting the issues you are having. You are doing what I would expect from a user wanting to resolve these issues.

I have taken into consideration everything you have mentioned above and even more. What frustrates me the most, is when I try to replicate the issue and I can't. That doesn't mean I think there is something wrong with the way others are doing things, it just means I will have a harder time figuring out what could be the issue and fix it.

So trust me when I say Thank You. I truly mean it.

I didn't take it that way. And I'm glad you didn't take my posts as non stop complaining. I was just super frustrated.

You're welcome. And Thank You for the time and effort you spend on making this work.