Zugg Software :: View topic

Wizard Joined: 26 Mar 2008 Posts: 1547

If I create one package for all of the general stuff that is the same between characters, the values of the variables still need to be different. If I put something in one package, and then put its reference variables in another (the character's package) will I be able reference my variables?

Posted: Wed May 28, 2008 3:19 am

Yep, as long as they're in a global module. But if you don't care about the right values being stored across sessions, and only during the current session, it might be easier just to turn off the shared option for your package. That'll load a separate instance of the package for each session, allowing each session to have its own value for the variables.

Wizard Joined: 26 Mar 2008 Posts: 1547

Well, the reason I wanted a global package was for some of the variables to be global. Namely, the ones that have values that all of the characters would use regardless, such as attack_type, etc... as I add to those I want it to affect all of my sessions. Hence the reason for a global package. But, as I did that, I realized that I wanted plenty of the other variables to remain localized, even if the triggers and such that used them could be globalized. So, if I kept them in the character's package, but the triggers that used them were in the global one, I'd be able to turn this off for individual variables? Is there a way to do that from the command output so I can include it with my copy and paste?

Posted: Wed May 28, 2008 11:25 am

Wizard Joined: 26 Mar 2008 Posts: 1547

The sharing values across packages.

Could I, for instance, say:

Variable_A in Package_1 is not shared
Variable_B in Package_1 IS shared

Variable_C in Package_2 IS shared

And would they all be accessible by triggers in both packages?

Wizard Joined: 22 Mar 2007 Posts: 2320

You're confusing yourself, Chamenas. The answer to your basic question is Yes, if you have variables in your session package, your addon packages can use them. So put the global variables in the addon package, and the session-specific variables in the session package.

Wizard Joined: 26 Mar 2008 Posts: 1547

Yeah, I think that's the route I want to go. Razz

I forget where the reference was for directing triggers and variables to go in one package or another via command line, anyone have a link?

Posted: Wed May 28, 2008 4:57 pm

#module. Anything in a global module is, well, global. Anything in a local module is visible only to other stuff in that package.

Wizard Joined: 22 Mar 2007 Posts: 2320

And since I know you like to specify a class when creating triggers on the command line, the format for specifying the module name is: //module/class