• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver

Problem - How is /noparse supposed to work.

Gnits

Active member
Joined
Mar 24, 2017
RedCents
674¢
From @Sicprofundus 's hotkeys, the following key does not work for me.

Everyone starts up including my zerker.
Code:
/noparse /squelch /bcg //if (!${Select[${Me.Class.ShortName},BER,ROG]}) /mac kissassist assist ${Group.MainTank} 98
 
No parse means it doesnt have the person issuing the me.class instead the person recieving the msg would.

If my warrior did me.class without no parse it would say warrior, instead of whatever class the command is being sent to.

Another example

If you did /bcaa //bc ${FindItemCount[Widget]} on your shadowknight, all your characters would /bc however many widgets your SK had, and not how many they had... so you need the no parse
 
From @Sicprofundus 's hotkeys, the following key does not work for me.

Everyone starts up including my zerker.
Code:
/noparse /squelch /bcg //if (!${Select[${Me.Class.ShortName},BER,ROG]}) /mac kissassist assist ${Group.MainTank} 98
You can easily test this by doing

/noparse /squelch /bcg //if (!${Select[${Me.Class.ShortName},BER,ROG]}) /bc My name is ${Me.Name} and I am a ${Me.Class}

I just did that in one of my groups and only the cleric, bard, and the pl shaman said anything (cause bcg and not bcga so didn't include the tank - and the other two are zerkers
 
When I do that, everyone else says they are Shadow Knight. Just like the character that issued the command.

EDIT:
Including the zerker.
 
Last edited:
When I do that, everyone else says they are Shadow Knight. Just like the character that issued the command.

EDIT:
Including the zerker.
something is definitely not right then :( I'm not sure what would cause noparse AND !$ stuff to fail on your end

you're not trying to put those on a separate hotkey line are you?
 
You can easily test this by doing

/noparse /squelch /bcg //if (!${Select[${Me.Class.ShortName},BER,ROG]}) /bc My name is ${Me.Name} and I am a ${Me.Class}

I just did that in one of my groups and only the cleric, bard, and the pl shaman said anything (cause bcg and not bcga so didn't include the tank - and the other two are zerkers

So updated to latest build and seems this broke, removing the squelch and you get the expected result, with it you get the toon you did the command on
 
This is indeed an issue in the latest build. It's because the changes I made to /noparse expect you to pass through the parser once after that and this passes through the parser multiple times. I'll fix it, but in the meantime you can do this to work around it:
Code:
/squelch /bcg //if (!${Parse[0,${Select[${Me.Class.ShortName},BER,ROG]}]}) /bc My name is ${Parse[0,${Me.Name}]} and I am a ${Parse[0,${Me.Class}]}
 
Problem - How is /noparse supposed to work.

Users who are viewing this thread

Back
Top
Cart