Zugg Software :: View topic - Variables being created/modified in separate packages + disappearing scripts

Apprentice Joined: 17 May 2005 Posts: 108

So I have a couple of problems I was hoping someone could help me sort out.
The first, as is likely unclear by the subject line, involves running very similar scripts on two characters (packages) simultaneously, and running into problems with the alias/trigger in one packages modifying the variables of the other package.

I set up a simple script to recast failed spells, with an alias, "ca," which initially had the value of "cast %-1;#var lastspell {%-1} {} {recast}." This worked well for quite some time, as I generally run one spellcaster and one melee class at any given time. Then I decided to run two casters at once, and found that one character's "lastspell" value would always override the other's. So, while one character cast, say, "fireball," and the other cast "lightning bolt," both of them would have "lightning bolt" as the value of "lastspell."

I tried what I figured would be the simplest solution--that of modifying the script to append the individual characters' names to the variable and all instances where the variable was called, and, as further assurance, I placed those variables in a new folder also named with the character's name. Thus, the value of alias "CA" became: "cast %-1; #var lastspellbob} {%-1} {} {recastbob}."

That sorted, I made sure it worked individually, and then tested with two casters grouped together. I had exactly the same problem. Now, @lastspellbob and @lastspellbill both contained Bob's last spell, despite Bob's alias only setting @lastspellbob and only in class recastbob. Bill's variable, lastspellbill, in class recastbill, would somehow have picked up Bob's spell.

I considered using local variables, but from the help file it seems those are a one-shot deal, and there are occasions in which I might need to call the same value multiple times.

Additionally, I wondered if anyone could tell me why my triggers, aliases, and even single lines within script blocks occasionally disappear. This seems to be a new trend, which especially affects newly created triggers/etc., but has occasionally occurred with long-standing bits of code.

If you made it this far, thanks for reading!

-Llohr

Sorcerer Joined: 13 Jan 2006 Posts: 715

Its funny... I logged into the forum to post the exact same issue.

I run an automatic practice script on a MUD that allows 3 characters online at once. If I have more than one session opened I get the issue described by the OP in which the sessions use the variables from each others' packages. This really messes things up since I may have each character practicing different things. I've made sure the package includes for each of the 3 character session packages is not including the other 2 character packages. Yet this still happens. CMUD 3.34. This only seems to happen for me when using #THREAD however, not all the time... so it may be a different issue despite sounding exactly the same.

Wizard Joined: 22 Mar 2007 Posts: 2320

Lines disappearing mysteriously in your scripts sounds like corruption of your package. This can also lead to many other mysterious problems. Try the export/import trick.

It is possible that problems with variables could be caused by the same thing, so fix that first. It does not sound like Ralgith has that problem, however. Can you explain how your session is set up? Does each session have a separate session package? Are the variables for each session in that session's package? Are the the triggers using those variables duplicated in each session, or are they in a separate shared package? Have you double checked that there aren't accidentally duplicated variables somewhere that all the sessions can see?

I suppose it is concievable that a thread might lose track of which session it is supposed to work with, but we will need more detail to track this down.

Sorcerer Joined: 13 Jan 2006 Posts: 715

Each character has its own unique session. The script is an exact duplicate between sessions except the contents of the variables controlling which spells & skills they're practicing & the ones that track their mana.

Here is the script XML for one character.

Sorcerer Joined: 13 Jan 2006 Posts: 715

I would like to state that I did work around this bug by editing the RunPrac alias to use the full variable paths just now as a test, however that should not be needed and really annoys me.

By full variable paths I mean:
@//Jenia/Automatic_Practice/VarName

Very annoying! >_<
But at least it lets me run the script while another character does something else.

Sorcerer Joined: 13 Jan 2006 Posts: 715

Then again... maybe not. I just had another time it went haywire. So, I guess that wasn't a valid work-around after all. Just didn't do it when I had another character on that didn't have the script is all.

So... any other ideas? >_<

Posted: Sun Mar 04, 2012 7:10 pm

You have seperate sessions with duplicate variables..
Make a seperate package that both will use just for setting the various variables

Apprentice Joined: 17 May 2005 Posts: 108

Okay, as far as I can tell, the only bit directed at me was a suggestion that I use the export/import trick. Beyond the obvious, what steps are involved in this trick? Should I reinstall CMud? Create a new session? Just delete all of my settings after exporting and prior to importing?

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

Easiest way is to export, remove the tab you just exported, find and delete the .pkg file that tab was associated with, then create a new package and import what you just exported. Since you cannot be sure exactly which package is broken, it's best to do them all.

For particularly large or complex packages, I've found it useful to only import small, manageable sections that I can then look at and make sure stuff was imported correctly before moving on to the next bit (since this will no doubt break some of your scripts while you're in the middle of reviewing them, you may wish to disable them).

Apprentice Joined: 17 May 2005 Posts: 108

So, I exported the package, then, due to some concern about breaking things, chose to simply create a new session rather than deleting the existing one, and imported the xml file into the new session.

I got what appears to be all of my triggers back. No variables, no aliases, no classes, just all of my triggers sitting in the root folder. Did I miss something?