Category : Communication (modem) tools and utilities
Archive   : TLXTW108.ZIP
Filename : SCRIPTS.DOC

Output of file : SCRIPTS.DOC contained in archive : TLXTW108.ZIP

Telix 3.15/3.21 Scripts for Trade Wars 2002 v1.03(d)
version 1.08

Copyright (C) 1993 Crown Software


Phil Crown

326 Kinney Drive

Wylie, TX 75098-7725 U. S. A.


Crown Software makes no warranty of any kind.


Use of Telix(tm) for longer than 45 days without appropriate payment
to deltaComm Development for Telix is a violation of international
Copyright Law.

These scripts represent months of work and over 250K bytes of source
code. These scripts are not free. These scripts are Share Ware. If you
use them and find them useful you should register. Registration will
encourage the author to improve and upgrade the scripts for future public
release. Registration will remove the annoying please register messages.
This release is a fully functional version.


SALT and Telix are trademarks of deltaComm Development.
Trade Wars 2002 is a Martech Software, Inc (tm) product.


1. Hardware Requirements............................................1
2. Quick Start......................................................2
3. Environment Variables............................................3
4. Configuration File - Tlxtw.Cfg...................................4
5. .Ke files........................................................4
6. .Slc files.......................................................5
7. Operation........................................................6
8. Helpful Hints....................................................7
9. Special Notes....................................................7
10. Registration.....................................................7
11. Glossary.........................................................8

1. Hardware Requirements

If you can run Telix, you can run these scripts. You will need about
42K of memory above Telix to run the largest script. (Hint: the size
of the .Slc file is approximately how much memory it will need).

2. Quick Start

Unarchive the distribution archive. (TLXTW108.ARJ/ZIP/LZH, etc).

Copy Planet.Ke, Trader.Ke, Tlxtw.Cfg, and Tlxtwhlp.Txt to the same
directory as Telix.exe.

Copy all .Slc and .Slt files to Telix's script directory.

Set all the required Environment variables. See section 3 for Environment

Log into a game, load Trader.Ke, the keyboard definition file.
Hit Alt-F1 for a list of the keyboard assignments. (Alt-F1 requires, edit and compile Tlxtwhlp.slt as needed).

Run BUSTREAD.SLC (F10) in any sector with a port in it. The first time
it will ask to create a directory and you should respond "Y"es.

Download the CIM PORT report (*.prt file) using DNINTG.SLC (CTRL-D).

Run CRAI.SLC (Ctrl-C). This will read the .prt file and extract
information from it. It does not write to the .prt file, so you can use
the .prt and/or .sct files for other third party programs, too.

If you know the locations of all three Class 0 and the Class 9 (Stardock)
run BUSTREAD.SLC (F10) and enter these into the data file Manually, then
run MAJOR_LN.SLC (Shift-F1). If you don't know all, enter as many as you

Now the scripts are ready to run. Hit Alt-F1 for Help. Edit
Tlxtwhlp.Slt and recompile if you don't use

Run DNINTG (Ctrl-D), then CRAI (Ctrl-C) regularly (daily, every other
day, etc) until you build up a good data file.

If you don't read this entire file, some things may not work correctly.

Please see the Glossary for detailed descriptions of each script.

3. Environment Variables
The directory where Telix.exe resides should always be set in the
environment whether you use these scripts or not.

From the Dos Prompt type: Set Telix=C:\Telix

Three other environment variables must be set for these scripts.

F1, DR, and TEMP.

F1 - the path where scripts will make and store data files.
Ex: SET F1=C:\Telix\Twgames

DR - is the delay rate. If your modem is 9600 bps or faster, this can
be 2. if you running at 2400 bps, set this to 4 or higher. The
lower this number the faster Telix responds. But if it is to low,
Telix responds to quick. If your experiencing trouble at 2400 bps
such as scripts hanging try raising this number gradually until
the problem disappears, but I wouldn't recommend raising it higher
than 10. Unless you want to have to wait for a full second in
some places.
Ex: SET DR=4

TEMP - where temporary files are stored.
Ex: SET Temp=C:\Temp

Here is an example batch file which loads Telix.

@echo off
set f1=c:\games\traders
set dr=2
set temp=c:\temp
set f1=
set dr=

If any one of the above environment variables is not set, some scripts
will not function.

4. Configuration File - Tlxtw.Cfg
The file Tlxtw.cfg belongs in the same directory as Telix.exe. This
file holds default values that some of the scripts use.
It is a plain ASCII file that looks as follows. Each line should
begin at the first column and end with a Carriage Return/Line Feed.
If you decide to leave a default value out for some reason, at least
PUT A BLANK LINE IN ITS PLACE or some things will not work right.

