This program comes WITHOUT ANY WARRANTY, without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

I am NOT RESPONSIBLE for ANY harm this script and|or its use may cause to you and|or any third party, that includes, but is not limited to, property and ANY and ALL things.  This script comes AS IS with NO GUARANTEE of any kind, neither expressed nor implied.

[*] T|X does _NOT_ contain IRC war tools.

[*] For official distribution sites and credits, type /CREDITS.

[*] If, you use anything of mine, give me credit, I try to credit all codes I use, even ideas and concepts, the same courtesy is appreciated.

[*] This script will help you have and maintain more than above average control over your channel(s), help you protect the same, and yourself, against channel takeovers, floods and other such warlike and annoyance tactics. If, you want a script which is feature rich, protection oriented, and totally all around kick-ass kewl, then this is the script for you, cause it frigging RuLZ! };>

[*] This script is not intended for new irc users, but rather, for the more experienced. Nevertheless, if after having read this notice, you wish to use T|X, I strongly advise you read this text file and use the help menus to familiarize yourself with the commands, know what the script can do for you, do not expect to know it all, unless you take the time to learn it all. Soon you will be mastering this powerful irc tool.

[*] A script can be a great tool for an irc user. However, I do very strongly suggest, that you try and learn the actual irc commands and be able to irc without a script, if the need arises.

[*] This section will no longer mirror the contents of the README.TXT file, which accompanies the TeRMiNaToR releases, you're gonna hafta read the doc from now on boyz and goilz.  As always, any post release news and information can be found at the _WHAT'S NEW_ section of this web site.

[*] This distribution package includes the following:

MODULE|FILE   DESCRIPTION

[*] tx-term.irc
MAIN utility|defense module.

[*] tx-help.irc
HELP module for EVERYTHING.   Type /THELP.

[*] tx-extras.irc
EXTRAS module.  Type /THELP EXTRAS.

[*] tx-bot.irc
BOT module, make sure bots are allowed on your server before running. Type /TXB HELP.

[*] tx-annoy.irc
ANNOY module.  Type /THELP ANNOY.

[*] tx-kicks.irc
KICKS module.  Type /THELP KICKS.

[*] linkfind.c
Seeks servers that allow you on, use a server that "allows" bots. Type /LINKFIND.

[*] lookup.c
Converts IP to domain.  Type /LOOKUP for HELP.

[*] netscan.c
Lists network IP.  Type /NETSCAN for HELP.

[*] portscan.c
Finds ports.  Type /PORTSCAN for HELP.

[*] progs-c.tar.gz
All above c programs are kept in here.

[*] txsetup
Compiles, sets up your c files, and makes your directory|file structure for T|X - USE IT.

[*] sample.ircrc
Sample .ircrc file - YOU NEED THIS.

[*] terminator.xdcc
Sample .terminator.xdcc - YOU NEED THIS.

[*] If, you encounter a bug in the script, email me telling me the problem(s), include a log clip showing the error(s) if possible (_TRY TO KEEP THE LOG CLIP BELOW 10K IN SIZE_) and:

1) Name(s) of other script(s) (if any) you had loaded.

2) Your irc client version.

3) Your irc server version.

4) The OS you are using.

5) The UNIX SHELL you are using.

6) Any other information you deem relevant and necessary.

[*] I will look into it and try to have the problem resolved by the next release issue of T|X. If, I can not recreate it, I can not fix it.

[*] If, you have a fix for any bug, email it to me, it will be appreciated, and if implemented, credited to you in the next release.

[*] Do not automatically assume anything apparently not working is a bug in the script, take the time to read the related docs, make sure it is not U.B.F.
(User Brain Failure (c) Taz).

[*] GUNZIP AND UNTAR T|X

You may use this syntax to gunzip and untar the tar.gz file:

[*] TYPE TXSETUP FROM A UNIX PROMPT AFTER YOU GUNZIP & UNTAR T|X

Depending on your system and how your path is set or not, you may need to type ./txsetup to have the file execute.

[*] From IRC with tx-term.irc loaded type this config command:

[*] To get HELP (with tx-help.irc loaded) type /THELP.

[*] All HELP for PROTECTION toggles are in /THELP USER (page 4).

[*] In order to use this script properly, you MUST load it via an .ircrc file, this is NOT optional. If, you do not have one, use the "sample.ircrc" file supplied with this package, and be sure to RENAME it to .ircrc

TXSETUP file automatically does this for you.

If, you already have an .ircrc file, your original .ircrc file will be backed-up and renamed to .ircrc.bak by TXSETUP.

[*] In order to avoid error messages on startup, you MUST have the file ".terminator.xdcc" in its appropriate path, failure to do so may result in errors during your irc session. Use the
 sample "terminator.xdcc" file accompanying this package and RENAME it to terminator.xdcc if you so wish.

TXSETUP file automatically does this for you.

If, you already have a .terminator.xdcc file, your original file will be backed-up and renamed to .terminator.xdcc.bak by TXSETUP.

