This document covers the changes from normal eggdrop to my eggdrop:

Commands changed:
1. The chattr command, this is probably the one you'll notice most:
 .chattr <nick> +o/m/n, which normally would give the user +o/m/n on one chan, 
 in my script instead gives them "global" masters. Which means that they are
 now a op/master/owner on all your channels. Assuming you do not want this, 
 the correct format for a channel op/master/owner is:
 .chattr <nick> #chan +o/m/n
2. +ban <nick> <chan> <host> <Time> <reason>
 This replaces the normal banning systems traditional .-ban <host> command.
 The reasons I think this system is better is because: 
  A. It bans not just 1, but all hostmasks.
  B. It bans using the hostmasks YOU give, not the hostmask of just that user.
  C. Bans can expire, or optionally not expire.
 Nick is the users nick, mainly for identification, chan is of course the 
 channel the user is on.  Chan can also be "global" to specify the user
 should be banned on all channels. <host> is of course the hostmask of a 
 user. Hostmasks can be added thru .+ban or thru .+host. <Time> is the time
 until the ban expires, and <reason> is the traditional reason. 
 The system works like:
  .+ban lamer #lame *!*@*lame.com 3d2h no reason.
 See: The .+ban help page.
3. .-ban <nick> <chan> 
  No explanation needed. Chan can be global.
4. .bans <chan> all
  Lists bans for <chan>, or optionally, the list of global bans for <chan>
5. .bans all
  Lists all perm bans for <chan>
6. .match <host> 
    Matches all people with the hostmask of <host>
    For example, .match netcom, would match netcom.com, netcom.ca, etc...
   .match <chan> <flag>
    Lists all people with <flag> on <chan> if it is 
    a emulti flag. If it is a flag other than +o, +m, or +n, it ignores chan
    and lists all people with <flag>
   .match <flag> - Matches all people with <flag>
    Same as <chan> <flag>, except all users are listed.
   .match <nick>
    Lists a little info about <nick>..

Commands added:

1. autoop <nick>
 This command toggles autoop for <nick>. Of course, if channel autoop is off
 (See chset), then the user is not autooped. The user will be autooped on any
 channel with autoop on that he has ops in.
2. addops <channel>
 This command adds all current ops on <channel>, as emulti +o users on 
 <channel>. As a bonus, if they are a new user, or do not have a password 
 set, it sets a random 6 digit password and tells them their new password.
 This is more secure than the traditional /msg bot pass <pass>.
3. wall <channel> <msg>
 This sends a traditional wallop to the ops in <channel>.
4. act <target> <msg>
 This sends a action to <target> of <msg>
5. +chan <chan> <mode> <channel to mirror>
 Adds <chan> with the channel mode of <mode>, mode is any normal channel 
 mode (chan as +nst). <channel to mirror> is a new feature. It allows you 
 to have <channel to mirror> and <chan> have the same user list. 
6. .-chan <chan>
 This deletes <chan> from the emulti and channel list. However, if the chan
 is in your bots config, you will have to manually remove it there.
7. .chset <chan> +-autoop +-joinonstart
 This toggles autoop or joining on start for <chan>.. Autoop is whether
 users defined as autoopable users are autooped, and joinonstart is whether
 the bot joins channels on start..
8. .join <chan>
 This command is used to temporarily join a chan, as long as it's in the 
 emulti database. Can be used on chans without joinonstart and channels
 that you have used .leave on/
9. .leave <chan>
 This command is used to temporarily leave a chan. The userfile database 
 entries are still stored for future use, and you may use .join and .leave
 as often as you need. 
