Zugg Software :: View topic

Beginner Joined: 25 Oct 2006 Posts: 14

I have 2 characters on one mud. How do i exactally create a seperate set of macros, triggers, etc for the second character?

Posted: Tue Dec 05, 2006 10:41 pm

You create a separate session for that character. Just click "All Muds" at the bottom of the sessions window, find your MUD on there (there's a filter box) and click "New Session". Name it something nice and you're away :)

Beginner Joined: 25 Oct 2006 Posts: 14

Isnt there a way to do it with packages etc?? I dont want to have to use a differant seesion...i was under the impression i could just change folders of settings or something.

Posted: Tue Dec 05, 2006 11:01 pm

on the subject of multplaying, is anyone still having huge issues when they try to log on a second char? my settings do all sorts of odd things.. i loose all the buttons on my primary char window, as well as a number of other unpredictable things. they come back up on restart, but cmud has to be shutdown for it to recover.

Posted: Tue Dec 05, 2006 11:41 pm

Is this a question about multiplaying, Renegade, or about simply having two separate characters on the same mud? I assumed you meant using two characters independently because most muds don't allow multiplaying - if you are using the two characters independently, creating a second session is much easier, since it'll automatically have its own .pkgs and log you in separately if you use auto-login. If you wanted to use the same settings for two different characters, I could understand your concern (and it is possible to have two characters using the same settings, you just have to edit the session and navigate to the .pkg you want to use).

If this is a question about multiplaying, it gets a bit more difficult, but yes it's possible. You'll want to open the session you want to use for your two characters, open the Package Editor and create a new window. Position it however you like using the options available, then change it to use its own network connection. Type in the address and port of your mud and presto, it has its own connection. Any settings you create under each window will be specific to that window.

If you want to create settings that'll apply to both windows, create a new module and put them in there - they'll be visible to both windows by default.

Posted: Tue Dec 05, 2006 11:54 pm

is it better to use the same session for the 2 chars? or use 2 sessions.. ive always used 2 sessions on zmud, but cmud hates it with a passion at the moment.. wondering if this could be a workaround to that problem.

Posted: Wed Dec 06, 2006 12:06 am

That's the way I'd do it - I'd forgotten that you even could open two sessions at once. It just seems better to me to do it this way - it stops you having to play with module publication settings and the like to get things to work.

It's quite hard to draw a comparison with zMUD since it blurred the line between sessions and windows and didn't have modules or packages. Opening two sessions in zMUD is the same as opening two windows in CMUD to my mind - the settings in the window being the settings that would've been in the .mud file.

Beginner Joined: 25 Oct 2006 Posts: 14

QUOTE " is it better to use the same session for the 2 chars? or use 2 sessions.. ive always used 2 sessions on zmud, but cmud hates it with a passion at the moment.. "

That is exactally what I am finding...2 sessions just trashed CMud...

Posted: Wed Dec 06, 2006 3:24 am

There's a known bug with packages becoming confused between sessions if you open more than one at once... or something to that effect. I think it's fixed in the next version.

Beginner Joined: 25 Oct 2006 Posts: 14

Theres more than that.,.. I created a new package and toiled at recreating my triggers etc.. Some just stopped working...my Ailias @target=%1 for one just quit working after the update....the program crashes and now everything is gone...even the package I had saved from other sessions. This is nuts.... I dont mind beta stuff....but i do think the 2 yr update should start from the public release...not during this. ....but thats another gripe :)

Wizard Joined: 14 Aug 2004 Posts: 1269

Posted: Wed Dec 06, 2006 6:01 pm

Posted: Wed Dec 06, 2006 6:06 pm

thats cool zugg, i use my 2nd char rarely, but it was something i wanted to get straight.. that way of doing it is fine. our mud is hugely multiplay (2 chars max at a time) and alot of people do.. so i was more trying to get the procedure straight in my head when they all go buy cmud and then pounce me expecting to know (jeez the pressure we put ourselves under).

Posted: Wed Dec 06, 2006 6:21 pm

The next version will also move the Connection stuff at the bottom of the Session pulldown menu into it's own "Connections" sub-menu that will be at the top just under the New Session option. This should make it a bit easier to select connections without having them all at the bottom, which can be a pain if you have a lot of session icons making this menu long.

Posted: Wed Dec 06, 2006 7:35 pm

doing things that way is far far easier, but i have a problem.

once ive disco'd the 2nd char, and clicked offline to go back to my other main window, i end up with most of my scripts that use variables to display info failing to work. for instance.

status window fails to display the contents of variables, it doesnt show anything were that info should appear.

there are other things that fail, but its alot of different stuff and i cant boil it down to specific elements.

I realise this is probably covered in the multi session bug that corrupts settings, so its more to confirm it.

edit: forgot to add.

once i go into settings, disable the extra window and restart cmud, all is well again, so whatever its doing, its not perminent to the settings files.

Posted: Wed Dec 06, 2006 11:23 pm

I'd actually suggest that you just wait for the next version. I've been working on multiple sessions and multiple characters all day today and have found tons of problems. And some of these problems can cause all of your settings in a package to get removed. There are so many issues that cause so many different bugs, that reporting them at this point probably won't help me. I've had to make some pretty significant code changes in 1.20 already.

I'll try to see if I can get 1.20 out tonight so that you can play with a version that works better.

Posted: Wed Dec 06, 2006 11:31 pm

No 1.20, Zugg?

Posted: Wed Dec 06, 2006 11:31 pm

Typo...edited my post just as you posted :)

Posted: Wed Dec 06, 2006 11:52 pm

ok no problems :) will await as suggested.

Posted: Thu Dec 07, 2006 5:24 am

OK, give 1.20 a try. I hope it works better.

But please create new topics for any 1.20 bugs. Let's let this particular thread die.