An example tlxtw.cfg file looks like the following:


Row 1
Number of turns that trading scripts will stop trading. 10 means
that the trading scripts stop when you have 10 turns left.

Row 2
The second line is for Dnintg (Download Interrogation Reports, Ctrl-D)
script. Each letter represents default reports to grab. The above
grabs all available reports the script currently is capable of
grabbing. Reports that can be captured are:

R = Trader Rankings
O = List Corporations
N = Rank Corporations
G = Deployed Fighters
K = Deployed Mines
I = Ship Information
C = Corporate Planet Scan
E = Personal Planet Scan
T = Team Assets
V = View Game Status
X = Avoids
P = Port (CIM)
S = Sector (CIM)

This will be easy to see what each letter does once you run the
script. These are just defaults, you can still choose what to get
from the menu when the script runs.

Row 3, 4, and 5.
Third, Fourth and Fifth line are all for the DEPLOY_F (Deploy Fighters)
Third line is the default number of fighters to deploy.

Fourth line is whether the fighters should be Personal or
Corporate, followed by Defensive, Offensive, or Toll on the
same line.

Ex: PD Personal Defensive
CO Corporate Offensive
PT Personal Toll

Corporate , Offensive

Fifth line is whether to deploy in Major Space Lanes (MSL).
If it is blank the script will not deploy in MSL's. If you
want to deploy fighters in the Major space lanes put "MSL"
without quotes in row 5.

Row 6
Number to multiply experience by when calculating how may credits are
safe to rob.

Row 7
Number to divide experience by when calculating how many holds of
commodities are safe to steal.

Row 8
Minimum number of fighters to have possession of when attacking ports
with Attkport (Ctrl-A).

Row 9
Default strings to watch for when running Etherend (Ether probe
script, Ctrl-E)

A = Aliens
T = Traders
E = Federals
F = Ferrengi
M = Mines
P = Planets
C = Class 0 Ports
B = Beep when found

5. .Ke files
Key files allow you to redefine the keyboard. The default .key file is

(Note: the default extension is KEY, but I am using KE to help avoid
confusion between ANSI.KEY and AVATAR.KEY, etc, which Telix uses for
Terminal Emulations).

Copy Trader.Ke and Planet.Ke to the same directory as Telix.exe.
(Tlxtwhlp.txt also belongs in this directory).

Type Alt-K, R, L,, X.

After or has been loaded type Alt-F2 to switch
between the two.

You can optionally compile the below script for a quick and easy way to
initially load Trader.key.

// loadkey.slt
if (keyload("") > -1)
status_wind(" loaded", 10);
// end

To assign scripts to the keyboard, in Telix, type Alt-K, R, E, key to
edit, @name_of_script. Note the "@" precedes the name of the script, then
Enter and SAVE.

Ex: [type] Alt-K, R, E, F1, @Loadke, [Enter], [Space], S, Telix.key,
[Enter], X.

Now just hit F1 to load Trader.Ke after you load Telix.

Please read the Telix documentation for further information about Telix.

6. .Slc files
All .SLC files belong in the script directory. Here they are and a brief
description for each one. See the Glossary at the end of this file
for complete descriptions for these scripts.

