Zugg Software :: Search

I'm not sure if this is a factor, but have you tried changing this code to match the documentation? Like this:
#alarm {+0.5} {#T- SomeClass}
I've never seen the problem you des ...

There is a "Trigger on Commands" option in the Preferences to control whether a command fires a trigger.

Ah my bad, didn't remember this one. :)

I replied to your error report too, but thought I'd also post it here:

I notice that you are using a computer in Finnish. It might be a problem with your floating point format in Windows. Does Fi ...

Can make the package editor crash with following procedure:

Make an alias and paste the following into it:

#alarm +10 {#if (1) {
}
}

Then move your cursor in fro ...

I'm not sure if this is a factor, but have you tried changing this code to match the documentation? Like this:
#alarm {+0.5} {#T- SomeClass}
I've never seen the problem you des ...

Don't use a multiline trigger, use a trigger. They're better than multiline in every way possible :P

Though for this particular problem, it might be better to use a single trigger on the Obvious E ...

It is a desired feature because cmud has to be able to check your own mud commands to see if they fire triggers. So, cmud cannot ignore your commands to the mud.

How do you make a trigger that fir ...

Sometimes CMUD stops handling floating point values and produces an error every time you try to use one with a command. When this happens I can even test it from the command line by typing "#say 0.5" ...

I have talked with another mud client coder about this problem and now understand it a bit better. Seems that to completely fix this problem CMUD would have to use a different kind of regexp parser, a ...

Cmud has lots of wonderful features, maybe even too much, since there are still many stability issues that haven't been resolved. Cmud would easily be the best mud client ever made by a mile if it was ...

That doesn't work so great either, because I can't scroll back the main window and see when each command was sent, which is needed if I want to debug some trigger's behaviour.

I guess I could log t ...

I don't really understand what you mean... Of course line two is appended to line one if there is no CRLF. And those graphical problems happen all the time, that is not a problem, can make smart trigg ...

But shouldn't triggers fire on text received from mud, not on text that is shown on screen? Could handle those two things totally separately.

I have a trigger like:

#trigger {^Your group consists of:} {#say blahblah}

But when that line is received from mud sometimes my own commands can come in the middle, so the output looks like:

...

Actually now that I tested it some more, it has nothing to do with CMUD scripts. It steals focus even if all triggers and tick timer are off. It happens when other program commands CMUD with dde. When ...

I don't have any Stay on Top turned on.

Very often when changing the window away from CMUD it steals the focus back after a sec or two. It can happen after ALT-tab or just clicking a different window. So for example if I click on Wordpad an ...

Simply enough, if you have a trigger:

#TRIGGER {%x tells you 'enter (%x)'} {#alarm +1 {enter %1}}

it doesn't work. It doesn't expand the %1 before making the alarm. Using local variables works t ...

Yea this is not a big problem for me, since I'm normally restarting CMUD anyway. I just wanted to inform you of such behaviour. :) I mean if there is a bug it can always cause other problems too.

Well the alarms get removed automatically since I use temporary alarms, like: #alarm +4 {blah blah}. So Package Editor only shows current "pending" alarms, 0-3 at a time.

When CMUD has been on for about 12h it starts having periodic lags, and the lag keeps becoming longer and longer. First the lag is under one second but after a day it's like 3 seconds. The lag (or fre ...

Yea I noticed this too, it worked on 2.29 atleast. Same thing happens with "page up/down" buttons. Also CTRL-Z doesn't work on the child windows.

It seems that the "save scrollback" feature only works on the first time when starting logging.

So if I connect to mud, type "#log logfile.txt", then just "#log" to turn it off, it will create the ...

OK seems that adding with #tab-command works. But when I add with CTRL-W the word goes under "default settings" in tab completations and disappears after a restart. #tab-command adds it under my curre ...

I have a problem with the tab completations. I can add and use them just fine, but after I close and restart cmud all the completations have disappeared. Other settings are saved OK.

Any ideas?