* fordfugue.tar.gz is a gzipped tarball of these scripts, they're more readable when apache isn't rendering trailing \s as a joined line.

All global settings (anything that might be shared between more than one character) should
go in the root tiny/ directory.  Character specific settings should be in a sub-directory,
preferably named after the character.  Hence I "cd ~/tiny/ford/;tf" to start playing Ford.
Ford's .tfrc file, with password info and so forth, goes there.  It loads the global trigger
and alias files, e.g.

/load ../triggers-g.tf
/load ../vars-g.tf
/load ../alias-g.tf
/load ../comm.tf

Then loads his guild object settings,

/load ../guild_gentech.tf

Then loads anything specific for Ford, the character, which is sitting in the ford/ directory,

/load aliases.tf
/load triggers.tf

And so on.  Clan, syndicate, equipment specific (e.g. nex), or what have you go in the tiny/ root directory to be shared between characters, as needed.  Since almost everything is character agnostic, about the only things that go in my character's directory is the .tfrc and some hiliting triggers to ansify, for instance, scavenger hunt items, or bolding my character's name, or more project specific TF scripts.  Ford for instance has a TF scripts for rebuilding the gentech.flagrancy.net website when the helpfiles are updated, Fjord has his maintenance scripts for building the 3k.flagrancy.net armor database, and so on. 

There's also a highmortal toggle, that redefines fantasy aliases ("towforest","toeforest","toroad", etc.) depending on what the HighMortal variable is set to.  Hence, in paths-g.tf

/if (HighMortal == 1) \
    /load ../highmortal.tf%;\
/else \
    /load ../mortal.tf%;\
/endif

mortal.tf macros from wayhaven, highmortal uses "portal road".  This makes it easy to switch back and forth as needed, without having to rewrite every alias you have to shit in fantasy.

comm.tf will write a communications log into the tiny/ directory, called Comm.  Just tail -100f Comm to follow your chats.  I used to have a separate Comm log in each character's directory.  This got annoying having two characters active at once on 3K/3S, so I moved it up a directory and now unify chats into one log file.  This might be confusing to you if you can't tell who is talking to which character on which mud, you could always add something to the chatlog timestamp to indicate which world the chat is coming from.