Zugg Software :: View topic

Posted: Wed Mar 26, 2008 10:06 pm

change your square brackets to round ones and it might work

Wizard Joined: 26 Mar 2008 Posts: 1547

And I would encase the entire thing in { }?

Posted: Wed Mar 26, 2008 10:12 pm

Wizard Joined: 26 Mar 2008 Posts: 1547

Is it possible to explain what you changed?

Wizard Joined: 26 Mar 2008 Posts: 1547

Hmm,

Liluye tells you (Elvish) 'Testing!'

and

Liluye tells you 'Testing!'

didn't work.

Posted: Wed Mar 26, 2008 10:20 pm

Wizard Joined: 26 Mar 2008 Posts: 1547

Possibly, but none of them work. :/

Posted: Wed Mar 26, 2008 10:27 pm

you need to make sure the trigger is set to regexp, not normal trigger, the normal trigger would be vastly different

Wizard Joined: 26 Mar 2008 Posts: 1547

How do I set it to regexp?

Wizard Joined: 26 Mar 2008 Posts: 1547

I set it, nevermind.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

I'm not sure what you want to do with the text once you have matched it. If you really did mean that you wanted to capture the text then you probably want to save it into %1.
For that you would use this pattern. [On the bottom right of the editor window under the trigger priority box you would check the Regular Expression box to make a trigger a regex trigger.]

Wizard Joined: 26 Mar 2008 Posts: 1547

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

Well, you would probably need to use \n instead of \r to match your line breaks/carriage returns for starters.
Next you need to actually know where the line breaks are... It can all get very messy.

If you use multi state triggers it is easier. I usually turn on or off several triggers based on a pattern instead of trying to match all possible combinations of line breaks.

#T+ triggerName

Turns on a trigger.

#T- triggerName

Turns off a trigger

Wizard Joined: 26 Mar 2008 Posts: 1547

I'll give you an example and we'll see what you think. I know where every line will end, yes.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

(?:) means match what is in here but throw away the result. () means match what is in here and save the result to the next open %n. %n being %1 %2 %3 etc.

| is the OR character so this|that means to match this or that.
. matches any single character.
.* means match any combination of characters including none but excluding new lines or carriage returns.
.+ means the same as above except it does NOT include none + means one or more * means any amount.
\ is the escape character.

Wizard Joined: 26 Mar 2008 Posts: 1547

So here's an example of a DSL quest:

Posted: Thu Mar 27, 2008 8:29 am

Okay, you're making this a million times more difficult than it needs to be :P There are far too many .*s in that pattern, which'll slow it down immensely. Here's something for you:

(tells you(?: \(\w+\))?|You tell \w+|You tell the group) '

This matches all those tell lines and should do so quite quickly. Depending on what you want you want to do, it might not have enough captures - if you give us the details of the script, we can suggest a better pattern. If you want to do something with the name and text, you could try this instead:

^(?:(\w+) tells you(?: \(\w+\))?|You tell \w+|You tell the group) '(.+)'

Triggers can turn one another off if the trigger has an ID (there's a field for it in the package editor). You then use the ID with #t+ and #t-.

However, capturing all that text is pretty easy.

#regex {You ask (.+?) for a quest} {QuestGiver=%1#t+ QuestCap}
#cond {You have (%d) hours to complete this quest} {#t- QuestCap}

#trig "QuestCap" {^@QuestGiver says '(*)'} {} "" {disable}

This uses a multistate trigger.

Wizard Joined: 26 Mar 2008 Posts: 1547

The tells one I have right now works. I'll be looking into multi state triggers, thanks.

Wizard Joined: 17 Jun 2006 Posts: 1201

The fastest way to match something in between quotes or brackets is a negated character class.

Wizard Joined: 26 Mar 2008 Posts: 1547

Ah, alright. Well, I'd change it, but I sort of want to find out why I have to create them every session for them to work. They don't disappear, they're still there. But they won't work unless I recreate them.

Posted: Thu Mar 27, 2008 4:28 pm

Your comments about negated character classes are true, but only when the tell can never contain the quotes that surround it. Since that's rarely true (especially given that the quotes in this case are apostrophes, which people use in tells all the time), your regex will miss bits off of many tells. \w+ is fine for the language name, but you need to use the dot for the tell because the tells can contain any character. It should only backtrack one step to match the apostrophe at the end, so that's not a problem. By the time it reaches the dot, the match isn't going to fail.

Wizard Joined: 17 Jun 2006 Posts: 1201

What do you mean they don't work? Are they grayed out and disabled? You have to make sure the Regular Expression option for the trigger is checked.

Wizard Joined: 26 Mar 2008 Posts: 1547

They work, then I disconnect. I come back, connect to mud, disconnect and reconnect to avoid the stupid Read-Only bug and a select few of my triggers won't fire. Nothing has changed, they aren't disabled or anything. They just wont fire.

Wizard Joined: 17 Jun 2006 Posts: 1201

Oops Fang is right. More than likely someone will use an apostrophe or quotation mark within the quote so use .+.

As far as the read only thing and triggers not working, I'm not really sure what you are talking about.