splitting up chars

[silvea]

atm I got 2 characters, a shaman and an invo, but the triggers for both are messing up each other. Is there a way to make the triggers in a group?

like:
group sojourn (always on)
group shaman (when activated)
group invo (when activated)
group backup (always off)

This way I got the triggers for the char I'm playing at that time.....

[Gindipple]

Once you got a good core set of triggers that each will need, do a save as under settings for each char.
Should solve your dilema.

[Vazzgo]

i think what gindipple said is the best solution, but if you still want to keep all those settings on the same file, you could have a button or trigger at connect to ask you wich char you gonna use.. like: "Char using today?: 1) Voker 2) Shaman" then capture into a variable and wich a #case turn on your selection and off the rest.

[Nokie]

What I do in Tinyfugue is to use a hierarchy of files, each with their own scope.

For example, I have a file, triggers.tf, which contains all 'global' triggers. I also have a file called rogue.tf, which contains rogue-specific triggers (like standing up from a failed trip, etc). Lastly I have a file called soj.nokie.tf which contains things that are specifically tailored to Nokie.

So I load triggers.tf at loadtime globally, and when I load soj.nokie.tf (when connecting as Nokie), that file in turn loads rogue.tf.

[Gindipple]

Vazzgo,
Prior to doing it the way I stated I used to use this method.
#if (%char == Gindipple) {do Gindipple stuff} {do non-Gindipple stuff}
The variable %char automatically does what you mention.
That is of course if you atleast have a seperate login for each char, which you should else you're typing manually the pword and login stuff for each char from one setup.