KildClient

nice, thanks

FYI: I spent a frustrating while realising that deleting a timer from within code called by that timer triggering was a bad idea.
The solution was to use distimer instead.

[this is a summary of a thread on the old nabble forum]

I want to syntax check my perl kildclient code. When I run 'perl x.pl' I get loads of $world errors; as its not defined. Any suggestions on a better approach? Shedding a bit of light on this, I can now now use strict and use warnings as well as compile code from the command line by declaring $window...

[Original came from the Nabble forum] I want to separate my perl into files (modules) without having to create a plugin. How do I instruct kildclient to honour 'use x;' statements? Normally this is via @PERL5LIB or @INC. I've tried setting these, but the use statements are not finding the x.pm files...

No sure if this is still true, but using an old MUD, the MUD caused Kildclient to turn off the echo of the text I typed and I was unable to turn it on in any satisfactory manner. The work around I used was edit ~/.kildclient/MUD_0.wrl or what ever your world file is called. Assure the following is s...

Thanks, I've looked further into what I actually need and realise that this isn't really needed. Internet delays give me the jitter I was looking for as it is.

Each MUD sysop seems to have a different opinion on allowed/fair use of triggers. I'm developing a system which has a more human appearance to anyone monitoring my input. The odd pause here and there and time to enter each line. My current weakness is my pauses are always multiples of seconds. I hop...