Zugg Software :: View topic

Posted: Wed Jan 28, 2009 4:50 am

For me at least figuring out how to capture and store the following is proving extremely difficult.

[ 73] bladder slice [ 28] blue ink [ 26] bone

It presents itself on the screen as shown. And it just the first of many lines like it. I am trying to capture each value individually and store them as a variable.

[ 73] bladder slice would be stored in a single variable and so on.

My issue is catching the numbers inside the [ ]
Also if the value is 0 then it will not appear in the list.

Any ideas on how to catch these lines?

Apprentice Joined: 14 Sep 2007 Posts: 167 Location: aztx

#TRIGGER {~[ (%d)~] (*) ~[ (%d)~] (*) ~[ (%d)~] (*) } {#additem VarStowslees {~[ %1~] %2};#additem VarStowslees {~[ %3~] %4};#additem VarStowslees {~[ %5~] %6}}

Well I guess that's one way.

Posted: Wed Jan 28, 2009 5:08 am

I will give it a try thanks

Input the code...

Trigger reads
~[ (%d)~] (*) ~[ (%d)~] (*) ~[ (%d)~] (*)

and the command it executes
#additem Cache {~[ %1~] %2}
#additem Cache {~[ %3~] %4}
#additem Cache {~[ %5~] %6}

Doing this it stores nothing to the @Cache string.
Also... quick question. In doing this will I be able to refer to each items Number specifically?

[ 73] bladder slice
@bladderslice = 73 is my intent. If at all possible, or at least some way of referring to its value.

Apprentice Joined: 14 Sep 2007 Posts: 167 Location: aztx

Funny, I tested it and it worked.

#TRIGGER {~[ (%d)~] (*) ~[ (%d)~] (*) ~[ (%d)~] (*) } {#ADDKEY Cache {%2=%1|%4=%3|%6=%5}}

How's that?

Posted: Wed Jan 28, 2009 6:05 am

When using the full version it doesn't seem to catch anything, could it have to do with there being the possibility of two words?

When using ~[ (%d)~] (*) I get

bone slice [ 18] castorite [ 139] castorite slice =158

as the value... it copies the entire line.

Apprentice Joined: 14 Sep 2007 Posts: 167 Location: aztx

Using that trigger you just gave will capture the entire line.

So if you did #show @Cache you would Not get:
bladder slice73blue ink28bone26

Is this the entire line? [ 73] bladder slice [ 28] blue ink [ 26] bone
Or does it show more?

Posted: Wed Jan 28, 2009 6:23 am

It shows nothing when I use the #TRIGGER {~[ (%d)~] (*) ~[ (%d)~] (*) ~[ (%d)~] (*) } {#ADDKEY Cache {%2=%1|%4=%3|%6=%5}}

And this is everything I am attempting to capture... though it looks a lot prettier on the MUD screen to be sure.

Glancing into the cache, you see:

Apprentice Joined: 14 Sep 2007 Posts: 167 Location: aztx

the type of trigger you asked for and what you asked it to do: ~[ (%d)~] (*)
Are a lot different and I can't do that right now.
However,

#TRIGGER {~[(*)~] (*) ~[(*)~] (*) ~[(*)~] (*)} {#ADDKEY Cache {%2=%1|%4=%3|%6=%5};#show 1}

Works for me.
You will probably still need a regex? trigger to fire off likes like
[ 306] testis slice [ 10] tongue, hopefully someone else can get you one.
I might be able to days later.

Posted: Wed Jan 28, 2009 7:01 am

I really appreciate your time and help... and I did actually learn quite a bit from what you showed me. I will be able to use what you showed me in other places. Thank you again.

And just tested the code you gave me above... worked perfectly. I should be able to work with that.

Posted: Tue Feb 03, 2009 3:56 am

Hopefully my last shot on this topic... I was able to create a set of triggers that will capture everything in the code listed above with a few exceptions and have no idea why.

I use the triggers

~[%s(%d)~] (%w)
Command - #var %2 %1

And

~[%s(%d)~] (%w) (%w)
Command #var %2%3 %1

Problem it it catches the first instance of the trigger on the line and each contains multiple instances. Is there a way to make it so the trigger fires on each instance on each line?

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

I worked on those problems for days some time ago. I don't play Iron Realms games lately, so I don't know how portable or valid this code is. I do remember a lot particular bugs with tracking names in my rift, but discovered it was totally reliable to just trigger on adding and removing from the rift. So the easy answer is to remove all from the cache, then enable your tracking triggers. In the hope of being portable, I tried a multistate trig to capture what was already in the rift. Something here might interest you.

Posted: Thu Feb 05, 2009 5:57 pm

Damn, you guys like making this stuff more complex than it is.

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

*snuggle fang

Cool, I know I had finally gotten my trigger to work for cases of one or two items as well as the three, just not sure when now. I think that one up there (mine) does that though. Saving the page for reference.

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

I replaced spaces because I wanted predictable keys for future scripts, I replace apostrophes because I have no clue how all the functions define them. I did see Larkin use keys with spaces, but was not sure how I would process keys. Personally, spaces seem wrong. I don't know why. My ex told me the Romans didn't use them in Latin

Posted: Thu Feb 05, 2009 7:14 pm

The trouble with replacing them is that it only really helps when you yourself are interacting with the data. Any script that's working with it can be set to use a name with spaces just as easily as it can to use one without, and scripts that're using some data from the game will need to do the replacing every time. And the actual help it'll give you as a user is dubious, anyway, since you'll have to remember to replace the stuff you got rid of every time.

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

I had found #IF (whatever==%i) while looping and looping dbs unmanageable with spaced data, at least as I recall. My scripts were horrendous though, the output was beautiful, but the logic was interminable. I am sure I can find examples of why I needed to replace, only I would be afraid my methods were clunky and everyone else would have done something simple instead to the same results

Posted: Sun Feb 08, 2009 1:59 am

Thank you guys very much, and the script you wrote up Fang worked incredibly well. I really appreciate the assistance.

Posted: Sun Feb 08, 2009 3:00 am

In retrospect, I probably should've made the #trig {prompt} a #cond {prompt} instead. You may wish to delete the first two triggers and make that change. I've edited the post above.