'Events' vs. Triggers or Macros, Is it possible? Options

[rowanflowers]

Since switching from DSL to broadband, I seem unable to idle for 15m without completely freezing on a MUSH. As a wizard, builder and long poser (sorry) this hasn't been the most convenient "new feature" of broadband.

We've performed a few tests and having ambiance code active in the space where I'm standing seems to alleviate this issue (though, very spammily, if I may invent an adverb). An associate of mine uses 'events' in SimpleMu to send a @pemit %R (line return) to get to the same solution and in a much easier-on-the-brain fashion. I have played around with macros and triggers, but neither seem to fit the solution I'm after.

Anyone have any hints on how they might be used or how I might be able to go about it?

Thanks muchly

[Day]

I, too, had this problem. I managed to write a macro for it, which I set to be triggered in my connect commands. Here:

##task 600 IDLE

This sends the IDLE command every, what, 600 seconds, so... ten minutes? If you're not playing on the most recent PennMUSH build, then the IDLE command prolly isn't there and you'll have to make do with something else. Before IDLE was invented I used th time() and it was kind of convenient for things to be time-stamped every ten minutes.


->Day<-