Zugg Software :: View topic

Magician Joined: 23 Jul 2005 Posts: 334 Location: Chicago

Well... I've been posting alot on here, so I thought that I would break it down a lil more and get some help with just what I need. So here goes. Am I using %line{num} correctly? TIA!

Posted: Wed May 14, 2008 3:06 am

No. %line isn't a function, it's a variable. It contains the most recent line of text. If used in a trigger, that's the line that fired the trigger.

Magician Joined: 23 Jul 2005 Posts: 334 Location: Chicago

Ah... So you would use %line(1) to point to the line that fired the trigger? So it would be used something like this instead? (In continuing with the code from the first post.)

Posted: Wed May 14, 2008 12:30 pm

No. Like I said, %line isn't a function, it doesn't take any arguments. It's a variable, like %1 is a variable. You use %line in your scripts, not %line(number). Remove the (1) part.

Though you need to be sure that that'll do what you want, because word wrapping might mean that %line has stuff in it that's nothing to do with the trigger match.

And now I think about it, your #var syntax is potentially wrong. You're setting the default there when I think you mean to be using #addkey to set up a dbvar.

Magician Joined: 23 Jul 2005 Posts: 334 Location: Chicago

Mmmm.... Ok, that makes a lil more sense. LoL! So... I'm thinking this is looking better?

Posted: Wed May 14, 2008 4:29 pm

You need to be very careful setting up a dbvar manually with the #var command. The spaces and non-alphanumeric characters you have in it might cause problems. Were it me, I'd use #addkey to set up the initial variables as well, because then you know for sure you're getting what you want. So:

#addkey sob_list "Galloping by, a horse nearly runs you over." "Stallion"

etc.

And okay, I understand where you're going with this script now. I suspect you'll need to use %2 rather than %1 in your gob_list trigger, because the brackets () around the {@gob_list} will cause the entire match to be captured into %1. Which, I suppose, would be pretty handy - you can replace your use of %line with %1.

The fundamental problem here, though, is that you're adding a key based on %line to the mob list when what you want is the key in mob_list to be the value of gob or sob that matches that line. So change %line to %db(@gob_list,%line) or %db(sob_list,%line) (or %1 if you decide to go that route). Hopefully you understand what that'll do - it's the reason, I think, that you changed your *ob_list variables to dbvars in the first place.

Posted: Wed May 14, 2008 11:05 pm

He could create a db variable as follows:

Posted: Wed May 14, 2008 11:08 pm

He could do it that way (even without explicitly setting the type as you do there), but the trouble is that his keys are very long and contain spaces. So he can't do that in this case.