Here are some of the changes I have made. There are some other smaller issues I forgot to log but trying to remember them. Yesterday was a busy day for me with the bot. I am not ready to release a new version yet but will do so soon. I will take a look at the qset command as well. As for the clear screen, that is just something you will just have to live with.

01-12-12 - Fixed issue where Xporting without turns would not display over ss until next command.
01-12-12 - Added options to surround before hkill and to turn off busted/msl prompts
01-12-12 - Fixed Bug where pgrid would hang if enemy cannon and mines were in target sector.
01-12-12 - Fixed issuer where MEGA, ROB, XPORT, and HOLO would hang if no turns left
01-12-12 - Exit Enter now reloads figs before exit.
12-20-11 - Removed all command. No longer needed due to team callin. Fixed issue with TOW.
12-18-11 - Added a corp command to Join/leave corp
12-17-11 - Fixed issue where BOT was not capturing StarDock on script startup.
12-12-11 - Fixes due to Public Release many changes made by multiple people.

Okay, but I'm curious exactly what causes that?

It's a swath thing. Does not happen when using ZOC. Only time it happens there is when you go to the preferences menu.

There is a problem with logout/logoff with cloak enabled on the new versions since the game only exits you to this menu:

==-- Trade Wars 2002 --==

T - Play Trade Wars 2002
I - Introduction & Help
S - View Game Settings
H - High scores
M - View Access Modes
X - Exit

Enter your choice:

It will successfully exit game and cloak, but since it doesn't go to the right menu it can try to auto relog and that could be bad
I did fixed mine by adding a second trigger so it now works on both 1.03 and 2.16 but some others might not know where or how to fix.

Maybe I need to stop using Swath, then. But I like the map.

I wish I had time to write my own helper...

When I start up an important game I run swath and zoc at the beginning. You can connect them both to twx at the same time. Then I run the SWATH ZTM for mapping features and then I had swath offline and only pull it up if I need to look for bubbles or something with the map.

When it comes to the new version of TW the bot is not very friendly. There are many issues there. I have not taken time to look at the newer versions yet. I would like to put the proper triggers in there for both versions but that will take some time.

No problem I am just trying to pass info as other people and I find them. All in all it is typically only a few triggers that need added to conform to both versions. But digging through roughly 11400 lines can be a little intimidating to some people

yes, I do need to do a line by line walk-through of the bot but as you said, with that many lines of code and following it area to area will take a while. but it will get done eventually. I do appreciate the feedback for other versions. That will get fixed eventually as well and it is nice to have a place where I can go back and look at everything.

Just an FYI for people following this. Until I stop supporting the bot I am only going to release compiled versions of the bot. I went back to the last version released by MD, Lone, and myself and did some comparisons to current versions and there were a lot of functions that were broke. (not saying that version was perfect).

I know some of you will not like this, but it is up to you if you want to use the new version or not. If you have changes that you made to "Your" version and would like them implemented hit me up on ICQ, message me here or post in this thread and I will put them in. This will eliminate to many "rogue" versions or versions that are not working properly from being distributed.

Hmm, yeah I don't know if I will use a version that doesn't include the source. Probably not.

One thing I always add to mombot is extra user variables. So instead of just x, i have a bunch of other ship variables. I also define a bunch of sector variables so i can do stuff like this for example (i'm not doing anything specific below, just demonstrating how I use the variables with twarp, pwarp, etc)

>setvar p1 5
>setvar j1 10593
>setvar j2 5924
>setvar h 1043
>setvar tow1 11
>t h
>land p1
>p j
>t j1
>tow tow1
>t j
>land p1
>mac qtnt1*c
>p j2
>surround
>land p1
>p j1

etc and whatnot... It's very easy to add any number of variables.

Would also be nice to add an alias for current sector to setvar so for example
setvar j1 current
would set j1 to current sector.
That's probably not so easy, I just thought of it and haven't tried it before.

Couldn't you just create a bot module that would let you add all the variables you wanted to add then save them to a file?

H

Like Helix said, you could just do a module that would load that up for you. that way you would not have to adjust it for each game.

I understand your concern that you would not want to use a non-source script. But as I noted I leave that up to you. Once I stop supporting the bot I will release the code at that point. You can see the changes that I have made and I am adding in new functionality to the bot as well.

Is most of the work you are doing in the main botfile itself?

H

Yes, as of right now most of it is in the bot file. I know there are some of the modules that need to be fixed but i will get to them in time. i have fixed the SDT script that would crash if you got caught on first steal. Also added sector parm busted to the SDT file. Am pretty sure the SST will need the same fix just havn't looked at it.

With the modules, a lot of them were other scripters code so they can take a little longer to go through as i have to understand what they were doing first.