AutoTRIG®
99.24.11 HELP FILE
email: autoscript@usa.net
website: http://autoscript.fr.st/
Note:
updated for mIRC 5.91 (appears compatible with 5.71, 5.82
& 5.9)
Watch
for highlighted
items, representing new features or details in this version of AutoTRIG.
Note:
Details of dcc send "A2" protocol can be found in a file
contained within the AT® 99 zip file, entitled A2_protocol.txt. The
authors of this protocol welcome input from anyone interested in promoting
growth of the dcc send trigger format and encourage anyone creating a dcc
trigger server or client to participate by incorporating details of the
protocol within your coding!
OVERVIEW
This
script is designed to aid in maintaining triggers for individual files
(single file type) or group of files (collection type) or FServe type
triggers. In addition to maintaining the triggers, there are supplemental
functions such as creating .txt files that represent the triggers within
the system. Once a trigger exists, this script can assist in making an
offer to display on irc channels to advertise the trigger or group of
triggers.
INSTALLATION
New
Installs
Move
ALL files to your mIRC folder
then in any
window type
/load -rs at_install.mrc
then in
any window type
/at_install
Once
installed you'll see the choices offered by the script by right clicking
in an active channel, status or select "Commands" in the menu
bar..
AutoTRIG® (Off/Off).
Upgrades
Move
unzipped files to mIRC folder.. right click in active channel, status or
select "Commands" in the menu bar.. click
AutoTRIG®
(Off/Off) line..
select
Utilities and
then Upgrade
AT® ..
press the button.. new upgrade will then be loaded. If you are wanting
to re-install AutoTRIG, and do not want the old data to remain, uncheck
the box at the bottom of the install dialog,
and the data will be overwritten. The install script will
compare your version of mIRC with a list of versions AT® has been
tested with. If the version
has not been tested, you will be notified, installation can still
continue at your own risk.
Uninstall
This selection allows for removal of AT®.
All script files will be removed from mIRC remote and all AT®
variables will be erased from the common variable window.
The AutoTRIG® folder with scripts and data files will remain
intact and will need to be removed by hand if you want total removal.
Uninstall is found under Utilities in the main AT® menu.
CONTROL
PANEL
Allows
entering your favorite channels (you may choose to join or part any or all
of them), and allows selection of which channels will see your offers.
This panel also maintains a time separation between offers and
allows you to start an offer timer. Enabling
and disabling trigger response is also handled on this panel.
If you use removable media (such as CD's or Zip/Jaz), you can input
the current on-line volumes in this area and then update the trigger lists
and to view them. Entry of Sends/User for AutoTRIG® and FServer triggers.
Offer
timer
Enter the desired number of minutes between offers and push the
START TIMER
button.
To stop offer display press the same button that will now be labeled
STOP TIMER
Trigger
Master
Select
to ENABLE /
DISABLE trigger
use. When 'disabling' there
are four choices:
Normal
that places a notice in display channels that your triggers are
off-line
w/Message
same as normal but allows you input a short message to the
channel
Countdown
gives a timed notice that triggers will soon be off-line
Silent
only notice of off-line triggers is to those currently receiving
transfers
Command
Line functions
There are 3 command line functions to assist with controlling parts
of AT99®.
/alos
will
start and stop the offers timer
/alo <offer number>
will
display the offer number entered to the channel in which the command is
typed
/atts
will
start and stop the master trigger control.
Sends/Person
Enter the desired number of sends at one time to any one individual
person for AutoTRIG® and FServer triggers.
Reserved
The total box displays the max sends you have chosen in mIRC DCC
options. The Reserved box is for entry of the number of total sends you
want to save for use only when sending .csv and .txt files. The idea is
to allow users to be able to get the small files like .csvs as quickly
as possible. Recommend at least 1 or 2 reserved slots.
Note:
you can control the total number of sends at one time to ALL users with
a function under mIRC's DCC|Options. This does not limit manually
initiating a DCC send but it does apply to
users who request a DCC send remotely
i.e. via AutoTRIG®.
Channel
entry
Enter the
channel name, the associated check box enables/disables offer displays
for the selected channel, in addition to choices for joining or parting
the channel. To remove a channel, highlight the channel name.. hit space
and then push the 'ENTER' button next to the trigger name. The 'JOIN'
and 'PART' buttons allow you join and part your favorite channels.
Removable
media
Enter the
Volume ID of the on-line CD's and Zip/Jaz, the script can then create an
updated trigger.txt list that accurately reflects the collections that
are currently on-line. The "Volume ID" is described below in
the Trigger Wizard section.
Enable/Enforce
Class
Toggle status of each user
class, enabling/enforcing the class or not. Works the same as the
controls within AT Options, just makes them more accessible.
Trigger
Lists
Choose to update any of the trigger lists and review the results.
Active
Trigger List
refers
to the .txt file containing only the currently on-line triggers (based
on your input of the on-line removable volumes).
Singles
Trig List (SGL.txt)
refers to a .txt file that contains ONLY single file type triggers
that are currently on-line
Collections
Trig List (COL.txt)
refers
to a .txt file that contains ONLY collection type triggers that are
currently on-line
Removable
Trigger List (REM.txt)
Consists
ONLY of the triggers that are contained on removable media.
Logging
View, erase or
START / STOP logging
of trigger requests. There are also functions for quickly sorting some
the more common log results.. such as viewing all busy trigger requests.
The logging file (AutoTrig.txt) is now limited to a 10,000 line maximum,
as new logging entries go in, older ones are removed. 'Busy' requests
are no longer logged.
Control
Panel can be opened at any time and remain open your entire session or
closed at any time. There
also 3 command line functions to assist with controlling parts of
AT99®. /alos will start
and stop the offers timer, /alo <offer number> will display the
offer number entered to the channel in which the command is typed, and /atts
will start and stop the master trigger control.
OFFERS
WINDOW
Allows
entry of Offers (channel ads) and keeps an equal time spacing between
them. The current version manages up to 99 offers..
(User has control over number of offers to be available on their
system up to 99).
Offers
Popup Menu
An Offers
popup menu is available by right clicking in the Offer window.. choices
include Edit/Creation Wizard, Delete, Status, Test, Display to channel
selections, Start/Stop Offers Timer, in addition to control of the Offer
window settings (described later in this document).
The
'Delete' button can be more than it says, depending on settings on the
Offers Page in Options. Delete
can be used to ONLY delete the selected offer.
By choosing Delete 'Single
Triggers' w/Offer in
options, there will be a second menu choice to delete any "Single
File type triggers associated with the offer.
By also selecting the Delete
associated file option,
a third menu item will appear that allows to remove the offer, trigger
AND the associated file with one click. In fact.. by highlighting
multiple offers, you can remove several offers, triggers and files with
one click.
Note:
if choosing to delete files along with offers and triggers, the file
will actually be moved to a folder under mIRC named Recycle.
Any deleted files can be recovered from that folder by using
Explorer or another file manager. Or deleted permanently by selection in
the 'Recycle window'.
Once an
Offer is created.. double click it to turn the offer status to ON/OFF.
An Offer can be removed from rotation simply by toggling its status to
the OFF position. Testing an offer results in echoing the offer in a
channel window to see how it will appear to others when actually sent to
the channel. You can choose
to manually send offers to all selected channels or ONE individual
channel from the Offers window popup menu.
Start/Stop the offers timer from the offers window.
Edit/Offer
Wizard
Dialog that
allows editing of an existing offer or the creation of a new one. The wizard
allows you to choose elements to include in a basic offer. The
message created differs depending on the elements chosen and the type of
trigger that is being targeted (single file or collection).
To use the wizard hit the
CREATE button,
enter the reference number of the trigger you wish to target and select
from the choices provided, press CREATE
again
and you will be able to edit, test or save the offer created by the wizard.
There
are three templates available for "Single File" triggers and
another 3 templates for "Collection" triggers.
Color
selections are made by pressing <ctrl>k and using mIRC's own color
dialog.
Offer
Identifiers
The
following identifiers can be used in an offer to represent information
you may wish to present:
*ctrig
number of currently on-line COLLECTION type triggers
*ftrig
number of currently on-line FSERVE triggers
*strig
number of currently on-line Single FILE type triggers
*bw
bandwidth currently used (cps)
*chan
channel the offer is displayed in.. displays proper
channel name
*etime
duration of time since updating the last single trigger to appear
in an offer
*ip
your current ip number (xxx.xxx.xxx.xxx)
*me
your current nick
*new
date and time of last editing of active triggers (01Mar@10:01)
*etime
elapsed time since single file in offer was last updated
(such as trig list) *new
*mtime
date and time
of the last single trigger to appear in an offer
*max
the number of max sends defined within mIRC
*fmax
the number of max fserve sessions defined within mIRC *new
*sends
the number of sends currently in progress
*fserv
the number of active fserve sessions in progress *new
*cds
the identity of current on-line cd's (CD_1)
*zips
the identity of current on-line zip/jaz drives (Zip_1)
*trigson
total number of
triggers currently on-line
*trigsoff
total number of
triggers currently off-line
*trigstot
total number of
triggers
I dentifiers
are shown in the Offer Wizard in a scroll box.
By double clicking a particular identifier.. you will add it to
the 'end' of the offer. The following identifiers are used for display
of trigger information, in addition to making sure your nick is always
displayed properly in the trigger,
Format:
#T900 *T900 #C900 *C900 *D900:
*C1
the name of trigger CSV: !Trigger.CSV
#C1
the complete triggerCSV: /ctcp yournick !Trigger.CSV
*T1
the name of trigger: !Trigger
#T1
the complete trigger: /ctcp yournick !Trigger
*D1
the trigger description text
A typical
raw offer might look like this example:
Raw:
offers
SDC99. Type #T60 for the
scans, and #C60 for the csv.
Actual
display:
HackerOne offers SDC99.
Type /ctcp HackerOne !SDC99
<filename> for the scans, and /ctcp
HackerOne !SDC99.CSV for the csv.
Offer
Modifiers
Displaying
random collections can be
accomplished by beginning an offer line with #random. Using
#random 4 would result in displaying only
collections updated in the last 4 days. The requirements for an
offer to display a collection:
1)
the description for the trigger must contain [folder count/csv
count] details
2)
the counts of folder and csv must match (100%)
3)
the trigger must be turned on
4)
if a CD or ZIP mounted collection.. it must be Online
While it is
possible to intermix dedicated identifiers with random identifiers, any
random identifier must be carefully inputted with NO trigger number
information (ie: *T #T *C #C *D):
Raw: #random
_3r_2a_4n_5d_7o_10m_12l_1y_ offers _4*D_. Get the scans with #T or the
csv #C _14(*sends/*max *bwcps)
Actual
Display: HackerOne
randomly
offers SunScan
(173).
Get the scans with /ctcp HackerOne !SunScan
<filename> or the csv /ctcp
HackerOne !SunScan.CSV (4/4 6883cps)
The
following modifiers let you control the display of specific offers to
specific channels. There are 2 types.. one inclusive, the other
exclusive.
Inclusive
To
include a specific channel to receive a specific offer, begin the
offer with the following modifier: #chan:<chan number(s)> where
<chan number> refers to the channel line in the control panel
containing the channel(s) in question. If, for example you want
to include the channel on line 1 and line 4, the offer would begin
with #chan:1,4
Exclusive
To
exclude a specific channel from receiving a specific offer, begin the
offer with the following modifier: #chanX:<chan number(s)> where
<chan number> refers to the channel line in the control panel
containing the channel(s) in question. If for example you want
to exclude the channel on line 1 and line 4, the offer would begin
with #chanX:1,4
Note: Use only one
modifier per offer, DO NOT place both #chan: and #chanX: in the same
offer! It is acceptable to include BOTH a #chan type modifier AND
#random in the same offer!
Template
Wizard
Dialog
that allows editing of templates that can control the way your offers
look when the offer is created through the Offer Wizard. Operation
of the Template Wizard is very similar to the Offer Wizard. There
are some additional "variables" that are needed by the
Template Wizard which are listed below. The "variables"
listed above are all also available for use with the Template
Wizard. You can create 3 different templates for
"Collection" type offers and 3 unique templates for use with
"Single File" type offers. Once you have made changes to
existing template, simply hit the "Save" button to be able to
use it in future Offer Wizard sessions.
*title
the
name of the collection or file
*fsize
the
file size of a single file trigger: [25.6k]
*Vcount
the
number of files listed in the CSV
*Fcount
the
files residing in a collection folder
TRIGGERS WINDOW
Allows
you to create and control triggers.. AT® handles up to 1500 triggers..
including your choice of 'single file', 'collection' or 'FServe' type
triggers. A trigger consists of several basic pieces of information. The
trigger ID (ie: !Scanmaster), trigger path (location to of file or folder
that is being triggered), CSV path (if trigger also offers a csv file),
description (ie: BigCenterfold [547/547]). AT® also supports ecsvs
for collections like PhotoShoot, the request for this type of
collection must include the \pathname\filename details within the
trigger structure.
Trigger
Popup Menu
An
Trigger popup menu is available by right clicking in the Trigger
window.. Choices include New, Edit, Delete, View, Tools, Offer Wiz, in
addition to Utilities and control of the Trigger window settings
(described later in this document).
New
There
are 3 types of triggers, 'single file', 'collection' and 'FServe' style.
When selecting
NEW TRIGGER WIZARD to
create a trigger.. choose the type of trigger being created from the
choices in the popup menu..
Single File,
Collection or
FServe,
or use the
Multiple Folders that
allows you to create a trigger for each folder in a root folder in an
automated fashion.
Note:
Triggers created from a recognized CD-ROM or Zip/Jaz drive within your
system will result in a prompt for the Volume ID.
Do NOT include CD or Zip/Jaz in your volume identities, the
script will maintain that information for you.
Include only an identifying factor such as A1 or 001 (for
example).
Once the
type of trigger is determined, a dialog box will appear prompting you
for information to complete the trigger. The prompts, in most cases,
will include a default value. Below are descriptions of the process for
the 3 different trigger types:
Single
File Triggers
Creation
of a 'single file' type trigger involves using the directory dialog to
find the file to be triggered, naming the trigger (if you select
sdc99_195.zip as the file, the default trigger name will be
!sdc99_195), and then giving a description of the file (if you choose
to make it appear in the triglist.txt file).
You can choose to create one single file trigger or many with
the trigger selection dialog
Collection
Trigger
Creating
'collection' type triggers is very similar, including selecting the
folder that files will be sent from, entering a trigger name (i.e. !Scanmaster),
choosing the corresponding .CSV file if applicable, and then a
description.
One
Folder
Choose
the folder you wish to trigger, if "Removable media" is
involved, you will also be prompted for the "Volume ID" of
the disk
Multiple
Folders
Automated
process to create 'collection' type triggers. Process is the same as One
Folder above,
except you choose a root folder that contains the folders you want to
trigger. Allows quick
creation of triggers, one after another. The script will search the
folder chosen for collections that have not been triggered previously.
If the media being triggered is removable, AT® will prompt for
a volume ID. Selecting VOLUME
TRIGGER causes a single trigger to be created for the
volume, first choose the folders on the removable drive that you want
to appear in your trigger list, then press VOLUME TRIGGER to
store the folders and create the trigger.
FServe
Trigger
Creation
of an 'FServe' trigger consist of choosing the root folder you desire
to make available to users, entering a trigger name, folder path,
description and selection of a 'welcome.txt' file if you desire
Create
Folder
Method
to create a needed folder without having to open Explorer
Delete
Remove
a trigger. If options are
chosen in the AT options area, it is also possible to be prompted to
delete the actual file (single file triggers only) making it easy to
maintain a zip collection of single files are daily distribution
View
ACDsee
AT makes easy access to your collections, selecting ACDsee will cause
the collection contained within the trigger to be sent to ACDsee and
synched so that any new files added are shown by the viewer.
Folder
Details
Displays
all files currently residing in the folder represented by the trigger.
CSV
Details
Displays
the contents of the CSV file represented by the trigger.
Tools
Leech
If you have AutoLeech® 99 installed in mIRC, this selection allows
you to easily start a new leech session for the folder and csv listed
in the trigger details.
Clipboard
This
selection copies the trigger ID to the clipboard to make it easier to
display a trigger in the channel.
Offer
Wiz
Works
as described under Offer
Window section.
With the following exceptions:
The Offer
window need not be open.. and the choice of the 'target trigger' is made
by highlighting the trigger line to be offered.
Note:
If a trigger is turned off and someone requests it.. they will be
notified that the scan is not available at the moment.
All triggers have a limiting routine to determine how many files
one individual may receive at any time.. You can modify that number from
the Control Panel. Max DCC sends is a function of mIRC, you can control
the total number of sends by clicking on DCC icon and choosing the
'Options' branch, entry of the maximum is near the bottom of the box.
Utilities
Update
Triggers Lists
All
Trigger Lists:
Updates all 4 trigger lists
Active Triggers List:
Updates only the Active Trigger List
Single/Collection Trigger Lists:
Updates both the Single and Collection Trigger Lists
Removable Triggers List:
Updates the Trigger List for your removable type triggers
Verify
CSV Links/Counters
Fixed
Disks:
Searches all FIXED disk based CSV links to be certain the file exists.
Very useful when using a collection manager (like PicCheck or
Hunter) that will remove all superseded csv files from the CSV folder.
When that purging is done.. run this utility within AT® and
allow the system to help you replace the deleted CSVs with the most
recent. This utility also looks for descriptions where the counter
information ( i.e.: Scanmaster [1000/1000] ) may need to be changed
and prompts you to accept the new counter data.
Zip/Jaz:
Same process as above, but prompts for the removable media Volume ID
that you want to check, useful for zip and jaz drives with changing
collections.
Verify
FIXED Folder/File Links
Searches
all FIXED disk based 'single file' and 'collection' triggers for a
valid path to the file or folder being triggered.
If the link is nonexistent, then you are prompted to find a new
path, delete the trigger in question or skip the trigger.
Rename
Volume ID
Prompts
for the ID of the volume to be renamed and the new ID, then updates
the trigger database.
Delete
Volume ID
Prompts
for the ID of the volume to be deleted and then updates the trigger
database.
Find
Trigger Location
Allows
entry of a trigger ID or a portion of it and searches the trigger
database for a match and then highlights the match in the Trigger
window.
Window
Sort Type
Allows
you to choose from several options for sorting the Trigger window.
Triggers
Trigger ID: !Scanmaster Default
Date
trigger modified date
Reference
trigger line number
Drive letter
path of trigger
Type
Single file, collection & FServe
Status
on, off
Hits
number of times the trigger has been requested
Description
trigger description
COUNTER
LIST
View
details of trigger details. Items
like total sends, average sends, and number of bytes sent per
hour/day/week
OPTIONS
The
Options dialog consists of several pages of option choices.
Each with a specific category and itemized below:
Default
Folder Options
'Single
File' Default Folder
Choose path to BEGIN file searches
'Collection' Default Folder
Choose path to BEGIN folder searches
Ongoing CSV Default Folder
Choose path to BEGIN Ongoing CSV file searches
Finished
CSV Default Folder
Choose
location to BEGIN its Finished CSV file search
Event
Messages
Permits
editing of messages returned to users hitting your triggers. Most event messages can be edited. Note: this process requires a knowledge of mIRC in some
situations, edit carefully.
'File
Sent' Message Options
Select
file type to edit
'File
Sent' Notice status
allows
you to turn ON/OFF messages following successful completion to person
requesting a file, to notify them it arrived!
Edit
'File Sent' message for File Type
This
feature allows you to easily edit the message sent following
completion of the following file types: .jpg, .zip, .csv, .txt, .wav,
other
Note:
an understanding of mIRC syntax is most helpful in changing
these messages
Hogger
Alarm Options
The
term hogger.. refers to someone that is attempting to obtaining more
sends per person than you have allowed!
Audible
Hogger Alarm
Check
whether play a wav on your machine when someone is hogging.
Select
Wav Path
Choice
of which wav to play when a person hogs from you. Default: druman.wav
.. thanks Klipto!
Edit
Hogger Message
Allows
you to modify the message that the hogger receives to inform them they
are hogging!
Miscellaneous
Optional
Text Editor
Allows
you to use a custom text editor for some functions within AutoTRIG®.
Default editor is notepad.
Enable
ACDsee viewer
When
checked allows AT to display an ACDsee selection in the trigger window
menu under VIEW.
When selected, ACDsee will be invoked and the scans within
the folder represented by the trigger will be displayed by ACDsee.
Optional
text colors
Changes
some of the colors in AT® displays to accommodate some users who
prefer dark backgrounds in their list boxes.
No
AT® logo on connection
Mutes
display of the AT® logo window
Mute
"away" messages
Mutes
messages returned by other users from their away scripts.
Mute
"Thank you" messages
Mutes
messages returned by other users from their AG scripts.
Non-Counted
File Types/Folder Names
Non-Counted
File Types
Input the
extension of any file types that you DO NOT want AutoTRIG to count
when calculating the number of files in a collection or folder. (ie:
*.csv, *.txt, *.ion, *.db)
Non-Counted
Folder Names
Input the
names of any folders that contain files you DO NOT want AutoTRIG
to count when calculating the number of files in a collection or
folder. (ie: backup, unknown, bad)
Offers
Options
Offers
quantity
Input
the number of offers (max: up to 99 offers) Default at setup 20
Display
of trigger color in offer
Choice
of colors for your triggers can be selected from a dropdown box,
including transparent which allows you to completely control the
coloring in an offer
Audible
Offers Notices
Check
whether play a wav on your machine when an offer is displayed to the
channel to make you aware that you are advertising again.
Choice of which wav to play when displaying an offer.
Setup default: test.wav
Offer
deletion menu options
Delete
"Single Trigger" w/Offer
Displays
the option to delete both the offer and an associated trigger
Delete
associated file
Displays
the option to delete the offer, an associated trigger and the file
attached to the trigger.
Removable
Disk Support
Allows
selection of drives in your system to be recognized by the script as
CD-ROM and Zip/Jaz type drives. The
important of this option comes in AutoTRIG® knowing when a trigger is
built from a CD-ROM drive that it must maintain a volume identity (ie:
CD_01). When drives are
properly selected the system will automatically prompt for this volume
id during the trigger creation process.
Triggers created from Zip/Jaz drives will also result in the
volume id prompt.
Note:
placing a CD in any recognized CD-ROM drive will result in the
collection being found. It
is NOT required that the CD be placed in the same drive in which its
trigger was built. By
placing the Volume ID in the Control Panel area for CD's and Zip/Jaz's..
updated trigger lists will accurately reflect the volumes you identify
as being on-line.
CD-ROM
Drives
Input ALL
drives that triggers might be accessed from that represent CD-ROMs.
(maximum 6
drives)
Zip/Jaz
Drives
Input ALL
drives that triggers might be accessed from that represent Zip/Jaz's.
(Maximum 2
drives)
Note:
the input for these two options should be the drive letters involved
ONLY! For example if you
have 3 CDROM drives, D: E: G:, then your input should be DEG
Restriction
Classes
Preferred/General/Restricted/Banned
User Setup
This area allows you to set separate wait times for
Preferred as well as General users.
By having 2 classes of users you can define parameters for
each. Presumably those
you select for Preferred status will have shorter wait times and fewer
restrictions than the 'General' user category. Preferred users must be defined, and is accomplished by
right clicking on their nick and choosing Preferred from the AT® User
List selection. General
refers to all other users. The
Restricted user area can be used for a reverse type situation (to
single out users for fewer privileges).
You can also choose to 'Ban' a user from using your triggers.
Again right click on the nick and choose the Banned selection
under AT® User List. Anytime
a user is refused access to your triggers because of restrictions or
being Banned, the standard 'Triggers Off' message will be sent to that
user individually!
Enable
(Enforce) class
Turns
on the restrictions you have chosen for the Preferred and/or Regular
user categories when the box is checked while viewing a particular
class. Or enforces the
Banned function.
Include
OPs
The
same as giving every @OP on any channel you are in Preferred status. The only exception to the rule.. an @OP that you have Banned from
your triggers.
Include
Voices
The same
as giving every +Voice on any channel you are in Preferred status. The only exception to the rule.. a +Voice that you have Banned
from your triggers.
Wait
Seconds
Number
seconds following the completion of a send that a user is placed on CTCP
Ignore. As DCC Trigger Clients become '~Ax~' compliant,
this information will be transferred to the client to control its
requests.
Time
Limit
Sets a time
limit that an individual leecher can leech from your AT® server
before a required time out (a rest period in which all requests from
that individual are ignored). The intent is to prevent a leecher from
dominating your server. Input allows for the time limit in minutes, the rest period
in minutes.
Send
Limit
Sets a sends
limit that an individual leecher can leech from your AT® server
before a required time out (a rest period in which all requests from
that individual are ignored). The intent is to prevent a leecher from
dominating your server. The input allows for the number of sends, the rest period
in minutes.
Max
send CPS
Available
only if using mIRC 5.71-5.82. Enter
a number results in the max speed of sends to that class matching the
number you enter. Note:
entering a zero, results in no limit being imposed! mIRC
5.9 is limiting overall bandwidth usage as opposed to individual file
transmissions. For compatibility, the CPS option will remain in
AT®.
Restriction
Options
Ignore
'Guest Nick' Restriction
Restricts
use of triggers by users with a GUESTxxxx nick. If the option is ON,
and a user with a Guest Nick makes a request of your triggers, they
will receive a polite message stating your policy.. sends will not
occur!
Ignore
'Away/AFK' Restriction
Restricts
use of triggers by someone that has "away" or "afk"
in their nick. If the option is ON, and someone with either of these
designations in their nick makes a request of your triggers, they will
receive a polite message stating your policy.. Sends will not occur!
Common
Channel Requests Only
Restricts
the use of your triggers to users that are currently sharing a channel
with you. If you select
the channel restriction option, any trigger requests from outside your
channel(s) will be replied to with a polite message stating your
policy.. Sends will not occur!
Annoyance
Restriction Options
There are five annoying areas AT® can monitor, if any of
the chosen areas result in an infraction 5 times within 10 minutes,
then an optional rest period is imposed on the user committing the
annoyances. Annoying
options include:
1)
Missing file requests
2) Mount requests
3) Invalid Trig requests
4) Trigger Down requests
5) Failed sends
Speed
Check Options
SpeedCheck
will watch the speeds of sends to leechers, when a send is below your
predetermined threshold, the routine will terminate the send and
notify the user of the slow speed problem!
Choose
SpeedCheck status
Enable/Disable
the SpeedChecking process
Change
Threshold Level
determines
the speed (in cps) the routine will terminate a send.
Choices: 1 - 9999
Change
Checks/Send
determines
the number of checks to be made on a send before determining the speed
is too slow. Choices: 1 through 10
Change
Checks Separation
determines
time period (in seconds) between each of the above checks. Choices: 15
- 60 seconds
Scanfinder®/Protected
Triggers
ScanFInder®
link
Allows
you to create a link between AT® 99 and ScanFinder®, please note
SF® version must be 2.2 or greater for link to function.
The link allows another user to request a ScanFinder® trigger
list from your collection. The
user would send a normal trigger request in the following format /ctcp
yournick !atsf <model name>. AT® 99 then passes the request
to ScanFinder® which creates a list of scans you have that match the
<model name> info in the trigger sent. The list created by SF®
is then sent to the person requesting, via dcc send.
The list is created in a format that allows the user to then
request the scans from your triggers in AT® 99.
The
button in the ScanFinder® option area allows you to tell AT® 99
where SF® is located.
Protected
triggers
Allows
protection of up to 40
triggers from AT® intervention. Allowing other scripts to have access
to any of the protected triggers. Useful when using other scripts such
as @CSVSearch.
Trigger
Options
Collection
CSV Support
Allows
you to locate the csv that is associated with a collection type
trigger. Using this
method.. one trigger line (reference) handles BOTH the collection and
the csv! The user can use
a collection trigger ID PLUS .CSV to obtain the associated CSV file.
Search
SUB-folders
Allows AT® to search any sub-folders that exist under a
chosen folder for triggers.
Search
D/L for missing
Designed
for those offering collection triggers to receive the current file
from a scanner, and be able to offer as part of the collection before
it is moved to the collection folder.
Note:
This option presents something of a security risk.
IF you were to receive in your 'download' folder a private
file, and someone was making a collection request.. And knew the
filename! The private
file could be caused to sent to the requesting user.
THIS IS ONLY TRUE OF FILES IN YOUR mIRC DOWNLOAD FOLDER.
If wary of such action, then leave this option unchecked!!
Trigger
AND File deletion
Option to
allow the removal of both a trigger and its associated file when
deleting. The option was
added several versions ago to allow those who trigger many single file
triggers an easy way to remove both he trigger and file (assuming a
duplicate file was used for the trigger).
By default this option is OFF!
Note:
if choosing to delete files along with triggers, the file will
actually be moved to a folder under mIRC named Recycle.
Any deleted files can be recovered from that folder by using
Explorer or another file manager.
ReSend
Failed Sends
Option to
re-send any incomplete transfers automatically.
View
Hits
Status
Window
Allows to
see all hits and the results of the hit in your status window.
AT®Hits
See the
same information as the status window option.. but removes the
information from status window and places in separate custom window
for those with already busy status windows.
Single
Description Default
When
creating a single file type trigger, this selection will cause one of
three possible default items to be inserted into the edit box. 1) The
filename of the file being triggered
2) The filename PLUS the size of the file in kilobytes
3) the size of the file being triggered in kilobytes.
Or you can choose no default!
Collection
Description Default
When
creating a collection type trigger, this selection will cause one of
five possible default items to be inserted into the edit box.
1) The name of folder being triggered
2) the CD Volume AND folder name
3) the folder name AND the number of non-csv and non-txt files in
the folder 4) the CD Volume
AND folder name AND the number of non-csv and non-txt files in the
folder 5) the name of the CSV file associated with the
triggered folder. Or you
can choose no default!
Connection
Type/Speed
Choose the
type of internet connection you are using.
Helps other users know what speeds you are capable of producing.
Active
Nick Color
Highlights
nicks (in the nick list) that are currently receiving transfers from
your server in a color of your choice.
Trigger.txt
Options
Trigger
List Nick
Input the
nick you want to appear in your trigger list.
It will be used in the actual trigger shown within the
trigger.txt list (i.e.: /ctcp TomTerrific !Scanmaster).
There is now an option to have AT® change the nick in the list
to reflect your current irc nick.
Each time your nick changes.. the list will be updated
automatically.
Trigger
List File
Input the
filename you want for your trigger list.
The default is trigger.txt, please change to personalize it and
avoid users receiving the same file name from multiple trigger
providers.
Trigger
List Sort
Choose
sort method you like for trigger.txt list. Choices:
Date, Description, and Triggers
Custom
header and footer lines
There is
now room for five lines of text in both the header and footer sections
of all three trigger lists
Offers
and Triggers Window Settings
Screen/Font
Options
Save
CURRENT window position: after you have sized and position the Offers or
Triggers window to suit your situation, simply choose this option to
save the size and location information.
Screen
Location
Choice of
location for offer or trigger windows within mIRC window or the desktop.
Select
Window Font
Select the
name and size of the windows font you want to appear in both the Offers
and Triggers windows.
Desktop Status
Choice of location for offer or trigger windows within mIRC
window or the desktop.
Backup
& Restore
Backup
Each time
you invoke mIRC, an automatic backup will be made of the AT® data
files. The script will maintain a 3 separate sets of backups. As a new
set is created, the oldest will be removed from the cycle.
Restore
If the AT®
detects corrupt data, it will prompt the user to select for one of the 3
sets of backups maintained. Listing the date and time of the backups.
User can invoke a restore on their own by using the Restore button in
the Utility area of the main AT menu.
Known
Issues and problems
all
mIRC versions
Unable to dcc
send files. This is not a bug in either mIRC or AT® 99.
The most likely cause is the 'local host' box becoming UNCHECKED in
mIRC options under local info tab. Solution:
disconnect from irc, check the local host box and then reconnect.
This will cause the local host info to be properly loaded.. And dcc
sends should now work!
The first
time the trigger window is opened on a fresh starting of mIRC, a blank
window may appear. Closing the window and requesting the window again will
give the correct results. Gold
stars to anyone that can figure it out!
Status window
error message: '$dll identifier invalid' means prior to installation, the
DLL box under mIRC options | general | lock was not UNCHECKED.
That must be done.
When creating an
fserve trigger be aware that mIRC seems to error when the path of the
welcome file contains a space. Anyone with knowledge for a work around to
this problem, please e-mail me! Thanks
Nemesis, for the fix!
mIRC
5.71 version
The version
required several changes in AT to satisfy some procedural issues, no known
"BUGS" as yet
mIRC
5.7 version
No known AT
issues, many previous problems resolved
mIRC
5.61 version
There is a
bug in mIRC 5.61 that may be related to only my setup.
When clicking on channel icons in the mIRC taskbar, when the name
of the channel is longer than the icon can hold.. I get a page fault error
and mIRC dies. The author of
mIRC has not been able to duplicate my problem, thus no fix is available. I believe the problem is related to a new routine in mIRC
that displays the long channel names in a tool tip like box.
mIRC
5.6 version
The most
common complaint concerning AT with 5.6 is that dcc resumes many times do
not restart or take forever to restart.
Be aware this is not a function of AT.. It is a known bug in mIRC
5.6. (Resolved in mIRC 5.61)
Known bug
within mIRC 5.6 prevents the proper display of drive space available in
some situations.
|