There seems to be a problem using some M()Mbot routines on a v2xx server since we probably haven't updated to the necessary stats routine for v2. I just had a ship stats issue happen on a v2 server where the same routine works just fine on a v1.03 server.

T0YMAN!!!!! Help LOL I am going to try to update the bot to use your ship stats routine for v2.xx what do you think?
1. It would need to get the type of server during the mombot initialization, v1 or v2, and save it.
2. Then for any script or module, check the variable before doing anything that uses the ship stat routine
3. Then gosub to the correct routine.

Is that about right? Some of the routines affected are wsst, auto-kill, cap, etc.... I am sure there are others.

H

I had it working on both and all the commands mentioned have been tested. only time I have seen a problem is on a corrupt database or it might be in the storeship command for the uncommon ships that aren't grabbed in the startup routine.

Yes its weird. The only time I have seen issues have been on version 2 servers. I commandeered 2 of Micro's games and it happens in Hell on Earth but not in Subzero, both 30k sector games. I am going to try and nail it down tighter post some logs and have a look at the twx config file and see if there is a difference. Gonna make a couple test games (One sub and one Hell) on my v2 server and see if I can spot the issue in the logs/.cfg ( v3.1042.cts has been working great for 99% of everything I run. I even killed my existing twx/swath install and started from scratch with "The Easy TW2002 Player Setup Pack v1.00". I will post again when I can provide a log. I am going to kill the dat files for Hell on Earth (Game H on MBN)

H

Helix , I made one change to your Easy TWX setup .. I moved the TWX proxy folder out to next to the Tradewars folder in the root of the install.
This keeps the directory depth just one shorter and a little easier for beginners to see/understand the structure.

Also I advised them to put this unzipped just off of the C:/ drive
all as C:/UnZipped/

Teaching has been a bit easier with the archive you presented.

Thanks again for your time and work.

Vid

Mom is capping all the ship stats and storing them in the _MOM_GAMENAME.ships file. If the problem is an issue with attacking verify using $sv ship_max_attack is the correct number there is an "if" so that if $ship_max_attack it reruns the getshipstats command. I have deleted *.ship and reran numerous times and I don't see any issue in that area.

The fast/auto kill might have a problem determining if the person to attack is eligible to be attacked or not, since the only game I am playing is locked I don't have a way to really test and I am not interested in entering a new game to chase something down that I can't reproduce.

If you can be more specific it might help point in a direction but I have not seen any of the problems with any of the above mentioned commands. Good Luck!

That's exactly what I was experiencing. I was in a Alien Ship. I removed the ships directory a few times and now it seems to be running just fine. The person(s) who i've tried to attack are both well over 100k experience. I'm waiting to test it out again but so far no bait lol. Updates soon to come

I always open that file and look to make sure it got added correctly. You can always add it manually if you want.

Shields O D Cost Holds Figs Init Holds Def Bonus - ship name
2000 15 15 329000 150 50000 40 4 0 Imperial StarShip

I think we are talking apples an oranges here. I am talking about the get stats routine, not the bot initialization ship info capture.

Sect 27643³Turns 0³Creds 774,622³Figs 97,970³Shlds 10,000³Hlds 250³Ore 0
Org 0³Equ 0³Col 0³Phot 0³Armd 226³Lmpt 226³GTorp 19³TWarp 2³Clks 20
Beacns 250³AtmDt 20³Crbo 1,000³EPrb 100³MDis 25³PsPrb Yes³PlScn Yes³LRS Holo
Aln -1,046,980³Exp 8,134³Corp 1³Ship 2 MisFri

I am not sure which fruit you're currently talking about, but, Comet and I were discussing 1 thing you may be discussing something else. The routine you're talking about does not typically have anything to do with mom bot but more a quickstat check setting that is set individually in each script. since nothing changed on that setting I can't imagine where it would make a difference whether it's v1 or v2. But I will look at it tomorrow if I have time.

The path is supposed to be C:\TW2002\... with all the other directories under it, if you unzip it directly to the root. Doing anything else means dragging the TW2002 to the root.

H

Sorry I didn't mean to derail this thread I was talking about something else. On the fact of apples and oranges that's the second time someone has said that today. Perhaps I should take in more fruit? Anywho sorry for the derail!

No problem I think I did the same for your thread so I made a new one. Turns out that wsst has its own quick stat routine. Thats probably the culprit of my issue. Whats so funny is that my issue only happens if SD is the refurb point.

H