Haven't done jack with TB in months. Code is stable and the !seen and !setinfo commands have been tweaked and the maintenance command that cleans up the ini's has been working great since redone a couple of months ago (went from 1-2 minutes to 10-15 seconds). Been doing a lot of "quotes" stuff with the !movie/!movielist and a few others (!sp and !quote). Getting the bot to not repeat (as much) wasn't too hard. I've also integrated some sudo "services" into the boot with a nice interface that I need to finish. I made a decision back in the spring not to release the tb code. I was pushing for getting the bot generic but had to make a choice in terms of coding to either hard code the script and keep maximum performance and features or lose some features and really have to do some crazy programming to get away from the hard coded stuff that's in TB. The good news is that I'll probably at some point start a new from scratch and redo the bot a 4th time with a more module approach as most of the script "features" are now VERY modular in the way they were scripted...here's a picture of the current box TB is running on...

First update of the New Year. A lot has changed since the last update. I have completely re-organized the TB script files and have started moving towards the third major TB revision. Unlike the last, this one will be done as a clean b0t with non of the old ini's being used except as objects/modules. That is to say that the foundation is getting an overhaul for the text triggers will remain. This will effect the way the b0t follows join's, part's, quit's, nick changes, topic changes, voicing and op'ing, spamming of info, channel protection, clones, etc.etc. Also, as sorta a exercise I'm going to take TB3 and package up the source code with an install script and release the b0t code sometime in May99. Included would be b0t documentation as well as the install script that would allow other clans/3rd parties to install their own "TB" to monitor their channels.

Haven't updated in a while basically because no one knows this pages exists except maybe a few since there are no direct links to it from the main page. I had put this page together because of the new page I was working on at the time had a little "TB" button that would jet you here. A hard drive crash has put me back to square one on the page.

A lot has been upgraded/changed to TB since the last update. I had to split the script.ini into smaller chunks because of a limitation to the size mIRC ini's could grow (30K btw). This was actually beneficial to my programming since I can now jet to different parts of the script depending on the function of that script. Examples being initial.ini for all the join's and CTCP stuff, text.ini for like all the text triggers, and so on. Lot's of stuff in the hopper ( as you can see above ).

Added the To Do list. When we redo the KI page...this page will have a little "secret" link to the page. You'll see...it'll be cool.

Here's is the below menu revised a little to be a little more logical and easier to use.

<<Snip>>
-
B0t Channel Commands
.Channel Topic's
..Add to Topic:/notice [Time-b0t] addtopic $chan $$?="Text to add to Topic"
..topic No. 1:/notice [time-b0t] topic1 $chan
..topic No. 2:/notice [time-b0t] topic2 $chan
..topic No. 3:/notice [time-b0t] topic3 $chan
..topic No. 4:/notice [time-b0t] topic4 $chan
.Channel Security
..Add to Auto-Voice List:/notice [time-b0t] addv $chan $$1
..Remove to Auto-Voice List:/notice [time-b0t] remv $chan $$1
..Add to Auto-Op List:/notice [time-b0t] addop $chan $$1
..Remove to Auto-Op List :/notice [time-b0t] remop $chan $$1
.Give
..Ops to user:/notice [Time-b0t] opuser $chan $$1
..Random Ops:/notice [Time-b0t] opuser2 $chan $$1
..Voice to user:/notice [Time-b0t] vuser $chan $$1
.Take
..Ops from User:/notice [Time-b0t] deop $chan $$1
..Voice from User:/notice [Time-b0t] devoice $chan $$1
.Kick/Ban
..Kick User (Why) :/notice [Time-b0t] kickuser $chan $$1 $$?="Reason for Kicking?"
..Kick User:/notice [Time-b0t] kickuser $chan $$1
..Kick/ban User (Why) :/notice [Time-b0t] kickbanuser $chan $$1 $$?="Reason for Kicking?"
..Kick/ban User:/notice [Time-b0t] kickbanuser $chan $$1
..Shit List User:/notice [Time-b0t] shitlist $chan $$1 $$?="Reason for the Shitlist"
..Remove User from Shitlist:/notice [Time-b0t] reshitlist $chan $$1
.TB Maintence
..Default Nick:/notice [time-b0t][2] changenick
..Join #KI:/notice [time-b0t] joinki
..Leave #KI:/notice [time-b0t] leaveki
<<Snip>>

