Zugg Software :: View topic

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

This seems to come up fairly often, so I decided to post my standard solution here.
#TR {Inside the (*) you see (*).} {#GAG;#VAR container {%1};#VAR contents {%2};#VAR contents %replace( {@contents}, ", and ", "|");#VAR contents %replace( {@contents}, ", ", "|");#VAR contents %countlist( @contents);ContentsSummary}
#AL ContentsSummary {#SAY Inside the @container you see;#LOOPDB @contents {#SAY %val %key}}

To create script, copy both lines to your command line (not the Settings Editor).

This works with MUD output similar to:
Inside the open large leather backpack you see a feathered birch spear, a feathered birch spear, a feathered birch spear, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, a quiver of oak arrows, and a quiver of oak arrows.
The output must all be on a single line, which can be a line wrapped by zMUD.

It converts it to a display similar to:
Inside the open large leather backpack you see
3 a feathered birch spear
22 a quiver of oak arrows

Enchanter Joined: 20 Nov 2002 Posts: 627 Location: USA

#TRIGGER {^Inside the (*) you see (*).} {container={%1};contents={%2};#VAR contents %replace(%replace( {@contents}, ", and ", "|"), ", ", "|");contents=%countlist(@contents);#Sub {Inside the @container you see};#LOOPDB @contents {#say %val %key}}

Wouldn't this work the same and be a bit more compressed?

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

There are many ways to do this. I could probably nest all the functions and get @contents with a single #VAR statement. I chose not to nest functions to make the script easier to understand.

The #LOOPDB should take significantly more time than any other portion of the script, so it doesn't really matter, timewise, whether the remaining statements are nested or not.

Enchanter Joined: 10 Oct 2000 Posts: 656 Location: USA

Good Script Lightbulb, would you mind making one change to throw all the code into a class to keep it seperated. I always have trouble writing scripts and specifying the class. I forgot where to place the class name in some of the syntax, and I still have not figured out the . notation for variables within classes in case somebody has another variable by the same name.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

If you want it in a separate class, just add a #CLASS command before the script and a #CLASS 0 at the end of it. If you want the variables to also be in that class, include the SETDEF option in the #CLASS command.
#CLASS Talahaski setdef
script goes here
#CLASS

Apprentice Joined: 22 Jul 2004 Posts: 118 Location: USA

what i normally get when i look in my pack is:

so tried to edit the script it would work for this and this is what i got:

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

Apprentice Joined: 29 May 2002 Posts: 121

After reading this thread, I made something similiar to it where it takes several lines, puts them all into a string and then returns an itemized list. Thanks Lightbulb for the original idea.

If you care to download the script, go to the following link.

http://infernalworlds.com.9.m6.net/smf/index.php?topic=1853.0

Wanderer Joined: 06 Apr 2007 Posts: 59

I took this and cleaned it up slightly, and changed the trigger a bit for GSIV.