Zugg Software :: View topic - Creating a list from the contents of a container

Beginner Joined: 15 Sep 2005 Posts: 14 Location: USA-CA

I'm trying to create a list variable from the contents of a container. A portion of the container is:

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

You really only need three triggers:

1)trigger on A Card Collector contains:. This trigger will do any of the preliminary work you might need/want--setting variables to zero, enabling other triggers, etc.

2)trigger on (#001) Card 1. This trigger will do nothing but fill in the variables, and since each card follows the same format (and since we're only interested in card numbers) we don't need 200 separate triggers for this.

3)trigger on whatever ends the list. It might be your prompt, it might be a blank line, or it could even be trailing lines about help/status. This trigger will do the figuring and calculating, which you have moreorless correct in the #FORALL.

Beginner Joined: 15 Sep 2005 Posts: 14 Location: USA-CA

I got 2/3 working...the #FORALL is screwing me up. In it's current state:

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

#FORALL @cardlist {#if [red]![/red]%ismember( %i, @containerlist) {#ECHO Missing Cards: %i}

Beginner Joined: 15 Sep 2005 Posts: 14 Location: USA-CA

Ok, I am posting my script in all it's glory because nothing is working now. Nexela's script only sends me into an infinite trigger loop that can only be shut down when zMUD asks me to disable the trigger (which doesn't even work) and the class won't disable either. To top it off, for some reason, the settings editor stopped recognizing it's own commands - for example, as i manually type a #FORALL script, the WHOLE line will be in black, no matter what I do. It won't even let me copy and paste either because I get the same results. I think this trigger class is screwing my whole client up. Anyway, here it is, I need massive help!

Newbie Joined: 17 Sep 2005 Posts: 5

That is screwing you up because the line
#TRIGGER {$} {#FORALL @cardlist {#if !%ismember( {%i}, @containerlist) {#ECHO %i}};#T- Smurf}

THis line triggers at the end of the line. but since you give it no pattern to match it will match at the end of EVERY line, including your output lines. Since the #T-Smurf doesnt execute till the #FORALL statement is finished, you wind up matching ALOT of endlines, and running ALOT of for all statements.

Find a better match statement for the end trigger. If the $ is your prompt for your mud, you need to put ~ in front of it, because $ is a zmud wildcard to force the trigger to match at the end of a line.

That should stop your eternal trigger problem. Not sure tho, writing this at work and cant test it on my own right now. If it does fix it, but doesnt get the output right, ensure your cardlist variable is being populated correctly.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

The cardlist variable is not truly needed since it is a continuous series of numbers. You can use #LOOP instead to have the same sort of series, it is up to you whether you want to eliminate the variable.

#TRIGGER {^$} {#T- Smurf;#ECHOP "Missing Cards: ";#FORALL @cardlist {#if (!%ismember("%i", @containerlist)) {#ECHOP "%i "}};#ECHO {}}

Beginner Joined: 15 Sep 2005 Posts: 14 Location: USA-CA

I need the cardlist variable because zmud defaults 001 to 1 and 099 to 99 and the keywords for these cards are 200-001. Unless I can force zmud to register 001 AS 001 I don't know any other way around it.

As for the two suggestions, I'm working on them :D Fiddling with page pausing because it seems to be scrolling too fast and sometimes zmud stores the wrong info into the containerlist var which screws it up.

I'll post something as soon as I make some headway.

Thanks all for helping and for those who do later as well ;D

(little bit later - my containerlist is not populating correctly. I've tried setting it to be empty using #var containerlist "" but it doesn't seem to be working at all. Not to mention I keep capturing the ( ) around the card numbers sometimes. I think it's moving too fast.)

Beginner Joined: 15 Sep 2005 Posts: 14 Location: USA-CA

I got it working spot in. Found out that my container var wasn't filling because it was INSIDE the class I was enabling, causing me some issues with triggering the blank line. Moved things around and viola! Worked like a dream. Thanks for bearing with me and giving me some help :)

Beginner Joined: 15 Sep 2005 Posts: 14 Location: USA-CA

Ok, one more question :) I have the following trigger:

~(~#(%d)~) (*) ~*Smurfemon Card~*$

and i do #ADDITEM containerlist %1

What I would like to do is add both the %d and * into one line into the string. For example...

(#198) B.S.O.D. Smurf *Smurfemon Card*

and I get 198 and B.S.O.D. Smurf and put them into one line of the container list var so it looks like:

198 B.S.O.D Smurf

I've used commas, | , and {} and parentheses....haven't an idea how to do it.

Wanderer Joined: 02 Sep 2005 Posts: 60

There's two main ways to handle that.

#VAR Card {%concat(%1, %2)}

or simply

#VAR Card {%1 %2}

Either should work.

Beginner Joined: 15 Sep 2005 Posts: 14 Location: USA-CA

I tried both using #ADDITEM no dice. not sure what's going on. I almost think it doesn't want to add %2. If I echo it to my terminal, I get the right name.

Apprentice Joined: 20 Sep 2005 Posts: 135

Would using quotes around %2

#VAR Card {%1 "%2"}

add the "text" portion.

Beginner Joined: 15 Sep 2005 Posts: 14 Location: USA-CA

Ok I got this working. I forgot to change my two variables to have the same matching patterns. I used #ADDITEM containerlist (%1 %2) so it would have the format 001 Card Name. Works great.

Only problem I am having is comparing the two variables...maybe it's too much text for it to handle? it adds in cards that ARE listed in both varaibles and therefore should not be echoed to my window. Is there a certain trick to preventing this or do I have to do something special for comparison because of adding %1 and %2 into the same text string?

Wanderer Joined: 02 Sep 2005 Posts: 60

The FORALL in this trigger looks fairly time consuming. It may help to make it a priority sequence. If it is 'too much text' for it to handle this should resolve it. Note, I also see that your {$} trigger has been changed to something, obviously you should include any such changes, this was just the only copy I could see to grab.

A good way to test this is to color each line that you trigger on so that you can SEE if a trigger line gets skipped or not.

#TRIGGER {$} {
#PRIORITY {
#FORALL @cardlist {#if !%ismember( {%i}, @containerlist) {#ECHO %i}}
#T- Smurf
}
}

Beginner Joined: 15 Sep 2005 Posts: 14 Location: USA-CA

My actual trigger to capture the items works fine. The variable populates perfectly. I checked it manually and found no errors. During the comparison, there seems to be an error. My capture trigger is as follows:

#TR {~(~#(%d)~) (*) ~*Smurfemon Card~*$} {#ADDITEM containerlist {%1 %2}}

which works perfectly.

Once the end of the list is encountered, I do the followng:

#TR {^$} {#T- Smurf;#WAIT 1000;#WINDOW Smurf "Card Count:" %numitems( @containerlist);#FORALL @cardlist {#if (!%ismember( %i, @containerlist)) {#WINDOW Smurf %i}};put smurfedex belt}

This is to compare and report missing values. Problem is that it is reporting values that are identical in BOTH variables that it shouldn't be reporting.

I'm still tweaking it, and any comments are appreciated!

SubAdmin Joined: 18 Nov 2001 Posts: 5182

You shouldn't need the #WAIT since you are sending your output to a seperarate window. Using #WAIT in triggers tends to have some very bad consequences, even for just the 1 second you have.

Next I would suggest putting some surrounding characters in your output with #WINDOW. This will help you identify the problem if it is an odd trailing space. #WINDOW Smurf {Missing '%i'}

Also keep in mind that %ismember is a case-sensitive function. Upper and lower case as well as spacing must match exaclty. I would suggest having output on all the cards while debugging. Inside the #FORALL just before the #IF add in #WINDOW Smurf {Checking '%i'}

Once debugging is done you can remove that line.

Beginner Joined: 15 Sep 2005 Posts: 14 Location: USA-CA

It's not a matching issue because the funky values are the same throughout. There are no wrapping issues involved because i put ' ' around it and everything stayed on lined spaced nicely. As for the #WINDOW...wouldn't work. got weird syntax errors no matter how i put it in there with the #if statement.

so i'm at a loss. there should be no reason for it to bugger up like this. I'll leave it as is unless somebody as a solution cause I can't find one.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Sometimes syntax errors can actually be ignored. The syntax checker is more picky then the parser and doesn't always know every exception there is.

%i is subject to a form of early expansion and should be surrounded with quotes in your %ismember.
#if (!%ismember( "%i", @containerlist))

Beginner Joined: 15 Sep 2005 Posts: 14 Location: USA-CA

Ok nailed the problem down. Thanks to vijilante with the " " around the %i i also used a #priority when capturing the cards. but this is the problem:

the " " in certain card names are killing it. making it appear as if they aren't there when they are. i checked both vars and they are the same just not recognizing the quotes. so what do i do to force the quotes to be recognized?

Beginner Joined: 15 Sep 2005 Posts: 14 Location: USA-CA

got it! used %quote(s) syntax around my two variables for output.

thanks everybody for your help!