Zugg Software :: View topic

Newbie Joined: 12 Feb 2009 Posts: 6

I'm having a bit of difficulty with this, because zMud isn't quite working as well with my
new computer as my old one, so naturally I was excited about cMud which runs smoothly
on it. I have this old zMud script written up, it's more of a series of complex triggers
really, and it doesn't seem to fire correctly when uploaded into cMud, I'm certain this
is because of some minor alteration in syntax that I'm having difficulty narrowing down,
I was hoping for some guidance from a helping hand.
the zMud script is as follows, and is meant to identify where tokens are (something shiny) in adjacent
rooms using a command that in the game scans them, then travel to said adjacent room (up to three away)
collect the item, and return to the spot of origin from whence the rooms were scanned. It takes into account
some serious variables when determining what will fire the trigger, and is going to be a pain to rewrite if
I can't figure out where to begin:

#CLASS {Dwarf} {enable}
#ALIAS scan {
#VAR dir {}
#VAR distance 0
#T+ scan
~scan
emote done
}
#VAR imps {31}
#TRIGGER {You eat Spice of the black, aquatic centipede.} {scan}
#TRIGGER {Sammy done} {eat spice}
#TRIGGER {You do not have that item.} {
c gate delica
vis
#10 buy 50*spice
c dark
eat spice
}
#TRIGGER {Your vision blurs and feels limited.} {c far}
#TRIGGER {Some unknown magic holds you here.} {
C portal zein
enter gate
}
#TRIGGER {A pile of coins.} {get all}
#TRIGGER {*pile*} {get all}
#CLASS 0
#CLASS {Dwarf|scan} {disable}
#TRIGGER {Nearby (%w):} {
#VAR dir %1
#VAR distance 1
#IF (@dir = West) {#VAR backtrack East}
#IF (@dir = Down) {#VAR backtrack Up}
#IF (@dir = Up) {#VAR backtrack Down}
#IF (@dir = South) {#VAR backtrack North}
#IF (@dir = North) {#VAR backtrack South}
#IF (@dir = East) {#VAR backtrack West}
}
#TRIGGER {Not Far (%w):} {
#VAR dir %1
#VAR distance 2
#IF (@dir = West) {#VAR backtrack East}
#IF (@dir = Down) {#VAR backtrack Up}
#IF (@dir = Up) {#VAR backtrack Down}
#IF (@dir = South) {#VAR backtrack North}
#IF (@dir = North) {#VAR backtrack South}
#IF (@dir = East) {#VAR backtrack West}
}
#TRIGGER {Far off (%w):} {
#VAR dir %1
#VAR distance 3
#IF (@dir = West) {#VAR backtrack East}
#IF (@dir = Down) {#VAR backtrack Up}
#IF (@dir = Up) {#VAR backtrack Down}
#IF (@dir = South) {#VAR backtrack North}
#IF (@dir = North) {#VAR backtrack South}
#IF (@dir = East) {#VAR backtrack West}
}
#TRIGGER {- Something Shiny} {
#IF (@distance = 0) {~get all}
#IF (@distance = 1) {
@dir
~get all
@backtrack
}
#IF (@distance = 2) {
@dir
@dir
~get all
@backtrack
@backtrack
}
#IF (@distance = 3) {
@dir
@dir
@dir
~get all
@backtrack
@backtrack
@backtrack
}
}
#TRIGGER {Right (%w):} {
#VAR dir %1
#VAR distance 0
}
#CLASS 0

Thoughts?

Magician Joined: 17 Apr 2005 Posts: 496

This would be much easier with some sample output from the game. From your triggers, I think your game does something like this:

Wizard Joined: 22 Mar 2007 Posts: 2320

It would indeed be useful to have samples of the actual text.

I do see one bit of syntax that has changed between Zmud and Cmud. You can no longer start a command line with @ or %. Instead you would need a #call in front of it. Actually, for what you have, I would change, for instance, the "@dir;@dir;@dir" to "#3 #call @dir".

As an aside, the "#TRIGGER {*pile*} {get all}" can be simplified to "#TRIGGER {pile} {get all}", and "#TRIGGER {A pile of coins.} {get all}" is probably superfluous, since it also matches the other trigger.

Enchanter Joined: 09 Sep 2007 Posts: 605

Rahab

*cough*
I wished to write the same about "start line with command", but have made a test. What can I say - CMUD still executes single @dir or @backtrace lines. CMUD does send, say, @dir verbatim from the command line, but expand it value from within a setting.

Wizard Joined: 22 Mar 2007 Posts: 2320

Whoa, you're right. Embarassed

I have a vague memory of Zugg deciding to put that capability back in. It's still true for %, but not for @ (in scripts) I guess. And in any case, I should have said to use #send instead of #call, in this situation.

Newbie Joined: 12 Feb 2009 Posts: 6

[quote="gamma_ray"]This would be much easier with some sample output from the game. From your triggers, I think your game does something like this:

Newbie Joined: 12 Feb 2009 Posts: 6

To elaborate even further, when executed successfully in zMud this is what it looks like and how the trigger
responds:

Right Here:
- A medium-sized mutant
- A small mutant
-
- a large-sized mutant

Far off South:
- A small mutant
- A medium-sized mutant
- a large-sized mutant
- A medium-sized mutant
- Something Shiny
#3South
get all
#3North
- A medium-sized mutant

Wizard Joined: 22 Mar 2007 Posts: 2320

You say "it doesn't seem to fire correctly when uploaded into cMud." What do you mean? I don't see any syntax problems in your code. There are several places where it could be greatly simplified, but I don't see any reason why it shouldn't work. What exactly isn't working?

Newbie Joined: 12 Feb 2009 Posts: 6

Most specifically, it's firing "west get all" instead of "west" and then "Get all", I thought perhaps cMUD might have had a different syntax for separating multiple commands. It's firing all 3-7 of the trigger commands in one line, or one command.
West,
West
West
get all
in the script is returning
West West West Get all
with no carriage return between the commands, but it works just fine in zMud, not in cMud.

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

You may want to see if this works. Try going through the script and removing the line breaks in the #IF statements. For example:

#IF (@distance = 2) {
@dir
@dir
~get all
@backtrack
@backtrack
}

just change it in the editor to be #IF (@distance=2) {@dir;@dir;~get all;@backtrack;@backtrack}

I've had the occasional issue where I've reformatted a script in the editor, and the inserted line breaks sometimes end up doing this.

Magician Joined: 17 Apr 2005 Posts: 496

Wizard Joined: 17 Jun 2006 Posts: 1201

I noticed you had posted this same question in the MUSHclient forum. You can use Lua in Cmud too and using Lua tables makes things a little easier. Plus you only need one trigger really.

For example:

Newbie Joined: 12 Feb 2009 Posts: 6

Problem solved! And how minor the problem was in the end.
semicolons no longer separate commands without a carriage return at the end of them. I rewrote the whole thing a number of different times just to find out that west;get all;east wasn't firing
west
get all
east

because in the trigger it needed to be
west;
get all;
east.

I feel stupid. Thanks for all your help everyone.

Posted: Mon Feb 16, 2009 5:59 am

Actually, if you have the carriage return, you don't need the semicolon - the idea of the semicolon is that it's supposed to let you separate commands without using a semicolon. I don't see this problem with a simple test:

#trig {test} {lol;hax;pwn}
#say test

So something else is going on.

Newbie Joined: 12 Feb 2009 Posts: 6

This is true, while it corrected my trigger problem I did notice that other triggers programmed into the client function just fine with semi colons in place of carriage returns.
Oh well.