[*] Remember to /SAVE after you have upgraded, made a first time installation and|or changed any variable(s) you wish to retain.

[*] T|X is made to run on ircII clients v2.8.2 (19950405) or later.

[*] T|X may NOT work properly with some versions of the following:

[*] Please keep in mind that, T|X as with any other script of its class, may not be fully compatible with all IRC nets and its servers, the reason is simple, the various nets currently
operating do NOT all have the exact same server|ircd config, although I do try to make it as compatible as possible with all nets currently known to me, I can only stay current of the
net(s) and the server(s) I most frequent. Moreover, the same applies to the various UNIX OS currently in use, I can only ensure the compatibility for the OS I work with, currently SunOS, Solaris and Linux.

[*] If, you encounter a compatibility issue, email me telling me the problem(s) and follow the instructions under:

[*] The script default is set to turn ON your IRC LOG when you enter IRC, if you do not want this, once in irc type /IRCLOG OFF then /SAVE.

[*] This will allow the unflash in T|X to work properly, once set accordingly, in your appropriate shell configuration file(s).

[*] For csh      :  setenv TTY "$tty"
[*] For bash    : export TTY="$(tty)"
[*] For tcsh     : setenv TTY "$tty"

[*] If, you do NOT have NSLOOKUP available on your system, the protection against dcc-bombs could be decreased, otherwise, protection should be outstanding.  Regardless, I recommend you keep dcc auto get OFF all the time (T|X default setting), new bombing techniques and floods are created constantly and one can only protect against that which is known at the time of creating the protection, no protection routines are 100% infallible, at least, not forever, nothing is forever.

[*] If, you do not have NSLOOKUP installed in your system, you will receive a ONETIME per irc session notice message from T|X when you receive a DCC for the first time, informing you of this.

[*] LINX (Links Internal Net Xplorer) is a BOTLESS server split and merge scanner.

[*] It will automatically (when engaged) report any splits and merges of servers to the irc network structure.

[*] I do NOT recommend the use of this feature for a prolonged period of time.  Although it employs a "VALID" irc command called "LINKS" running this command frequently may get you possibly K-lined and|or Killed by IRCops mistaking you for a bot and|or because they may feel you are wasting their resources.

Basically, it does _NOT_ take a lot to be killed by _some_ IRCops.  Moreover, keep in mind that these trigger happy IRCops, usually have no life, small peckers and/or are past 30 and still wearing their hymen! heh <G>.

The default check time cycle for LINX is 1 minute, I do NOT recommend you go below that setting.

[*] This program does NOT lag me, nor has it lagged any of the beta testers, it may however, depending on your system and resource factors, lag you.

[*] TX-BRO only works if BOTH parties (requester and you) run T|X, ALL users of TX-BRO including yourself MUST have the SAME password.

[*] For more HELP (in IRC with tx-help.irc loaded) type /BROHELP.

[*] The intended main purpose of TX-BRO is to help the process of synching a channel, specially when someone is just idling in the channel (as is usually the case) and is the only one holding OPS. Therefore, the abilities of JOIN and PART are included for this purpose. TX-BRO is far more secure than regular friends list, due to the password checking and
screening it performs on each request, which is obviously necessary due to its abilities and intended purpose.

[*] It is obvious, that you should NOT use TX-BRO as you would the regular friends list, and if you do, be very careful when placing the privileges past the default setting of (OP INVITE UNBAN), in other words, unless you are going to give full privileges, you might consider using your regular friends list.

[*] I have had users ask these questions in the past, so here are the answers for everyone that cares to know.

Q1: Why does T|X ignore, ban and kick the shit out of people using BitchX, mIRC or similar clients/scripts?

A1: Unless, they have actually attempted to flood you, the most common reason is, the other user has made contact with you and said contact most probably included COLORS.

T|X reacts the way it does to colors because some sequences employed in colors contain CONTROL CHARACTERS which are/can ALSO commonly be found in SOME FLOOD STRINGS. In effective flood prot such as found in T|X, the same scans for these
CONTROL CHARACTERS to protect you against floods that could cause you harm.

Q2: What can I do to stop ignoring, banning and kicking the shit out of BitchX, mIRC and other users that trigger my flood protection?

A2: To better control flood protection:

a) READ the README.TXT and /THELP USER (page 4). This will help you know wtf  you are doing.
b) FLEX the person (/FLEX <Nick>) This will exempt the person from flood prot.
c) Set higher triggers via /CONFIG.
d) Toggle CFPROT OFF (/CFPROT).

WARNING: Setting /CFPROT "OFF" _WILL_ expose you to some specific types of FLOODS, which can potentially disconnect your IRC session.  Turn it OFF at your own risk, you have been warned.

Q3: How do I make DCC CHAT messages not have a long header?

A3: To shorten incoming DCC CHAT message headers:

a) /EXTMES (this will also affect MSGS and NOTICES)

