Zugg Software :: View topic

Newbie Joined: 25 Sep 2007 Posts: 2

So I'm very new to using cMUD and it's scripting language. Currently I'm trying to make a trigger that will catch chatter from a MUSH channel and dump it to a new sub-window under the specific connection. While I've managed to do that, It creates a second window above the main connection window. What I'm curious to know is if there is a way to cause the window that spawns to be tabbed in relation to the specific session's main window, instead of a separate one.

EDIT: Aww, bloody heck. Now I'm just wondering if I'm going about this the right way at all... Okay. So here's the situation, then.

I play on multiple characters, on multiple MUSHes. All of which have pretty heavy channel chatter. What I'm looking to do is somehow weed the channel chatter for each channel out of the main MUSH session for that character, and put each channel in a tabbed sub-window within that Session's Main tab. From what I read, it looked like using a trigger with #MAKEWINDOW would be the best bet, using code something like:

Posted: Tue Sep 25, 2007 1:03 pm

#cap will create the window if it doesn't exist. You don't need to make it yourself.

I'm really not sure why the window isn't persisting across sessions, though. Once you've got the window where you want it, use the #save command to force the layout to be saved. CMUD should be doing this in the background. If that doesn't work, try opening the Package Editor and click New... Window to create the window. Just name it Chatter, put it where you want it and use #save again.

If neither of these works, it sounds like there's a bug here. Are you using 1.34 or 2.03?

Newbie Joined: 25 Sep 2007 Posts: 2

Ah. Okay. I've gotten things mostly to where I want them now thanks to that advice. Very Happy

One last question. I have multiple characters connecting to the same MUSH. Problem is that if two of them are on the same channel; say "Bob" and "Bill" are on "Public", then I'll start seeing two instances of each message pop up in the "Public" window under Bob's connection. One from Bob and one from Bill. I would assume this is because both instances of the trigger are looking for the Public window, and since it's already active under Bob's session, it just uses that instead of making a new one under Bill's.

The trigger itself is: #TRIGGER *<Public>* {#CAP Public;#GAG}

Is there a way to force it so that it would make a "Public" window for each Bob and Bill, or is that outside the scope of the program's capabilities? o.o

EDIT: Sorry, Ver. 1.34. Though I'm not adverse to upgrading to the 2.03 Beta if it would provide the functionality I'm looking for and 1.34 wouldn't.