Zugg Software :: View topic

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

I have this vision of what I like zmud/cmud to look like when I multiplay, and it is glorious (to me). I used to have this glorious vision work for me when I mudded many years ago and it worked pretty well, when it worked. Anyway, here is a picture of a basic Idea of what I want to happen, perhaps you guys can figure out how to make this work for me. I use cmud 2.37 pro.

http://i97.photobucket.com/albums/l228/jimbabwe77/commwindow-1.jpg

Now, I made the Mumra character session first. Managed to use #MAKEW to get a window size/etc that I liked for 'Comms' up top. This layout is beautiful to me. Now, I log another session. It ends up being Tabbed and taking the full window. I drag it out of the tab, and down into the Mumra section, voila! It tabbed in perfectly! I try again hoping it isn't a fluke. Voila! Alysa tabbed in. I was ecstatic for a minute. I logged the two extra characters out. Tried to relog one of them again. Bam. Error! Here is the appropriate error stuff:

Posted: Tue Aug 21, 2012 1:09 pm

Are you actually creating a different session for each character (correct way)
Or trying to kludge a child window into holding char data?
There are several threads already on how to maintain a mutiplay layout.

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

Each character is their own session, created the normal way. having their own packages, etc. The child window I want is strictly for information purposes, but that information can come from any open session. As for other threads on this the ones I checked seemed to involve me making up a Multiple character layout, and then selecting it with that icon. That would involve me not using whichever characters I want at any time I want and restrict me from swapping easy.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

You can write a script (or perhaps find one) to handle character selection. Once you know who you are going to log on with, you can then load their package.

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

I don't follow Matt. Do you mean like a session with no name or character associated with it? I think I see something like this mentioned by Zugg in a post.. since you can use like #SESSION 216.251.47.10 4000 to create a session to a mud. Then use an alias or triggers to rename said window.. and load packages? If that's what you mean, I don't see the point.. since I'd essentially be doing the same thing as just using #SESSION charactername, no?

At the moment, I have an alias: as follows.

#ALIAS log {#if %ismember(%1, %names) {} {#SESSION %1}}

Fairly straightforward, and since I named all of my windows as the characters name, it allows for fast logging right from the command line.
I also have aliases to disconnect by name, close window by name, etc. Sometimes calling multiple sessions up at once.. for say a spellbot crew.