Zugg Software :: View topic

Newbie Joined: 11 Oct 2016 Posts: 6

Hi guys I am new to zmud, so consider me clueless.

I am trying to set up an alias (getgroup) that will make a trigger to fill a variable (groupmember) with all members of my group, fire the group command in game and then delete the trigger.
The following text is what shows when using the group command in game and the variable will need to store at least 5 names.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

First let's make sure. You are using zMud and not CMud. There are many differences and given all the years I am not sure I remember them all.

In general for both you want to use an #ONINPUT trigger instead of an alias to start your group capture. This is because the trigger only needs to clear some variables and can let the command pass unchanged. By creating a sub state for that trigger it will automatically become active allowing the capture to proceed. I tend to use a LoopLines sub state and parse all the information with script for each line. %begins, %ends. %match, and %regex are your friends here. From what you said I would likely use %ends and the ">" to detect when to stop capture and parse all the lines with %subregex, because there is a solid speed gain. However, %subregex was originally buggy and I don't remember when it got rewritten to be stable.

As for sending the rescue command you want your trigger to check #IF %ismember on a variable for a groupmeber and #ADDITEM when it sends the command. Add a second trigger for doing the rescue to #DELITEM.

Newbie Joined: 11 Oct 2016 Posts: 6

Hi Vijilante, thanks for your response. I am using zmud.

You have pointed me in the right direction, but total beginner here with zmud.

Should I be inputting this from the command line? Or should I go into the trigger menu?

Could you give me an example of what it should look like?

All help appreciated, thanks again

SubAdmin Joined: 18 Nov 2001 Posts: 5182

In general you will want to build settings using the editor, but most things passed around on the forum are design to be placed directly in the command line.

Let's start with capturing the group member names.

Newbie Joined: 11 Oct 2016 Posts: 6

Thanks for your help Vijilante. I inputed the groupcapture code directly into the command line but it is not working. When I input group it doesn't fill the variable. Do I need to add something to the code?

^s+(TH|BA|CL|PA|WA|SC|WH|BL|RE|DA|SH|DR)s+(%1)

Or something like that for it to capture the name accurately?

Newbie Joined: 11 Oct 2016 Posts: 6

ok I got the errors sorted and it all fires correctly but it captures the wrong string. fills the variable with members. Could you explain what the first #cond does? Going to adjust the second #cond to a regex I think...

SubAdmin Joined: 18 Nov 2001 Posts: 5182

The first state(0) is the input trigger which catches that you typed group. It just clears the variable and sets the stage.
The next state (1) is simply meant to match the line "------------------------------------------------------------------------------------" so that we know the next line will start having group members. Perhaps a better pattern would be ^-+$ or maybe ^-{20,}$
The third state (2) uses a fixed width match to capture a portion like this

Newbie Joined: 11 Oct 2016 Posts: 6

So I changed the first #COND to ^-+$ and the second to #COND {^\s+(TH|BA|CL|PA|WA|SC|WH|BL|RE|DA|SH|DR)\s+(\w+)} {#ADDITEM GroupMembers {%2}} and it is now capturing names in the string. I had to take out the #state though because with it in it would only capture one name in the variable. I tried adding a third state #COND {^.*>$} {#STATE GroupCap 0} but my pattern would not match the command prompt.

403H 87V 6151327X 78.05% 2641C [**&groupmember:Fair**] [**Nulph Glug:Awful**] Mem:1 Exits:S>

It all seems to work fine without this addition anyway though. Is it necessary to reset the state to 0? It seems to automatically start from state 0 everytime I hit group. If there is benefit to using #state perhaps you can help me regex the command prompt?

Thanks again for all input, getting things moving now...

Newbie Joined: 11 Oct 2016 Posts: 6

Fixed previous post, disregard this Rolling Eyes

Posted: Sun Oct 16, 2016 2:19 pm

Its because the third state is of type {LoopPat|Param=100}
Though since he only wants to capture 5 names, 100 seems a bit excessive.

Essentially it will stay in the third state for 100 lines.
#STATE 0 forces it to go back to the first state early (when error checking shows that this line is not a match for the group member).

SubAdmin Joined: 18 Nov 2001 Posts: 5182

With a Loop Pattern trigger it will stay in that state until it matches the pattern the specified number of times. Again the best system is to use the fixed width pattern that checks for what it wants. All you need to do is change the %trim function to %word or add the %word function.

Newbie Joined: 29 Oct 2016 Posts: 1

thanks guys. a bit more time and I was ready to take some pills just not to sleep and find what I need but thanks to your answers I found what I needed :)