LS,

I think I ran into a bug in the 1.6 version you just put up. I was using 2 ships, one with 255 holds and one with 250 holds. It would only grab and drop colos from the first ship (255 holds) and just tow the other (250 holds) back and forth.

When I realized it was doing that I got another ship with 255 holds and everything worked fine.

Let me know if you want some more details or some other info.

Great script by the way.

Cerne

might be it only checks number of holds in first ship and assumes the 2nd ship is the same, but still I would think it would grab 25 collies with 2nd ship... try reverseing it if u have the chance, start in the 250 hold ship and see what it does with the second ship. I'm guessing here, that it would only put 250 holds of collies on it...
Also were both ships the same as far as having a P scanner?

Thanks Cerne for letting me know about the problem.

Zarkahn hit the nail on the head re P-Scanner. One of the small improvements I put into v1.6 was detecting a planet scanner in both ships to optimze the burst macro a bit. The autodetect worked fine. The problem occured because I also tried to make use of Load/Save-Var 'Logic' (another small improvement). Long story short: if the second ship had a pscan, and the script thought it didn't, the second ship would never land and pickup cols.

So problem's been fixed. And in the process I added another small improvement:

I use the TWX command: $SL (Load most recent script), alot. This wasn't possible because LSECT utilizes a support script (now called "LSECv10b.ts"). I made use of the TWX-Proxy command: ListActiveScripts to get around this. If using an older version of TWX remove lines 559 to 571, inclusive if this new Logic causes problems.

Thanks again to Cerne, fixed copy is on Grimy's.


[LSEDIT]
Forgot to mention that LSECT will need to be put in the 'Scripts' folder. If it's placed somewhere like: C:\TWX\Scripts\LoneStar\ ...then change line 569 to:

setVar $temp ($temp &" load #34LoneStar\" & $Master_File & "#34*")

It turns out that yes the ship with 250 holds didn't have a planet scanner.

Thanks for the update.

Cerne

I just ran the v1.61 and the status window didn't open. I have the script in the script directory. Also, it didn't stop when terra ran dry

Cerne

If the window doesn't appear, my guess is you're not using TWX Final. Which means the support script isn't loading (the same script that detects when terra's dry)

Delete or comment out lines: 559 to 571, inclusive. you should be good to go

Sounds like an awesome script.
I think someone actually made this script like 3 years ago.
MMMMM who was it. It was me lol.

It is cool that you improved on it LS. I always encourage it.

I solved the problem by doing a quick ship info and having it store the veriable and go from there.

You can hit me up on messenger anytime dude.

I thought I was using the newest and the 204 beta tag when it started was just an EP oversight

Okay I downloaded the 204 final version from Grimy's front page, the date on the executable is 01/21/2007 8:44PM

Cerne

It still says beta when you fire it up, is the version on Grimy's out of date. It was the same one I was using before

Cerne

That is the same version of twx that I am using.

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

Sorry your having trouble. I've since replaced the LSECT you've D/L'd with a copy that has lines, those I've mentioned in a previous post, commented out.

Thanks LS, out of curiousity, what is tha file date on the exe you use?

Cerne

File date on the exec, in the zip file: 21/01/07.

try the example for the ListActiveScipts found in the script.html

Here are the results:

Command [TL=00:00:00]:[2089] (?=Help)? :

Loading and compiling script: C:\TW2002\TWXProxy\scripts\test.ts

Command [TL=00:00:00]:[2089] (?=Help)? :
Script terminated: C:\TW2002\TWXProxy\scripts\test.ts

looks like you're using the latest and greatest of TWX.

hit me up on icq (240 630 042). In the mean time. try the script again (make only one run), make sure it generates the support file called: LSECv10b.ts ... then try and load that file see if there's any errors