Q4: Why does anti-idle (/ANTIDLE) have to use the "." (dot), and why does it not use other methods to keep unidled?

A4: Not all servers currently will reset your idle time by employing other commonly used methods, in fact, it is much easier to make an anti-idle which uses more common methods,
but it just will not work on all servers, and the goal is global compatibility, this is the only one method currently compatible with all servers, which will get the job done.

Q5: Why are people not able to get a reply from me on CTCP FINGER, TIME and VERSION after they request the same once?

A5: Yes they can, however, each requester is allowed ONE per cycle request, the cycle time interval, is the same as your ignore time limit, and it will not clear until you have had no requests from anyone for that time frame.

This helps the flood protection against bot-nets and alike from spamming you with CTCP requests, etc. Besides, why would anyone need to request TIME, FINGER or VERSION more than once per cycle anyways?

Q6: Do you really know all them people on your credits list?

A6: I know most of them, some are friends, some are enemies, some are neither, some are just mega lamah plonkers <G>.

However, they all to my knowledge, no matter how large or small, have made a contribution in the way of a concept and or code. I believe it fair to give them credit, my motto, unlike that of some of the people on the credits list, is "give credit where credit is due" and not try to hog the spotlight and pretend to have invented ircii code and all else in the code universe. };>

Q7: Is there a way I can make more space in my status bar?

A7: Yes, use the /CSTAT command to toggle the status bar flags and DCC sent|pending file counter ON|OFF.

Q8: What does the flags in the channel mini stats mean?

A8: The channel mini stat flags mean as follows:

TOT = Total number of people in the channel.
+o  = How many people in the channel have OPs.
-o  = How many people in the channel have NO OPs.
+v  = How many people in the channel have VOICE.
H  = How many people are HERE (not set away).
A  = How many people are AWAY.
COP = How many IRCOPS are in the channel.

Q9: Can I turn NOTIFY OFF so it doesn't lag me at login?

A9: Yes, type /NOTIFY -OFF. If, you want to turn it ON again, type /NOTIFY -ON. The setting can be saved via /SAVE if you so wish. The default setting is ON.

Q10: Why is it that on nethacks T|X still deops people I have in my friends list?

A10: If, you have the user in your friends list, the user MUST be in the list with OP PRIVS,
if not, T|X assumes that you obviously do not want this user to have ops.

If, the user is in the friends list with OP PRIVS, then it is most probably, due to you having an unsually LARGE list of friends, the nethack process takes basically a fraction of a second, in that time, T|X must compare the userhosts of ALL the people nethacking against your list of friends, as you can well imagine, the larger the list the longer it
takes, if T|X can not process the entire list in time to safely determine if the nethacker(s) should be deopped or not, then it defaults to deop, to avoid having you lose the
channel. When in doubt, kill it <G>.

Q11: How do I work NHP (Nethack Protection)?

A11: To control NHP:

a) /NHP OFF|ON (turns NHP OFF|ON).
b) /NHP BK (toggles NHP Ban Kicking OFF|ON).
c) /NHP CF (toggles NHP friend check OFF|ON).

Q12: Why does NHP act erratic and/or fails to perform at times?

A12: Thank TS (Time Stamp) and the alike clones for that.

In theory, TS should have done away with the need for NHP, however, in _practice_ TS causes  more trouble to the user than it's worth,  like desynches and  the bugs which cause
deops of the  wrong people and  thereby enable the channel takeovers, just to mention a couple.

The main purpose  for TS and  alike is the  need of _some_ IRCops not to feel threatened and vulnerable via killides, and to feel in _control_, thereby making them feel God and
31337 like, giving them what they  wanted when they kissed ass to get the 113 in the first place.

Q13: How do you add people to the TX-BOT auto-op list?

A13: The TX-BOT auto-op list works off your friends list.

Q14: When will you add channel selection to the friends list?

A14: The friends list has a channel selection, although, it is limited in the way that, you can only globally assign them.

When I first made T|X (many moons ago) for the exclusive use of the IRC group K.O.E. (Knights of ExCaLiBuR) we did not differentiate amongst us, if you were a friend you were welcome in all our channels and shared ops, this is why T|X is this way, which is a concept I personally still believe in today.

This is on my things to do list, but the friends list is tightly joined to the protection and therefore any changes to be made need to be done very carefully and beta tested extensively, since this is not a priority nor a bug, it can wait.
: 
Q15: Why are some of your answers so long?

A15: Cause I'm a friggin intense and passionate bastah <G>.

[*] If, you get this script from ANYONE|ANYWHERE, except the above named OFFICIAL SITES, discard it and obtain a new copy from any of the aforementioned OFFICIAL SITES. Distribution files on official sites are checked on a regular basis to
ensure file content integrity.

[*] When you do not obtain copies from official distribution sites, you take the risk of obtaining a copy that has been tampered with, these tamperings could serve to insert any given number of potentially malicious code, such as backdoors to control your client, remove your $HOME, damage your computer, etc.