There's a script I submitted to egghelp some years ago now, under a different name even, pisg-0.5.tcl, that I have bothered to finally clean up.
You will need: pisg - IRC Statistics Generator
Windows/Windrop Users: You will need ActivePerl. Install and associate with .pl files during the installation. Rename pisg to pisg.pl (possibly not needed) from the pisg-0.xx.zip.
Windrop error "couldn't create error file for command: no such file or directory": Downgrade to Windrop 1.6.17 and replace your libtcl8.4.dll with this one: libtcl8.4.dll. See this thread for more information.
Features:
- FTP uploading of html files (Windows/*NIX compatible sendftp routine included, based off Ernst's)
- Automatic/scheduled updates.
- Blah blah blah.
The binds are currently n|n.. you might want to change that to o|o or -|- depending. I'll add a setting for it. You can do !pisg * to update all channels found in the config file, !pisg in a current channel will update that channel, you can do !pisg <channel name> to update another channel. You can update in private message or dcc too, blah blah blah.
Automatic Updates: Currently, if you want a particular channel to be automatically updated at the configured times, set it to +pisg. This is problematic at the moment as you will also require +pisg in order to use the command publically in a channel. I was thinking I might add 2 channel flags for this script, +pisg (for public command control) and +pisg_auto (for whether this channel is included in automatic updates), would like some feedback on this.
Channel Prefixes: The other thing is I am currently only (manually) checking for # and & in channel names. But in a future release I will make it detect your channel prefixes based on your pisg config file.
Output Folder: There is no ftp_local_folder or pisg_folder setting because the script will figure out where your output files are being generated from your pisg.cfg, and upload them from wherever (if using ftp). If your OutputFile settings in pisg.cfg are not full paths, eggdrop will run pisg, and they will get generated in your eggdrop folder (this is also OK). Basically, your configuration requirements will be minimal.
Sample pisg.cfg with most settings.