I've setup Time-b0t to accept commands via YOUR IRC client via your IRC menu's. Here's what I have so far for TB. This is using "Notices" to do all the messaging to do the b0t admin functions. It's a lot cleaner than sitting in the channel doing "!kick That_Fool". You can use some of this...or you can use all of this. If you're running Virc, I'm sure Glide will be converting this to the Virc scripting language and will hopefully email it back to me to post.  I will be putting all of this on its own page when it's "Finished" for easy referral. **Please note that I do log all b0t requests to the channel #tbdebug. Finding folks that are abusing the b0t couldn't be easier**

These were specifically designed for Mirc...enjoy:

Go under the pull down menu "Tools" and select "popups" or do a "Alt-R".Once there...make sure that you select the "Popups" tab and under the pulldown menu "View" that "Nickname List" is checked/selected. Scroll down to the bottom of these file and copy past the below example minus the <<snip>> lines. Including the "-" on a single line will tell Mirc to put a horizontal bar there. Please understand that TB evaluates users not on who's op'd, but by its userlist. So even if someone is op'd in our channel, it doesn't mean they can operate the b0t.

<<Snip>>
-
B0t Channel Commands
.Give Ops:/notice [Time-b0t] opuser $chan $$1 $$2
.Give Random Ops:/notice [Time-b0t] opuser2 $chan $$1
.De-op User:/notice [Time-b0t] deop $chan $$1
.Kick User (Why) :/notice [Time-b0t] kickuser $chan $$1 $$?="Action to perform"
.Kick User:/notice [Time-b0t] kickuser $chan $$1
.Kick/ban User (Why) :/notice [Time-b0t] kickbanuser $chan $$1 $$?="Action to perform"
.Kick/ban User:/notice [Time-b0t] kickbanuser $chan $$1
.Shit List User:/notice [Time-b0t] shitlist $chan $$1 $$?="Action to perform"
.Remove Shitlist User:/notice [Time-b0t] reshitlist $chan $$1
.TB Maintence
..Default Nick:/notice [time-b0t][2] changenick
..Join #ki:/notice [time-b0t] joinki
..Leave #ki:/notice [time-b0t] leaveki
.Channel Topic's
..Add to Topic:/notice [Time-b0t] addtopic $chan $$?="Text to add to Topic"
..topic No. 1:/notice [time-b0t] topic1 $chan
..topic No. 2:/notice [time-b0t] topic2 $chan
..topic No. 3:/notice [time-b0t] topic3 $chan
..topic No. 4:/notice [time-b0t] topic4 $chan
.Channel Security
..Add to Auto-Voice List [5]:/notice [time-b0t] addv $chan $$1
..Remove from Auto-Voice List [5]:/notice [time-b0t] remv $chan $$1
..Add to Auto-Op List [5]:/notice [time-b0t] addop $chan $$1
..Remove from Auto-Op List [5] :/notice [time-b0t] remop $chan $$1
-
<<Snip>>

The b0t isn't perfect...please be patient. If something really bad happens Please email me at Timedie@glides.com.

I Start the TB Page...w00h00! What was just a passing hobby and convenience for the clan is now a little Pet project. This page is grossly under construction as I haven't had time to put anything really together in the way of art work....but the gears are working on something.

******Mini FAQ******

Q. Can I get a copy of the TB source now?
A. No. TB has been highly "hacked" and modified for specific channels and users and until I go back in and change some the script around to be more universal andopen in it's approach it would incur a lot of work from the recipient to try and get the b0t to work for them. It would be very buggy in other words....

Q. Why didn't you do TB in TCL or vIRC?
A. This b0t started as an mIRC script and will finish as a mIRC script. Because of the amount of work that has been done already and that probably will be done to map out the functionality and the commands that tb uses, it will be many times easier to take those notes and re-create TB in another irc scripting language after this project comes to a close.