Zugg Software :: View topic

Beginner Joined: 01 Aug 2006 Posts: 21

Hello everyone, I'm trying to make an identify trigger to relay the statistics of an object to the whole group. Now I know I could make seperate triggers for each affect and it tell the group each one individually, but I was wondering if there was a way to capture each one and relay them to the group all at once.

Here is an example of a piece being identified:

You feel informed:
Object 'a gold braid', Item type: Armor
It can be worn: Inventory Arms
Item is: NOBITS
Weight: 5, Value: 8500, Rent: 850
AC-apply is 8
Quality: INDESTRUCTABLE
Can affect you as :
Affects: Hitpoints by 13
Affects: Dexterity by 8
Affects: Combat Ability by 2

Basically I just want to be able to tell the group in one line, Affects Hitpoints by 12, Dex by 8, and Combat by 2, rather then multiple lines for each affect. Thank you.

Beginner Joined: 01 Aug 2006 Posts: 21

anyone know?

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

What comes after the last Affects: line? Since I assume that the number of Affects: lines will vary from item to item, you're going to require either three separate triggers or one single-state trigger and one multi-state trigger with three states:

#trigger {Object ~'(*)~'} {Item = "%1"}
#condition {Can affect you as:} {#T+ tItemAffects;Affects = ""}
#condition {whatever line comes next} {#T- tItemAffects;grouptell @Item %expandlist(@Affects,",")}

#trigger "tItemAffects" {Affects: ([%a%s])} {#additem Affects "%1"}

Beginner Joined: 01 Aug 2006 Posts: 21

Yes the number of affects vary from item to item, but after the affects is nothing. I tried using these triggers with no success.

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

No prompt or anything? Is there at least a blank line?

Beginner Joined: 01 Aug 2006 Posts: 21

Ah yeah after I scan an item I of course can see my prompt. Sorry about that.

Beginner Joined: 01 Aug 2006 Posts: 21

1097(1249)hitp 1561(1711)mana 166(283)move> This is what my prompt basically looks like

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

That is what you'd match on for the third state (that's the second #CONDITION). The pattern should be easy to figure out--~ in front of each of the parentheses, %d for the numbers, and so on. Don't forget to set the Trigger on Prompt option, too.

Beginner Joined: 01 Aug 2006 Posts: 21

still can't seem to get it to work heres what I have

#trigger {Object ~'(*)~'} {Item = "%1"}
#condition {Can affect you as:} {#T+ tItemAffects;Affects = ""}
#condition {(%d)~((%d)~)hitp (%d)~((%d)~)mana (%d)~((%d)~)move~> } {#T- tItemAffects;grouptell @Item %expandlist(@Affects,",")}
#trigger "tItemAffects" {Affects: ([%a%s])} {#additem Affects "%1"}

I set it to trigger on prompt, but still nothings happening when I identify.

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

I don't suppose you checked Trigger on Prompt for ALL the triggers and conditions, did you? It occurs to me that I was a little unclear with that, as I meant only to check it for the prompt condition. Everything else should stay on Trigger on Newline.

Beyond that, you can use #SHOW or #SAY to verify that each trigger or condtion is firing.

Beginner Joined: 01 Aug 2006 Posts: 21

ah ok I've seen to have gotten it to work, just have one little problem whenever an item gives a negative affect (i.e. Affects: Wisdom by -3) all it says is Wisdom by (blank). Any idea how to fix that?

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

just add in - to the range pattern used in the tItemAffects trigger -- [%a%s-]

Ditto for any other symbolic characters that appear

Beginner Joined: 01 Aug 2006 Posts: 21

Ok got that to work, thanks. Now just one more dumb question for all you smart people and I'll be happy. =) These are the triggers I have so far:

#trigger {Object ~'(*)~'} {Item = "%1"}
#condition {Can affect you as:} {#T+ tItemAffects;Affects = ""}
#condition {(%d)~((%d)~)hitp (%d)~((%d)~)mana (%d)~((%d)~)move~> } {#T- tItemAffects;grouptell @Item %expandlist(@Affects,",")}
#trigger "tItemAffects" {Affects: ([%a%s-])} {#additem Affects "%1"}

Now if I wanted to add the item level and the ac it applys how would I do that? Heres what that looks like on identify

You feel informed:
Object 'a lizard's smoldering cap', Item type: Armor
It can be worn: Inventory Head
Item is: Magic
Weight: 1, Value: 29100, Rent: 2910
Minimum Level: 37
AC-apply is 2
Quality: INDESTRUCTABLE
Can affect you as :
Affects: Wisdom by 4
Affects: Hitroll by 1
Affects: Combat Ability by 1
Affects: Mana by 18

I just want to add the Minimun Level line and the AC-apply line. Again thank you Matt for all this help. =)

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

