Never seen this. This is when I'm just opening it up to connect to a game

If your using that version on a V2.18+ server your going to have a lot more issues. It is NOT compatible with some changes that were made.

2.19. it's the newest version from TBH that was uploaded a few days ago. Also, I'm getting this before I even connect to the game. I can't get it to load =0/

Yes because he is not currently supporting 2.19. Thats why I sent you one that would work. If your going to use that version you will need to stay on TWGS 1.03.

I did not realize this. I don't play 1.03! Back to your version thanks again

Are you saying that changes that are new to TWGS v2.18/TWGSv2.19 are breaking Mombot, or are you referring to issues that are related to all TWGS v2 releases?

There shouldn't be any changes for recent releases that are breaking scripts. If there are, I need to know about it.

It started with 2.18 if memory serves me correctly.

I have played a couple games and noticed no problems but if you can send me a list of some of the script problems maybe we can figure out what the problem is. I would gladly join a game and do some testing but I need a list of scripts to test as I have no desire to test all 2000+ that I have.

I don't think it was breaking anything. this happened before i fired up the game to connect. I would start mombot to log into the game and it was giving me that error. I tried it on both TBH and t0yman's version of mombot. I just cleared out my data from mombot and created a new one. Probably just corrupt data. Something new I've never seen before just wanted to post it out there

Ok. I'm just keeping an eye out because there seems to be evidence that there are new issues showing up on the most recent versions. It's hard to sort out all of the variables, so I need to hear what problems people are seeing and try to isolate the cause.

Some of the changes with 2.xx have broken some of the scripts in mombot.
The exit/enter portion for example- and it has also affected some of the other add-on scripts that rely on exit/enter, such as clearing limps and minesweeper.

Some info for scripters.

Echo ANSI_10 &"**Try this*"

may get weird effects in Swath showing [32;4 behind a command prompt or planet prompt or even the Citadel prompt.
but if you rewrite it to :
Echo "**"& ANSI_10 &"This is better*"

You will not see these problems ....

Just something to look into when rewritting mombot.

Just some script info to share.

Echo

Someone in the past had turned off the fancy tagline that Mind Dagger had created and I turned it back on. That is the gibberish that you are seeing on the screen. It is just ANSI art that is not coming across properly. This will not affect the bot in anyway as it is just an echo. I will clean it up and simplify it a little so that it shows up correctly.

Isn't there a way to write the program (Mombot/TWX) to work with both 1.03 & v2.x ?

Seems to me we need to pull together the talents of the script writers to build a cohesive "helper". At least the basic public scripts updated to work with both releases.

Sort of like how we expect our productivity software to run on both 32 bit WinXP and 64 bit Win7 at the same time.

Short answer is yes.
Long answer is it will take some time, and functionality will be degraded.

The way to do it would be to replace the key commands with waits.
Part of the issue with the exit/enter is that in 1.x it queues the keystrokes while in 2.x it ignores them- so it will log them out fine, but won't log back in. You throw in a "waitfor" command and when it sees the login prompt, it will log them back in. There are multiple instances where this would be needed to get it to work in both systems, assuming all the prompts stay the same.

The degradation in performance comes from using the "waitfor" command.
It pauses TWX waiting for the appropriate prompt, then has to kick off the next section. Using the fix for exit/enter that was posted on the forums, it is noticeably slower than the same command in 1.x.

Hope this helps.

99% of it does work in both version's and most modifications are done so that it works in both, but there is occassionally that one that is a PITA and easier to just move it to the new. I have researched the one change (but I think JP might put it back) and it is possible to make mombot work in both but I don't play the older version and we needed a working copy for a tournament so we just got it working. Then of course like most things, lack of interest on my part tends to let it slide by the side.
This link will explain the area that changed, ship stats is not the same as it was, some items moved and that throws off the cuttext command. This change broke "mow" & "surround" and a few other commands but not all since some grabbed the data elsewhere.
http://www.classictw.com/viewtopic.php?f=15&t=32686
From the above thread that explains some of the issues.

Understood, and mombot has been corrected to work with this new data format.