Zugg Software :: View topic

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

I have started breaking my settings files down into packages for easier
distribution and organization just recently.

One thing I find rather annoying as I have upwards of 60 different characters and sessions in my cmud,
is this:
I make a new package, add whatever settings to it, get it all set up properly. save it, attach it to a session.
Then I log on a new session, and it automatically uses that package as well. Generally this ends up with me
having duplicate of a loginscript, triggers firing, etc. Is there a way to set a new package to NOT be automatically
used by every session that logs on?
It would be much easier for me to use that behavior versus logging up each session individually and unchecking
the package in each sessions window.

Also, invariably when I have to load up each session to uncheck, my cmud will gobble 50% CPU and freeze up,
requiring me to force quite it via task manager due to the loading of so many files it seems.

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

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

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

So, no solution to make packages not work across all chars loaded, other than loading each one individual and unchecking the package?

Because the package isn't listed in the 'default packages' for new characters.
Nor is it listed in the 'Session Properties' Packages.

Perhaps I am not using the correct terminlogy by saying packages. I will try to explain in detail what is occurring.

I have 2 'brewer' characters. Each with empty sessions, and no packages loaded other than the default three included with Cmud 2.37.
English Keypad
English Directions
Clickable URLs

I make a new package. I write up fantastic brewing, and scribing settings in this package which I will refer to as 'ALLBREWING' here. Adding in an OnConnect Event in case of disconnects so the bots can reconnect and continue brewing/scribing. I make sure this package is checked for both of my brewers in the 'Advanced' window in the settings. I notice this is now called a Module, as it has no window I guess. Either way. the bots brew and scribe away merrily, perfectly.

I then load another session. It has it's own OnConnect Event for instance. Now, both OnConnect Event's fire off, giving me a load of spam that I don't need for instance. Open Settings, Advanced, Bam. the ALLBREWING is checked for the new session I loaded. That's just a small example. I am forced to uncheck it in the 'Advanced' "List of Packages enabled for this module' to stop this crosstalk and such. I have over 60 different sessions as I said. So now I have to load every session, and uncheck this option because I might at sometime use other characters while my brewers are loaded and thus suffer multiple events, etc.

What I would like is for when I open a package with a session via New Package, for instance... it is only loaded for that session. Not every session that loads while that session is loaded.

Hopefully that is a little more clear. :\

Posted: Wed Sep 19, 2012 6:03 am

I can confirm this..

1) Create a new MageChar session and add a new Mage package, close
2) Create a new ClericChar session and add a Cleric package, close
3) Open MageChar then open ClericChar to make a supersession, the Cleric package will have been activated on the MageChar window and vice versa.

This isn't a big issue for 2 sessions/characters, but with more it's a problem. I don't see a simple way to get around this without code duplication ie. copy the Mage module to each mage's session.

I would just use multiple windows under a single Mage package/session, but this screws up the mapper.

Wizard Joined: 22 Mar 2007 Posts: 2320

Yes, the behavior you are seeing is normal. By default when you load a session, any other modules that have already been loaded are enabled, unless they
have been specifically disabled. This is what people would want most frequently, so this is the default behavior. There is no way currently to alter this behavior.
To disable the packages you would need to manually unmark the checkboxes, as you have been doing. Once you have done this, it will remember the setting
for the future, but I'm afraid there is no way to avoid doing this the one time.

Posted: Wed Sep 19, 2012 2:27 pm

this can be done by script as well, as i had to figure out when my capturing packages enabled themselves for the windows they capture to, resulting in infinite loops as it recaptures itself indefinately, and ididnt want all my end users having to constantly go in and uncheck boxes. (automatic windows update closing CMUD seems to reset this boxes to checked)

Posted: Wed Sep 19, 2012 8:00 pm

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

Where exactly am I putting that Shalimar?

Posted: Thu Sep 20, 2012 12:23 am

you put that in the XML tab of a new function and a new event settings