Zugg Software :: Search

Well, I finally cheated and sorted out the specific situation that was causing me grief. It now works fine, but the problem is still there.

edb6377

This all started from the problems you mention ...

mo24 - I experience that too. My solution to this problem has been to simplify the way I do things (cut down debugging) and it now seems to be working.

The glitches you mention have not all disapp ...

Triggers mis-firing is not my problem. That can easily be resolved.

What I'm referring to is lines from the MUD not being processed sequentially, which is what I need for some of my triggers.

I' ...

OK, that's different from what I thought. Might have to go through my triggers and re-organize the command order.

Did you have a problem with different triggers acting on the same line or with trig ...

Triggers fire in the order you put them into - I'm pretty sure of this as I have interdependent triggers.

My problem is that *sometimes* (not always) zMUD will start parsing a new line while it's ...

Is it possible to enforce sequential parsing of the MUD output on zMUD?

I seem to be getting a issues lately where zMUD seems to be attempting to parse lines in parallel (This is especially prone t ...

OK. Thanks for the suggestion, had not thought of that.

Thanks!

The alias is called 'debug', and is meant to print a line of text and then gag it. The version of it that I gave above is pretty much it, but if you want the alias itself, it is:

#ALIAS debug {#VAR ...

I'm get a pop-up window saying

Infinite loop detected in command parsing:
#VAR line.c @{line.g} ; #say @{status}%time"
All variables are standard variables with values.

My problem is that:
- ...

I use gag a lot, and don't have any problems with it. It does not insert a blank line, it just removes the last line that you have in the window (as opposed to the last line received).

One thing I ...

Thanks for the note Vijilante!

I probably will convert database manipulations to the last format - half of them now explicitly use #ADDKEY, converted while trying to figure out how to solve the pro ...

OK, fixed it. Looks like the <> part is not required any more.

Seems to expand properly without them.

When upgrading from 7.05 to 7.21 I noticed a problem with most of my scripts - This was traced to a particular syntax not working any more.

As an example, say I want to parse money in the format:
...

The reason you cannot see a connection from zMUD using netstat is that zMUD is connecting to the proxy not to the host.

As Darker said, you won't have much luck with connecting to your MUD via an H ...

Not exactly what I was looking for, but it does give me something to work on. Thanks.

The text I'm speaking of is essentially generated by triggers (or by aliases/loops called from triggers), so th ...

Is there a way to insert text into the main MUD window (so that it is logged) without having it processed by triggers?

Thanks,

Ideally your MUD will have a mode where it sends all the tell in one line - This is the easy solution.

Otherwise you'll have to match the start of the tell and the end of the tell, and process all ...

Should work fine, the only problem is getting the info you require on the computer you want it without having to look for it.

What I'd recommend is using the "save as" feature to save to a network ...

Thanks, didn't know about that. It's worth looking into.

What are your slow walking triggers?

If you're slow walking then you must have some trigger that is confirming movement. If you delay this you should slow the walk.

----

As for the problem yo ...

What happens when you double-click on one of the icons in the zMUD "Characters" window?

Try achaea, for example, and see whether you get a connection.

If you do, then it's something with the set ...

Thanks, problem solved.

The quotes were being 'lost' when I was assigning the contents of one variable to another with
#VAR V_1 @{V_2}

Everything works fine now :)

Thanks!

I'm running into problems using list variables that contain quotes.

Debugging of these problems is made more difficult as I know of no way of checking exactly what the contents of a variable is. Is ...

The LoopLines condition only matches lines that follow the original trigger line.

A simple trigger with regex was the answer. Read davidnmilby's post, it worked really well.

You don't want to use #WAIT. Read the support section for the reasons.

What I think you want to do is to go through the list manually (depending on the MUD output), In this case you can't use #FORA ...