Joined: 10 Mar 2007
|First we would like to give thanks to the people who's scripts and/or ideas were used for the bot:
Oz, Cherokee, LoneStar, Mind Dagger, The Bounty Hunter, SupG, Dynarri, Alexio, Xide, Phx, Rincrast, Voltron, Traitor, and Ender.
We used bits and pieces and / or public scripts and / or ideas for a lot of the early stages of the Bot.
This has been a work in progress for more than a year now.
Mind Dagger, The Bounty Hunter, and LoneStar all directly contributed to this at one time or another.
Thanks to Misbehavin for testing and debugging as well.
This set of scripts takes some time to learn and get used to. Once you get comfortable with it you will better understand its potential.
Unzip the MOMBot.zip file. Directory setup is vital to the bot use. The folder structure should look like this:
The __mom_bot.cts file can be placed and run anywhere. (Personally I leave it in my script directory). The MomBot Folder MUST be inside the TWX folder.
Prior to running the script you should ensure that your settings for user name, password and game letter are set up in the TWX setup. Now run the __mom_bot.cts script. You will be prompted for a name. This name IS case sensitive. After you start the bot will grab specific game information ie.. ship info, game settings, ship settings, stardock and class 0's if in database. It will quickly exit and re-enter the game.
All these settings can be changed later by accessing the preferences menu by pressing TAB-~
You are now ready to use the bot. For other users to login to the Bot all they have to do is send a corporate memo. Nothing else is required. This method has more security than the hail / ss method and is also easier.
2. Some of the bot features:
Self commands can be accessed using the > key or the up arrow key. For example. >citkill on
would fire up the citkill script (Must be at citadel). You can access which commands are available by doing >? or >help at the command prompt.
The self command prompt keeps a history of the last 100 commands entered. You can access the history by pressing the UP arrow once for each step backwards.
SWATH users: The advanced command prompt will not work with SWATH, because the up arrow is already mapped by SWATH. Also, SWATH does not render the ANSI correctly for the history. In order to use the bot and have it display correctly, go to the preferences menu (TAB-~) and change the prompt to SWATH prompt. I suggest using ZOC or some other terminal program to get all the benefits of the bot.
You can access many of the bot commands by using predefined hot keys. The hot keys can be accessed by pressing >help or >? and are as follows:
I will further document each command at a later time.
<TAB-K> Auto Kill From citadel, the bot will fire up citkill. If you are at the command menu it will attempt to kill any non-corpie. If in Fed it will NOT attack Federals or any fed safe player. It also will avoid empty ships and aliens.
<TAB-C> Auto Capture TAB-C does the same but captures instead of kills.
<TAB-A> Auto Capture Alien Captures alien ships if ship statistics are in bot file. You can add an alien ship to bot file if you are in the ship and use >storeship.
<TAB-TAB> Stop Current Mode Sets current bot mode to general. Kills current bot mode.
<TAB-R> Auto Refurb If at class 0 or class 9 port, will buy as many shields and fighters as possible very quickly.
<TAB-D> Dock Macros If at Stardock prompt, it will load Dynarri's Dock Kit menu.
<TAB-S> Surround Surrounds sector.
<TAB-H> Holo-Torp Holoscans and fires photon at non-corpies.
<TAB-X> Exit Enter Exit and Enters game quickly - must have password defined.
<TAB-M> Mow Mow - accessible from stardock, corp, computer, terra, and command prompt.
<TAB-T> Terra Macros If at Terra prompt, it will load Terra Kit menu.
<TAB-F> Fast Foton Starts/Ends Planet Foton.
<TAB-P> Planet Macros If at Planet prompt, it will load Psi's Planet Macros.
<TAB-Z> Clear Sector Clears Sector of all armids and limpets using exit/enters.
<TAB-Q> Quick Script Quick Script Loading Menu
<TAB-~> Preferences Preferences Menu
[SCRIPT HOT KEYS]
If you are going to use script hot keys, in your TWX directory you will need the following file: _MOM_HOTKEYSCRIPTS.TXT This file allows you to set paths for quick script loading. The file should be formatted something like this on each line:
[path] [script name]
scripts/MOM/MOM_UnlimitedGridder2_07.ts ""UNLIM GRIDDER""
scripts/MOM/MOM_LoginKiller.ts ""LOGIN KILLER""
scripts/MOM/MOM_PlanetGridder1_25.ts ""PLANET GRIDDER""
scripts/MOM/World_Planet_Stripper.ts ""WORLD PLANET STRIPPER""
scripts/2_WorldTrade.ts ""WORLD TRADE""
scripts/MOM/phx_SectorList.ts ""PHX SECTOR LIST""
scripts/MOM/MOM_GridClearing1_5.ts ""LIMP GRID""
You can list a total of 10 scripts in this way. This is NOT the same as adding a command to the bot. This is simply adding access to external scripts. This will number them accordingly 1, 2, 3 ect... Tab-Q will show a list menu of the scripts, but you can fire it off each directly by TAB-1, TAB-2, TAB-3...etc.
Corpies can access each of the commands by subspace calls. For example, if my bot name is jack. a corpie could send on subspace: "jack citkill on" and that would fire up my citkill (assuming you logged in already).
You can get a list of the commands and modes available by doing either >help or >? or those commands on subspace by doing 'botname help or 'botname ?
[ADDING NEW COMMANDS/MODES/DAEMONS]
This is a important part of the bot features. Do you have a favorite script that you want to access through the bot? Well, now you can add in your own bot commands WITHOUT editing the source code of the bot. Compile the script and re-name the file to the name of the command you want.
Example: You have your own tri-conn script. You compile it and rename it Tricon.cts. Place that file in the modes directory under the Cashing sub. Then you can call the command through the bot. You do not have to restart the bot after adding in a script module. Just simply call it using >tricon or 'jack tricon
An example of turning a standalone script into a bot script can be found in the MomBot directory called StripExample.ts
Here are a list of many of the bot variables that can be accessed by loadVar:
$user_command_line The entire command line entered by user. Example: "citkill on" $unlimitedGame TRUE/FALSE whether bot is loaded in is unlimited turns or not.
$parm1 The first parameter of the command line. In above example: "on" $bot_turn_limit Turn limit bot user has entered.
$parm2 and etc.... $password Password as entered by user.
$parm3 $mbbs TRUE/FALSE whether bot is loaded in MBBS game.
$parm4 $ptradesetting Planet trade percent.
$parm5 $port_max Port maximum in game.
$parm6 $steal_factor Steal factor
$parm7 $rob_factor Rob factor
$parm8 $multiple_photons TRUE/FALSE whether game bot is loaded in allows multiple photon firing.
$bot_name The user's bot name.
$rylos Rylos sector As entered by bot user (variable r)
$alpha_centauri Alpha Centauri Sector As entered by bot user (variable a)
$stardock Stardock Sector As entered by bot user (variable s)
$backdoor Stardock Backdoor Sector As entered by bot user (variable b)
$home_sector Home sector As entered by bot user (variable h)
It is important to note to scripters that the location variables (r,a,s,b, and h) can be used in the command line and are automatically translated into the sector numbers that are defined for them. If you want to use those variable letters in your bot command, you will need to grab them using Getword or some other method directly from the $command_user_line. The translation only happens to the $parmx variables.
The bot and all the modules that come with it use Sector Parameters. It uses the following Parameters:
$FIGSEC - TRUE/FALSE whether or not a sector has your fighter in it.
$LIMPSEC - TRUE/FALSE whether or not a sector has your limpet in it.
$MINESEC - TRUE/FALSE whether or not a sector has your armid mine in it.
Feel free to contact Mind Dagger at icq: 228-626-313 or The Bounty Hunter at icq: 21-316-991 if you have any questions or comments.
|Mind ()ver Matter Bot 3.0954
|| 966.49 KB
|| 2295 Time(s)