Just make a new trigger similar to.

#trigger "tItemAffects" {Affects: ([%a%s-])} {#additem Affects "%1"}

Only matching, (AC-apply is [%a-])
instead of, Affects: ([%a%s-]), and of course Do the same thing for item level.

Beginner Joined: 01 Aug 2006 Posts: 21

#trigger {Object ~'(*)~'} {Item = "%1"}
#condition {Can affect you as :} {#T+ tItemAffects;Affects = ""}
#condition {~<(%d)~((%d)~)hitp (%d)~((%d)~)mana (%d)~((%d)~)move~>~((%d) EXP~)} {#T- tItemAffects;gt %expandlist(@Affects,@Ac"|")}
#trigger "tItemAffects" {Affects: ([%a%s-])} {#additem Affects "%1"}
#trigger "tItemAffects" {AC-apply is ([%a-])} {#additem Ac "%1"}

I tried something like that but it doesn't work, suggestions?

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

Unless the AC, Level, and whatever else you'd want to add doesn't appear for all items, I would suggest forgoing separate triggers and simply add in #CONDITIONs in the appropriate places. The easiest way to do this is in the States tab for the multi-state trigger I provided. Because these are in fixed places and thus can be part of the multi-state trigger, you wouldn't necessarily have to save the info to a variable first:

#trigger {Object ~'(*)~'} {Item = "%1"}
#condition {Minimum Level: (%d)} {}
#condition {Can affect you as:} {#T+ tItemAffects;Affects = ""}
#condition {(%d)~((%d)~)hitp (%d)~((%d)~)mana (%d)~((%d)~)move~> } {#T- tItemAffects;grouptell @Item MinLvl~: %t2 Affects~: %expandlist(@Affects,",")}
#trigger "tItemAffects" {Affects: ([%a%s-])} {#additem Affects "%1"}

The AC would appear after the bold part, and would correspond to %t3.

Beginner Joined: 01 Aug 2006 Posts: 21

Thanks Matt, that way works. However I've noticed that when a certain object doesn't have a Minimum level (since not all do) the trigger doesn't fire, is there a simple way to fix this?

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

You could try changing the condition type to something like duration or withinlines. These two types will invalidate the current trigger condition if it's not found within the specified parameters so that it doesn't just hang waiting for something that never comes, but I'm not entirely sure if it continues on with subsequent conditions or simply resets the trigger entirely (the latter will make it so that subsequent conditions never match.)

If the latter happens, you'll just have to remove that #CONDITION and convert it to a #TRIGGER.

Beginner Joined: 01 Aug 2006 Posts: 21

when I change the condition to duration or within lines the trigger fires but it makes up a huge number for minlevel in replace of nothing. how would the trigger look like?

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

Because you are just telling a group of friends this information and throwing it away, there is no reason to store it in a seperate variable.

You are using the expandlist command improperly and using a different variable in your example.

%expandlist(@Affects,",")
Is the correct syntax. What you are doing here is telling zmud that you want to see the variable list named Affects with the comma as your seperator.

%expandlist(@Affects,@Ac"|")
Here you have told zmud that you want to see the Affects varable list with whatever is inside your Ac variable list and the pipe as your seperator. This under extremely rare circumstances actually output something comprehensable. But isn't what you want i'm sure.

Try these.

Beginner Joined: 01 Aug 2006 Posts: 21

Edited.

Beginner Joined: 01 Aug 2006 Posts: 21

actually I might have posted too soon. It seems whenever I add a trigger such as this:

#trigger "tItemAffects" {(AC-apply is [%a%s-])} {#additem Affects "%1"}

For ac level it seems to replace the old one for affects which is this:

#trigger "tItemAffects" {Affects: ([%a%s-])} {#additem Affects "%1"}

I tried changing ttemAffects to another name but then the trigger doesnt work. Sorry for this guys...

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

Sorry I forgot to add that you need to make sure that your second trigger is turned on and off.

#T- tItemAffects
Turns off your first trigger
#trigger "tItemAffects" {Affects: ([%a%s-])} {#additem Affects "%1"}

So add a line for the other trigger to turn off the second trigger.
#T- tItemAffects2
#trigger "tItemAffects2" {(AC-apply is [%a%s-])} {#additem Affects "%1"}

You get this.
#condition {~<(%d)~((%d)~)hitp (%d)~((%d)~)mana (%d)~((%d)~)move~>~((%d) EXP~)} {#T- tItemAffects;#T- tItemAffects2;gt %expandlist(@Affects,", ")}

And of course you need to make sure they are both turned on.

#T+ tItemAffects
#T+ tItemAffects2

#condition {Can affect you as :} {#T+ tItemAffects;#T+ tItemAffects2;Affects = ""}

I'm off to bed. Good luck.