Zugg Software :: View topic

Posted: Tue Mar 20, 2012 11:31 pm

Looking for some clarification on multiplaying ...

First - can anyone foresee any problems multiplaying in a single session? I've only been learning CMUD for a few days, so ...

From what I've learned, it seems like most people are multiplaying on the same mud by creating a shared map package and placing it in a single session, then opening up that single session twice.
I tried this and found it to be a little clunky, so I tried the following instead:

First, I created a single session for my mud.
In that session I renamed my main window to session_mainchar.
Then I created a new map and opened it.
Next I created a second window and named it session_secondchar. Clicking on that window I then get an option to connect from the file menu.
I mapped a few rooms. Then I placed both characters in specific rooms and from each session I entered the following commands:
#LOC "window_name" "vnum" // where window_name was either session_mainchar or session_secondchar and vnum was the room they were in
#TRACK "window_name" "color" // where window_name was either session_mainchar or session_secondchar and color was blue or red

Both showed up on the map and tracking works perfectly.

I've noticed the following complications/issues/problems so far:

If one character disconnects, I get the nasty popup. If I disconnect my secondary character on purpose - I'd rather not see it. Is there a way to suppress this message? Can you do this on per window basis? With a specific command?

The autologin junk is session based, not window based. The autologin fields define the session variables #CHAR and #CW. Since I've got multiple characters in the same session, I don't see a way to utilize these fields and thus the corresponding commands & variables.
Will this be a problem? Or can I make do just fine by defining those variables in the corresponding windows? Do you foresee any problems here?

The find location on mud and look (reload room info) commands from the map actions menu only work with the default window, regardless of what window is selected. Is there a way to force them to interact with a different window instead?

Posted: Tue Mar 20, 2012 11:56 pm

It is my understanding that each character should have a separate session.
And then an additional master session is used to house the map and layout of all the docked sessions together, but it has no connection of its own.

The reason for this is to make it easier to keep the variables relative to each character separate, via scoping.

As for suppressing the popup, for each individual character session, select preferences, then find and uncheck the option for automatic reconnect.

Posted: Wed Mar 21, 2012 2:05 am

I've found that logging into different muds within one cmud instance causes problems. It is probably doable, but the amount of care required is not cost effective. Best just to use a different cmud instance per mud.

Posted: Wed Mar 21, 2012 2:07 am

Posted: Wed Mar 21, 2012 2:10 am

Then, of course, you have to use the same cmud instance. I do think you will have problems with execution, though it's doable. You must remember there is only one package being used, not two. Unless you do something to explicitly change that. As I said, work is certainly required.

Posted: Wed Mar 21, 2012 3:59 am

The problem I'm seeing with this method now is that it appears that there is no way to share settings between windows. I.E. I can't create a class which contains a script and then place that script as a child of multiple windows.

However, I believe that you can create a package which contains settings and load that package into multiple sessions.

Posted: Wed Mar 21, 2012 4:36 am

Wizard Joined: 22 Mar 2007 Posts: 2320

Not the way you have it set up. As you have it set up, if you disable a class, it will be disabled for all sessions.