Zugg Software :: Search

%x would match the non-white space, so it eliminates the need of training.
Your (%x) is: (%d)
Should work just fine
The issue isn't writing to the variable. The issue is when he is trying to access ...

#show @{strike-number}
Or as Hpoonis says, #Trigger {Your strike-number is: (%d)} {#Var Strikenumber %1}

If you was to do...

#LOOPDB @Grade19 {#SHOW %key "=" %val}

what do you see?

He isn't writing to a dbvar, that's why your code did nothing.
You would use #LOOPVIEW {#SHOW %rec} to see what it ...

You grin proudly as you slay (*)

I created a database named Grade19 with two columns - Column 1 = Monster Type = Text and Column 2 = Kills Type = Number

Script I currently have

#DBLOAD Grad ...

Right click on the down arrow that shows past commands. Go to WIndow Options, and Re-Check Show Mud Output option.

Nothing that I can think of, no. You could write a script to handle it for you, however.
This script would activate off movement commands, check if you are currently in a walk,
if so, add commands t ...

By using %1 in a trigger pattern, you open yourself to vulnerabilities and abuse by others. Basically, using %1 matches everything, including special characters. Someone can abuse your triggers in-gam ...

You have to set the class of your new trigger to be in a different class to the mapper triggers.
Before you set the trigger in the roomscript, try putting #class "NewTriggerClass"
It should then be ...

It would be easier if your prompt started with a special character such as |.
As such, you will need to create a trigger to capture the mana level. Ignoring
the first 2 pieces of information, which ...

It should automatically grab anything between the roomname and the room exits as the description. If you open up the mapper, and run New Configuration, and go through that. Then after it captures the ...

Basically, he's saying that to use %1 as a variable, you cannot place it inside quotes. That would tell the script you want it to treat %1 as LITERALLY %1, and not whatever it contains.

For starters, you do not need the * in your trigger pattern. The pattern will match if the words you're searching for appear anywhere in the line anyway. Secondly, to match an item in a string list, y ...

Wouldn't the problem be that the trigger triggers off (*), and that means it doesn't fire when it receives a null line?
Hence, it does not reset the state of the trigger. A better trigger would be:
...

Yeah, there's a slight difficulty with %replace turning it into a string and stopping it from further expansion, even %eval wouldn't expand it further, however, the %exec function was able to force it ...

Try this one:
#trigger {(.*)} {#substitute %subregex(%1, "(\^F)", "@RandHigh")}

Or this one:
#trigger {(.*)} {#substitute %subregex(%1, "(\^F)", "%expand(@RandHigh)")}

This is probably the mos ...

Really? It doesn't do that for me. It expands it just fine. Hmmm. Maybe a setting somewhere.

I'm not sure what you need with regards to the water. Maybe you can give us some output of what is happening.
Here's something for you to color the rooms automatically:

#alias onroomcreate {#if %p ...

Actually yeah, it would, lol.

However, there is a way around that. By delaying the point at which the function @RandHigh is expanded.
With quotes, like so:

#trigger {(.*)} {#substitute %subregex(%1, "(\^F)", "@RandHigh()")}

Hmm, you're right. Because its calling the function.

Ahh. What you want to do, is instead of replace, use subregex.

#trigger {(.*)} {#substitute %subregex(%1, "(\^F)", @randHigh())}

Also, you can do this:

#SETPROMPT "HP" hp maxhp sp maxsp mp maxmp

And Myddrun, why don't you like setting the variable in the trigger pattern? It does make things easier.

I did something similar to this once. The hardest part is not adding points, but sorting them out into who has the most points. That's fun.
Here's something for you:

#trigger {{@PlayerList} quest- ...

This should do what you require:

#CLASS {tracker}
#VAR clannames {the Ebon Fist}
#VAR Houseenemies {}
#TRIGGER {Enemies of @ClanNames:} {Houseenemies=%null}
#COND {!%match( %line,"Total:")} ...

Otherwise, the other possibility is you've detached the command bar. In which case, you can just follow my above instructions and instead of selecting Show Mud Output, re-Attach the Command Line.