Zugg Software :: Search

If that is the actual disired result, your original trigger will work with my script body.
It looked like a potential error is why i separated them.

If i am understanding right, that may have thrown off your count.
Do both lines display when your skill improves?

If so you should be using something like:
#TR {^You concentrate and constric ...

Not in CMUD natively.
But if you have a means to fire one in lua, or some other installed language on your system... potentially.

I will let Chiara know.

It is possible, but you need to insert an anonymous variable ({str1 | str2}) in the brackets.

#WAITFOR {{str1 | str2}} 3000 {do something if found} {do something if not found}

I logged into the game to see for myself.
Several of the exits are bugged in that they sometimes skip over rooms.

For example, you are going east through rooms 1-2-3.
Yet, going west from room ...

Usually the #FIND command will try and figure out where you are, short of that, you have to manually select a room, and then click the blue pushpin button to set that as your current location.
So lon ...

you can always manually set it if the TAG wont take
#NOOP %roomvnum(, %2)

Hmmm... Try this:

#TAG exit %replace(%6, " ", "|")
#NOOP %roomexit(, %replace(%6, " ", "|"))

try adding
#NOOP %roomvnum(,%2)

Oh, is your trigger set to be on prompt instead of on newline?
It's the checkboxes on the pattern tab. Er... the Script tab.

Well, you can remove the #SHOW message now that you have confirmed the trigger is indeed firing.
That is just a debugging tool to use whenever you are fiddling with the pattern.
I suggested #PRINT s ...

In the prompt, the 'RUSH' keyword is toggleable, so optional.

I can't get the mapper to recognize this correctly, for some reason.

If you ever want to be able to reference those to be able to do ...

You still haven't showed the actual trigger you are using.
Not fully. Just the pattern.
And definitely not in text form.

If you want help, make it easier for folks to help you.
We cannot copy an ...

Yes, the variables numbers are different because my pattern included an extra variable for the RUSH state.

I am explaining the code I provided, so i used my numbers.

Well we might need to test if the trigger is firing at all:

#PRINT I see the Prompt!

And to ensure the numbers use

#TAG vnum %3

You do still need to have the map in edit mode to update roo ...

Likely just a typo on my end, I wasn't looking at the help files.

I had to edit my pattern cause i saw an extra space in it.

First off, when dealing with code issues, actual manipulatable text is much preferred over images of text.

That said, many mapping issues can be solved my making triggers to tag (#HELP #TAG) the va ...

Did you give it permission? If not that could be the issue right there.
Has the system been running to long? Might simply need a reboot.
Have you made any recent changes to your system?
Worse case ...

perhaps delete all the broken/unneeded stuff prior to converting

Try this:

~[H&%d{hit} M&%d{mana} V&%d{move}~]

It forces to only match with integer values.

The issue in this example is that the square brackets have another meaning where pattern matching is concerned (it expresses a range of acceptable characters).

In order for you to get the trigger t ...

It is possible, in fact, I have that very trigger.

#ALARM {0:00:00} {#LOG %concat(%sessionid, " ", %time(yyyy-mm-dd), " ", %time(hh), "00.txt")}

I also use the following:

#EVENT onConnect {#L ...

Thee issue here lies in the order of the various components in the corpse.

I would instead just reference %concat(@thisCorpse, ".corpse") in the grabber part of the stated trigger in the other thr ...

#TR {Obvious exit{s|}:} {thiscorpse=0)

would also work