When extracting your downloaded acttrack3.tar.gz or acttrack3.zip, the file and folder structure isn't optimal. Here is a layout of the intended usage. This is example assumes that the users web folder is ~/public_html/, sBNC is installed and running in ~/sbnc/ (default) and you want to have the statistics presented in a folder named acttrack3.

/home/user/public_html/acttrack3/index.php
/home/user/public_html/acttrack3/config.inc.php
/home/user/public_html/acttrack3/functions.inc.php
/home/user/public_html/acttrack3/search.php
/home/user/public_html/acttrack3/default.css
/home/user/public_html/acttrack3/gfx/acttrack3.png
/home/user/public_html/acttrack3/gfx/blue-h.png
/home/user/public_html/acttrack3/gfx/blue-v.png
/home/user/public_html/acttrack3/gfx/green-h.png
/home/user/public_html/acttrack3/gfx/green-v.png
/home/user/public_html/acttrack3/gfx/red-h.png
/home/user/public_html/acttrack3/gfx/red-v.png
/home/user/public_html/acttrack3/gfx/yellow-h.png
/home/user/public_html/acttrack3/gfx/yellow-v.png

/home/user/sbnc/scripts/acttrack3.tcl

• Edit sql_user, sql_pass and sql_db in acttrack3.tcl.
• Load account.tcl and acttrack3.tcl in sBNC using the following in sbnc.tcl

  set ::account354 "botname"
  setctx "botname"
  source "scripts/account.tcl"
  source "scripts/acttrack3.tcl"

  botname is the sBNC user which will do the logging.

• Rehash sBNC
• Set the usertags for ”botname” to specify what channels to be logged. Remember to change ”botname” for each command to the user with acttrack3 loaded. It defaults to log all channels.

  # Set channels to either LOG or NOT LOG depending on acttrack.method 
  /sbnc set acttrack.chans #chan1,#chan2,#chan3
  # Choose method the channellist above is to be, include will log those 
  # channels, exclude will log anything but those channels
  /sbnc set acttrack.method include
  # Ignore certain auths from logging completely
  /sbnc set acttrack.ignore auth1,auth2,auth3

Currently there are no instructions on how to make acttrack3 run on eggdrops since the basics rely on features that come with sBNC. Several people has asked if it will work for eggdrop and I am sorry to inform you that I probably wont have time for that myself. A third-party, however, has mentioned that he might do it. More on in this section later.

If one wants to use eggdrop instead of sBNC, http://thommey.tclhelp.net/eggdrop.html is a good place to start. It was what inspired the sBNC developer to create that function in sBNC.

Things in Acttrack v3 that is dependent on sBNC:

• Getting auths of users. sBNC includes a TCL script (account.tcl) which maintains an internal link between nicks and their auth in Q, through some advanced queueing of /who commands.
  Unfortunately for eggdrop users, account.tcl relies on functions not found in eggdrops. So to use acttrack3 with eggdrops you need to make your own scripts that gives acttrack3 a function, [getchanlogin NICKNAME], returning the auth of specified nickname
  One way to do this is to patch eggdrop.
• Saving settings. sBNC allow users to save user-specific tags which Acttrack3 use to determine what channels to include/exclude when gathering statistics, and what auths to ignore. The act_filter function in acttrack3.tcl is used to check these user-specific tags.

• Import the table definitions from acttrack.sql into your MySQL database using the following command in a shell, replacing ”port_num”, ”user_name”, ”pass”, ”database” and the path to ”acttrack3.sql”.

  mysqlimport -L --host=localhost --port=port_num --user=user_name --password=pass database ~/acttrack3/acttrack3.sql

  Or, as prefered, import it using phpmyadmin.

• Edit config.inc.php - only required changes are the MySQL login data.
• Place everything in the web/* folder in a folder accessable by apache, like: ~/public_html/acttrack3/, if you extracted the .tar.gz in your ~/ folder you can use (in a shell):

  $ mkdir ~/public_html/acttrack3
  $ cp -r ~/acttrack3/web/* ~/public_html/acttrack3/

Open up a browser and go to, http://server.domain.net/~user/acttrack3/

If it does not work, have a look at the Troubleshooting page.