Script name: Hot-Key ( Description:

DEPLOY_F.SLC F1 Deploys Corporate Toll fighters.
TRADE.SLC F2 Single trading (Equipment / Organics only).
SELL-BUY.SLC F3 Paired Ports (Equipment / Organics only).
SEL-STEL.SLC F4 Sell / steal cycle (Equipment only).
TRIPLE.SLC F5 Triple Paired Port Trading
SELSNHAG.SLC F7 Sell/steal cycle - non-haggling.
PRIME.SLC F8 Steals Equipment.
ROBCREDT.SLC F9 Robs credits.
BUSTREAD.SLC F10 Displays last time busted, menus, etc.
ATTKSHIP.SLC Alt-A Attacks other ships / deployed fighters.
CONFIG.SLC Alt-E Configures Tlxtw.cfg
TWIMAGE.SLC Alt-I Saves image of the screen in the game's directory.
DOS.SLC Alt-J Returns to Telix's directory after shelling.
MINE_DIS.SLC Alt-M Mine disruptors.
PHOTON.SLC Alt-P Launches Photon torpedoes.
DENSCAN.SLC Alt-S Upgraded density scanner. (also on keypad + )
FUEL.SLC F6 Steals Ore.
TRICRON.SLC Ctrl-T Tricron.
TLXTWHLP.SLC Alt-F1 On line help. (requires
LOADKE.SLC Alt-F2 Toggles between
CORPMEMO.SLC Alt-F8 non-CEO send messages to all members in one try
ATTKPORT.SLC Ctrl-A Attacks ports.
BBSNAME.SLC Ctrl-B Fills _entry_name variable (creates directory).
CRAI.SLC Ctrl-C Creates .dat file from .prt file.
DNINTG.SLC Ctrl-D Downloads .prt and/or .sct files.
ETHEREND.SLC Ctrl-E Etherprobes (reads text file of sector numbers).
GRIMY.SLC Ctrl-G Grimy Trader tracing.
CRSEPLOT.SLC Ctrl-P Turn counter / t-warp calculator.
BUSTED.SLC Alt-F10 Records sector and date when busted.
MAJOR_LN.SLC Shft-F1 Major Space Lane finder
HOWBADAM.SLC Shft-F2 How many holds / credits are safe to steal.
CUSGRIMY.SLC Shft-F3 Cuss Grimy Trader to lower alignment.
MOVE.SLC keypad . Move / Deploy / Scan
Script name: Hot-Key ( Description:

POPTRANS.SLC F1 Transwarp planet populator.
POPSTNRD.SLC F2 Standard warp planet populator.
MATLMOVE.SLC F3 Moves commodities between planets in same sector.
PLA_PO_M.SLC F4 Moves colonists between planets " " "
PLANET_D.SLC F5 Destroys planets for experience.
CEYLAD.SLC F10 Corporate Megaholds
POP_OPT.SLC Alt-O Disperse colonists on full planets.
PLANSHLD.SLC Ctrl-S Standard/Trans-warp planet shielder

7. Operation
Scripts create a separate directory under the path you enter in the F1
environment variable for each different BBS and/or game that you play.
The directory will be used to store data files that the scripts create
for each game.

The directory is named by the first eight characters of the name of the
BBS in the dialing directory. It doesn't matter if the name is less
than eight characters, though. Characters that are illegal in DOS
filenames are filtered out. They are ( ) space, * asterisk, + plus, .
period, / slash, and ? question mark. Any other illegal characters are
not checked for and should be changed by you manually in the dialing

The data files will be named by the first 3 characters in the dialing
directory for the BBS you call. This way there will be a separate
directory and data file for each BBS you call. For example, if you call
a BBS named Terminator, then the directory will be named \TERMINAT, and
the data file would be named TER.DAT. Quad C BBS would be named

If you're playing more than one game on the same bbs, then run
BBSNAME.SLC (Ctrl-B) after you finish the first game, and enter something
like termina2 or something to create a separate directory and data file
for that game. Remember to always enter the same name each time you log
into that particular game.

Using a status line is required. The status line will always show
which script is currently running, if any, which is very, very helpful
to avoid loading to many scripts at one time. Most scripts will
terminate automatically when its finished, but sometimes you may have
to abort one with the Esc key. Alt-8 toggles the status line on/off
in Telix. Some scripts will also display useful information on the
status line.

The easiest way to run a script is to assign it to a keyboard macro.
(Alt-K, R, E, key to edit). Make sure it begins with a @. Ex.
"@Bustread". and are included with scripts already
assigned with Alt-F1 for help, but you can reassign them anyway you like.
(Note: KEY files are being called .KE to avoid confusion with ANSI.KEY
and others that Telix uses for Terminal Emulations)

Scripts should be loaded while you're at the "Command [TL=" prompt,
except for GRIMY.SLC and TRICRON.SLC, which should be loaded while in the
"", and some of the planet operations scripts which should be
loaded while on the planet ("Planet command"). Scripts will tell you
if you are not at the correct prompt.

Trading scripts stop trading if you get busted or encounter a Ferrengi.

8. Helpful Hints
They will sell Ore but not buy it. This is intentional, to make scripts
run more in "automatic" mode.
About ships HOLDS.
When doing Planet operations ( holds should be EMPTY before
loading a script, except for PLANSHLD, which holds should be full of
Ore to begin.
All other times holds should be FULL, or as full as you want them to
be, but not empty before loading scripts, i.e trading.

The following two scripts do NOT require a Physic Probe.

This script is very good when you play good, or if
you're in a new game and are trying to build experience
fast. It haggles Org/Equipment at paired ports and
usually gets 1 or 2 exp. points each trade.

This script is just a single trading (as opposed to paired ports)


This is the only script that DOES require a Physic Probe.

Runs the sell/steal cycle for equipment only. sel-stel Haggles and
usually gets 2 or 5 exp. points. Requires a Physic-Probe.

Runs the sell/steal cycle for equipment only. selsnhag
Doesn't haggle, but is very fast. Very good for when
you don't need every little experience point. Turn off
ANSI (or leave it on) and let this RUN.

Sometimes if you try to download the CIM port and/or sector reports
(Ctrl-D or Ctrl-I) the game will kick you out to the BBS, to avoid
this move or plot a course into the ship's on board computer, and do a
[C]omputer, [R]eport, [sector #], first to avoid being involuntarily
kicked out.

Until you build up a good data file, you should run DNINTG, and then
CRAI, regularly. Every day or every other day, etc.

They will run with ANSI on or off, and will turn ANSI off when
necessary, (ie, downloading CIM reports or downloading the Unexplored
Sectors report for the etherprobing script to read).

Some scripts has several nested loops, so to get out of it you may have
to press Escape two or three times.

10. Special Notes
ETHEREND - etherprobes sectors read from a text file.

You will need a file called EDIT that will accept parameters from the
command line in your path which loads your text editor. The following
batch file will work if you don't already have it. Replace q with the
name of your text editor.

@echo off
q %1 %2 %3 %4

TLXTWHLP.SLT - check the variable "help" in here if you don't use and enter your list program. Then recompile
this script with CS.exe which comes with Telix.
Ex: CS Tlxtwhlp

11. Registration
When you register Telix Trade wars Scripts you will receive the latest
version of the Scripts on disk without the registration encouragement
features and annoying delays.

Register Telix Trade wars Scripts. Only $10.00

Quantity Description Price/copy Total:

___ Telix Trade wars Scripts (latest version) $10.00 ______

___ disk 5.25" ___ 0.00 __0.00

___ disk 3.5" ___ 1.00 ______

Texas residents add State and Local Taxes: ______

Grand Total ______

Your Real Name:________________________________________________________


City, State, Zip:______________________________________________________

Phone # ( ) ___-____

BBS Name:_____________________ Data # ( ) ___-____





Send registrations to:

Phil Crown
326 Kinney Drive
Wylie, TX 75098-7725

I can also be contacted thru:

Phil Crown
Fidonet Telix Echo
Fidonet Trade wars Echo
Netmail Address 1:124/6106.105

Registration will entitle you to legally continue to use Telix Trade wars
beyond a reasonable evaluation period and qualify you for the upgrade
package at a considerably reduced rate and remove any annoying delays,
messages, or limitations.

If you have any questions about these scripts, leave me a message in
the Fido net Telix or Trade wars Echo, or NETmail.

10. Glossary

Attacks ports. Will not attack if you have less than the amount of
fighters defined in TLXTW.CFG.


Attacks other ships / deployed fighters.


This fills the _entry_name variable in SALT. _Entry_name is a SALT
variable that holds the name of the BBS from the dialing directory your
connected to.

This serves three purposes:

It will create directories to store data files for new games.

If you start Telix while already on line or for some other reason the
_entry_name variable wasn't passed during log on it will fill that

Another use for this is if you're playing in more than one game one the
same bbs, you'll need a separate directory to store data files. Before
you enter the second game, run this and enter a name to denote the
change. Always enter the same name each time you enter that particular

This script is normally called by other scripts, but it can be run
manually (Ctrl-B) if needed, as in the previous paragraph.


Normally this will be "called" by other scripts, but it can be run as a
stand alone if need be. It writes a data file with the sector #, port #,
and date as represented by the number of seconds since Jan. 1, 1970 when
you get busted.


Reads the .dat file, so all you have to do is warp into a sector and run
BUSTREAD to find the last time you were busted in that sector.
If the port busts have been cleared then the options to steal or rob
the port will appear in the display box. Port bust records are
cleared every 14 days in the game.

If the file major.lan exists in the game's directory, then the
display will show if the port is in a major space lane (MSL). If you
run this in a sector without a port, and the file major.lan exists
(MAJOR_LN, Shift-F1) it will show if that sector is in a major space

If the file Corp.dat exists in the game's directory, then an extra
option will appear in the display box. Corp.dat is an ASCII file
that you must create, it should contain your handle in the game
first, followed by your corp team members handles in a column format.
For example my corp.dat may look like this

Phil Crown
team member 1
team member 2
up to

This option will make keeping track of who's been busted where and
when effortless. Currently, this requires that the Corp member is
using TLXTW Scripts too, but I may try to support a generic format in
the future. All you have to do is choose to "R"eceive or "T"ransmit.
At the end of your turns for the day, run Bustread (F10) and choose
the Cor"p" option, then "T"ransmit Bust Control records to corp
members. When a corp member logs on, he runs "R"eceive Bust Control
records. Now, when you run Bustread or Denscan scripts, then it will
show if you or a corp member was busted in that sector last.

If you just want to see how this works, you can "T"ransmit the info
to yourself, then "R"eceive it. This serves no practical purpose
except for debugging.

Example of the display box:

³ Sector : 806 Class 9 Major Space Lane ³ - port, class, MSL
³ Busted 16 days 7 hours 42 minutes ago. (2x) ³ - your last bust/times
³ Corp 1 days 3 hours 49 minutes ago. ³ - corp member busted
³ All busts will be cleared in 12 days ³ - when busts cleared
³ Steal Ore - Equipment - Rob credits ³ - options
³ Sell/Steal Cycle Attack Port ³ - " "
³ ³
³ Density Scan ³ - " "
³ Look up a sector ³ - " "
³ Manually Enter a Sector and Port ³ - " "
³ Corp Bust Control Receive/Transmit ³ - Exchange Corp busts
³ ³ records
³ ¯ Finished ® ÄÙ ³
³ ³


Runs the Corporate Megaholds bug. Start on the planet while the ship
that has 0 holds is in the citadel. If ANSI is on, it will be turned
off after entering the Citadel.


Edits the file TLXTW.CFG, which should be in Telix's directory.
The .Cfg file holds the default options that some of the scripts will
use. They are:

Turn Protection
Default reports to gather with DNINTG (Download Interrogation Reports)
Number of fighters to deploy with DEPLOY_F
... whether they should be Personal, Corporate, Toll, etc...
... whether or not to deploy in the Major Space Lanes (MSL)
Number to multiply experience times when Robbing Credits
Number to divide experience by when stealing holds
Minimum fighters to have when Attacking Ports (ATTKPORT, Ctrl-A)
Default things to watch for when Ether Probing (Ctrl-E)

There are descriptions for each option when the script runs.


Allows non CEO Corporate members to send messages to all other corp
members by typing the message just one time.

The file corp.dat must exist in the game's directory. Corp.dat is
described with the description for BUSTREAD, (above).


Builds a data (.dat) file from the CIM port (.prt) report file. If
you're on line run DNINTG.SLC (Ctrl-D) first, then run this. If
you're off line, CRAI can be run still, but the .prt file must already

If this script is aborted before its finished running any busted ports
and Class 0 / Class 9 information may be lost! This is why CRAI
(Ctrl-C) makes a back up (.bak) copy of the data file first. If you
abort this script and have any busted ports and/or Class 0 / Class 9
information you want to keep, which is likely unless you've never been
busted, then drop to dos, change to the game's directory, copy the .bak
file to .dat before starting this again. This can be avoided by just
not aborting this script. It only takes a minute or two to run.

CRAI only reads the .prt file, so you can use the same .prt file for
other third party support programs that use it.

If this is run on line, and the Stardock's location is displayed when
viewing the game "Game Configuration and Status" ("V" from the Command
prompt) then it will record that sector in the data file automatically
if it is not already recorded.

Crai requires the use of the External DOS Command SORT.EXE


Pops up a box with the current sector, asks for a destination sector,
then counts turns and fuel needed to Twarp from current sector to a
destination and back to the current sector.


Call's the Grimy Trader a bad name, thus causing your alignment turn
negative. Load this at the "Command [TL" prompt and it will show
exactly what your alignment is at all times. If you load it in the
Tavern then it will only show how many points your alignment has gone
DENSCAN = ALT-S or keypad + (TRADER.KE)

Reads the .dat file, and will show what class port is in an adjacent
sector when doing a density scan if that sector is not unvisited, and if
busted then how many days ago.

If the locations of the three Class 0 and the Class 9 (Stardock) ports
are recorded in the .dat file, and you've run MAJOR_LN.SLC (Shft-F1),
then it will show if it is a major space lane or not. The word "Fed"
will appear when a fed is nearby.

Example of Upgraded Density Scan:

Relative Density Scan
Sector 487 ==> 180 ÍÄ Warps : 3 Class 3 SBB 10 days ago
Sector 927 ==> 0 ÍÄ Warps : 6 MSL
Sector 978 ==> 0 ÍÄ Warps : 6 MSL
Sector 796 ==> 489 Fed Warps : 1
Sector 460 ==> 100 ÍÄ Warps : 4 Class 2 BSB
Sector 705 ==> 100 ÍÄ Warps : 1 Class 6 BSS 2 corp member

If the file CORP.DAT exists in the game's directory this will show if
you or a corp member were busted in the adjacent sector last. See the
description for BUSTREAD for more on Corp.dat. In the above example,
I was busted in sector 487 10 days ago, and a corp member was busted
in sector 705 2 days ago. The corp member was busted after me, so it
is safe for me to trade at that port, since the corp member was busted
there last.


Deploys fighters. Doesn't deploy in Fedspace. The number of
fighters and the mode are defined in Tlxtw.cfg. As well as, whether
or not to deploy in the Major Space Lanes. Run Config.slc (Alt-E) or
edit Tlxtw.cfg with a text editor to change the default values.


Download Interrogation reports. Originally this was just to download
the CIM Port and Sector reports. Its been expanded to gather all
reports intended to be captured in a log file. If you choose to
download the CIM Port/Sector reports, they will also be captured in
the log file, but it also does an ASCII download for which you must
press Escape once after each ASCII download is finished. The default
reports to capture are in the configuration file, Tlxtw.cfg, but they
can be changed on the fly after the script is loaded.

Reports that can be captured are:

R = Trader Rankings
O = List Corporations
N = Rank Corporations
G = Deployed Fighters
K = Deployed Mines
I = Ship Information
C = Corporate Planet Scan
E = Personal Planet Scan
T = Team Assets
V = View Game Status
X = Avoids
P = Port (CIM)
S = Sector (CIM)


Fires ether probes. Reads sector numbers from a text file. The text
file usually an ascii download of the Unexplored sectors function of
the CRAI XXV on board computer, but it can be any file, just sector
numbers in a column will work.

If the file Ether.123 does not exist in the game's directory OR in in
the directory specified by the "Temp" environment variable, this
script will do an ASCII download to that directory. After the
download is finished, the script will call Edit.bat to edit the file
it just downloaded (ether.123). This first line in ether.123 should
row of ether.123 must contain only sector numbers. Trimming off the
bottom rows helps, but it not mandatory.

Edit should be a file that will accepts parameters from the command
line that loads a text editor. The following batch file will work,
Edit.bat Q %1

Replace Q with the name of your text editor.

You can choose to watch for Aliens, Traders, Mines, Planets, Ferrengi,
Class 0 ports, a combination, or nothing at all, however, "Probe
destroyed" is always watched for. If one of the above is seen, except
for Class 0 ports, the you'll have the option to dump the screen to a
file called Ether.img in the game's directory or continue firing
probes. If you don't respond within 10 seconds then the script
resumes firing probes.

If you choose to watch for Class 0 ports, when a probe enters a
sector with a Class 0 port, then that port will be added to the data
file automatically, if it is not already recorded.

When you run out of ether probes it will port at the StarDock and buy 25
more ether probes, providing you're in the same sector as SD and have
enough credits. If you don't have enough credits for 25 probes, it will
buy what you can afford.

A temporary file called Ether.tmp is written that holds a string that
represents the offset of the last sector read from the text file
(ether.123) so that if the script is aborted, then resumed it won't
shoot into sectors that its already done.

If you want to use a pre-existing text file of sectors, copy the file
you want to use to the directory specified in the "Temp" environment
variable and name it ETHER.123. Ex: d:\tmp\ether.123. The .dat file
makes a good list of sectors to shoot at after you've run out of
unexplored sectors. Cut out just the sector numbers and copy them to
a file called Ether.123 in the directory specified by the "Temp"
environment variable. You should delete all the files in the
temporary directory when you are finished.

If you want to use a "permanent" ether probe file, copy the file
Ether.123 to the game's directory. The script will search the game's
directory first, then the temporary directory. If Ether.123 is not
found in either directory then it will do an ASCII download of the
unexplored sectors.


Robs a port of Ore for T-warp or whatever. The port must have at least
at least the number of you holds that you want to steal on its docks.
If you get busted, BUSTED.SLC is called which records the port in the
data file.


Asks the Grimy Trader to trace another trader. You must enter enough
letters to match the trader being traced exactly right the first time
Grimy says "Do you mean ***?" Saves any info the Grimy Trader gives in
a capture file named Grimy.Txt in the game's directory.


How many holds / credits are safe to steal. Looks at your experience,
divides it by x, multiplies it by y, then prints the results on the
status line. x and y are listed in the configuration file, Tlxtw.cfg.
Run Alt-E or edit Tlxtw.cfg with a text editor to change the default


Toggles between and, the keyboard definition files. holds all the planet operations scripts, and holds
everything else. You can reassign the keyboard anyway you want to, and
even create new key files if you like.

MOVE = keypad . (TRADER.KE)

Move / Deploy / Scan. You have to enter a destination first. Single
step once. Then use this to single step the rest of the way,
deploying fighters and Upgraded Density Scanning each step of the


Finds the major space lanes and/or the closest port to buy fighters.
You must have the three Class 0 ports (Terra, Alpha Centuari, and Rylos)
and the Class 9 (Stardock) recorded in the .dat file and sorted by
sector number, ascending. This script will tell you if you don't have
all the ports and/or if they need to be sorted with CRAI.SLC.

If all three Class 0 ports or the Class 9 port are not in the dat file,
but you know their locations, run BUSTREAD.SLC (F10) and "M"anually
enter them into the data file. Then run this again.


Moves commodities between planets within the same sector. Make sure
your HOLDS ARE EMPTY when you start.


Launches mine disruptors into the sector you specify.


Launches a photon-torpedo into the sector you specify then enters the
sector begins the landing sequence and will Attack ONCE, then you're
on you're own. Doesn't actually do the invading. Just gets into the
sector fast. It will ask for a sector, a planet number, and how many
fighters to use. If you don't know the planet's number you want to
invade, just hit enter to skip it, then enter the amount of fighters.

This script will launch the photon, then print the elapsed wave time,
and the wave maximum duration on the status line, so you'll know how
much time you have left before the wave expires. Press escape or wait
10 seconds when the script is finished before loading another script.


Planet Destroyer - blows up planets for experience and fun. You must
belong to a Corporation for this to work. Its a good idea to belong to
a corp even if you're the only one in it. This script works best with
ANSI turned off. Its written to be run in the sector with the Stardock,
so when you run out of Genesis torps and/or atomic detonators it will
port and get some more. It asks for a planet number so that you don't
accidentally land on a populated planet (if there is one) and get blown
up yourself, or if you have a Planet Scanner. A planet does not have to
specified for it to run, unless there is more than one planet in the
sector or you have a planet scanner. Just enter the number of the
planet to land on or hit Enter to skip it. Escape to abort.


Standard/Trans warp planet shielder. FILL your holds with Ore.
This is the only script in that you must FILL your holds with
Ore first. The others should be loaded with holds EMPTY.

Start in the same sector as the planet is in, and have all Transwarp
beacon fighters in place, if you'll be using the T-warp mode. The
port that you buy the shields from must be a Class 0, Class 9 will
not work. To use the T-warp, the Class 0 must be Alpha Centuari or
Rylos, since you can't warp into Sol (Fedspace).
This script will not work if the planet is in the SAME sector as the
Class 0 port.

A simple keyboard macro can handle that though.
These are a couple that will work is there is more than one planet in
the same sector. For example, assign the first one to F7 and the
second one to F8 in

"LLPT C1500^MQL " ; 1500 is the number of Ship shields
"24^M C GT150^M" ; 24 is the planet's #, 150 is Planet shields.

To use these, enter the citadel, transfer all shields to the planet,
then hit F7 (first macro) to leave,leave,port,trade, buy
Then hit F8 (second macro) to land on planet 24,citadel,transfer
shields,to the planet, 150.

Then repeat, F7, F8, F7, F8, etc...


Moves colonists from one planet to another within the same sector. PUT
COLONISTS IN THE ORGANICS GROUP on the planet to take colonists from,
and make sure your HOLDS ARE EMPTY before you run this script.


Adjusts population to optimum levels in Ore and Equipment only.
It tries to put 1 million in each group. This is mostly for use on
overcrowded planets when you want to keep 1 million colonists in Ore for
the Q-Cannon.


Standard Warp Planet Populating script. Start in the same sector as the
planet. If you have a Planet Scanner or if there is more than one
planet in the sector to populate enter the Planet's number. Otherwise
leave it blank, or the script may hang.


Trans-warp Planet Populator (handles Evil ISS). Just set everything in
place (beacon fighters) like you were going to do it manually. Start in
the same sector as the planet(s) to populate with all cargo holds empty
and not on the planet. There is one restriction currently: The sector
near to Terra to T-warp to must be exactly two warps from Terra, which
it usually is anyway. This script will abort if there is a Fed in any
sector near Fedspace. Uses density scan, not Holo. When this script
runs, it will ask for a sector to T-warp to (that is the sector near
Terra). Then it will count the turns and how much ore is needed, next it
asks for a planet number to land on (leave this blank if you do not have
a planet scanner or there is only one planet in the sector or the script
will hang), where to pick up the fuel, choices are the same planet,
another planet in the same sector, or a port in the same sector as the
planet to populate, finally how many times to run. *IMPORTANT* I have
recently discovered a flaw in the logic this scripts uses. Any density
scan ending in 2, 3, 4, 7, 8, or 9 is a FED. Therefore, if a Fed is in
Sector #1 with Terra, and a beacon, the density scan may end in 0, thus
not registering as being a Fed. I found this out the hard way, i.e I
lost my Evil ISS.

I've adjusted this script so that it will abort if the density is
higher than 1089 or if it equals 490.
It works out as:
500 (Terra)
100 (Sol)
1 (beacon)
489 (The Fed that causes the problem)

The worst that should happen, is if there are a bunch of rookies
parked in Sector 1, or there is a density is higher than 1089 then
the script will abort.


Steals Equipment. If you get busted, BUSTED.SLC is called which records
the port in the data file.


Called by BUSTREAD when you choose to "R"eceive Bust Control Reports.
This currently requires both sides to use TLXTW Scripts, but I may
try to support a generic format in the future. You should never
have to run this manually.


Robs credits. Looks at your experience, divides it by x, the robs a
port of credits. x is defined in the configuration file, Tlxtw.cfg.
Run Config.slc (Alt-E), or edit Tlxtw.cfg with a text editor to
change the default value of x.

If you get busted, BUSTED.SLC is called which records the port in the
data file.


Runs the sell/steal cycle (Equipment only). This script requires a
Physic-Probe. If you run this script without a P-probe it will sell
the load of Equipment and abort. To run: get a load of equipment,
warp to a port buying equipment, have a P-probe equipped ship, hit
F4. The rest is automatic. It seems to work best if you steal/sell
in multiples of 5 or 10, i.e, only use it with 70, 85, ... 150 holds.
I haven't tested it a whole lot with other values.

If after the first three or four trades have gone by, and you
haven't hit 100.00% on any trade, abort the script with Escape, then
start it again. If you do this two or three times and you're still
haven't hit 100.00%, then the port probably doesn't have a best price
or the port is not buying at 100%.

You may have to "lay" on the escape for a second or two to get it to
abort. This is the best prompt to abort it at, but requires a little
bit of timing on your part;

"How many holds of Equipment to swipe? [150] 150
You start your droids loading the cargo and..."

The status line is updated after every trade. Status line legend:

100.00% ³ dif 18 ³ adj 0 ³ Best $ 9170 ³ 131/hold
³ ³ ³ ³ ³
³ ³ ³ ³ ³
³ ³ ³ ³ Average price/hold
³ ³ ³ Best price
³ ³ Price adjustment (multiple of holes)
³ Difference between port's original offer and current offer
Last P-Probe estimate

If you want to know more about how the 5 point sell/steal cycle
works, find the file TWTIPS1?.*. It should be available on any
quality Trade wars BBS.

If you get busted, BUSTED.SLC is called which records the port in the
data file.

However, if you get busted after aborting, then you'll have to run
BUSTED (Alt-F10) manually.


Paired port trading. Organics / Equipment only. Load this script when
the ship's holds are loaded with Organics or Equipment and you're READY
TO MOVE into the adjacent sector to sell. Do not move, but be ready to

Haggles and usually gets one or two experience points. This is a very
good script when you are beginning a new game.


Runs the steal/sell cycle and tries to haggle without a Physic probe.
If you have a P-probe run SEL-STEL (F4). This script should only be used
when you don't have a probe.

You must already have the equipment aboard your ship that you want to
sell/steal. It only works for equipment.

If you get busted, BUSTED.SLC is called which records the port in the
data file.


Uses to list a text file that shows the key assignments.
Tlxtwhlp.txt should be in the same directory as Telix.exe. If you
don't use then edit Tlxtwhlp.Slt and enter your viewing
program, then compile it with CS.exe which comes with Telix. Ex: CS


Single trading. Ports and haggles whatever you have or want to buy.
Doesn't buy Ore.


Plays TRI-CRON for 3 minutes or until the jackpot is won.


Trades three commodities at paired ports. One port is selling
two commodities and buying one and the other port is buying the two
and selling the opposite of the first port. Except for a Class 7 and
a Class 8/9, then one port is selling all three and the other port is
buying all three.

It works out as follows:

BBS 1 ³ BSB 2 ³ SBB 3 ³ SSS 7
SSB 4 ³ SBS 5 ³ BSS 6 ³ BBB 8 or 9

If you're lucky enough to find a pair of these; fill your holds, be
ready to move into the adjacent sector to sell, then just hit F5,
and the rest is automatic. The advantage of trading at a pair of
these is you have 6 chances of making experience points from haggling
prices, rather than the standard 4 at normal paired ports.

Saves an image of the screen in the game's own directory.

End of File

  3 Responses to “Category : Communication (modem) tools and utilities
Archive   : TLXTW108.ZIP
Filename : SCRIPTS.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: