Zugg Software :: View topic

SubAdmin Joined: 18 Nov 2001 Posts: 5182

A few small additions and minor changes should do it.

Apprentice Joined: 04 Mar 2007 Posts: 103

Magician Joined: 28 Jan 2007 Posts: 430

You need the } after ) and before #delitem, imo.

Prog

Apprentice Joined: 04 Mar 2007 Posts: 103

I am just trying to concat the at maximum two lines of room exits and put them into one string, which i will then manipulate into an array or exit commands. Golly this is harder than I would have expected. It seems like sometimes zmud sort of bugs out and starts giving me responses that i wouldn't expect, even though its probably just bad syntax on my part. I thought i was getting close and i have manually typing the #show @RoomExits on the command line after i enter a room and my favorite new response to that comand is "=" .

One other thing is there a simple way to make the second conditional trigger not fire if the first exit line ends in a period. so that i don't get a stinking ogre as a room exit name.
Thanks for any help

Here are possible MUD outputs:

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

Before you go any further, does your mud have a word-wrapping function? If it does, simply increasing this to as high as you can go will fix your problem very easily.

Apprentice Joined: 04 Mar 2007 Posts: 103

yes it does have that ability but i am playing because i enjoy programming. I am trying to write a mapper bot that will map my whole mud and i am trying to do it in as few lines of code as possible, just for the fun of programming. My friends say that i am too intense and i need a hobby so i decided to mud, kills two birds with one stone. I have used the wrap function to play with this problem. but its more the concept that i am trying to master.

Thanks again for any input.

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

In that case, don't use a multi-state trigger. Multi-state triggers are only generally helpful if the lines will always appear rather than only sometimes.

#TRIGGER "CaptureExits" {-- There [is|are] %w obvious [exit|exits]:(*)} {#VAR RoomExits= %1}

2)insert (before or after, it really doesn't matter), an #IF check employing the %ends() function to test for the inclusion of a period. If it exists, the exits are all contained on one line. If it doesn't exist, you need to enable the trigger (your #CONDITION above) that will capture the extra line. This other trigger will also have to turn itself off.

Apprentice Joined: 04 Mar 2007 Posts: 103