I want to say that thanks to you and our play in the April challenge that I have a better understanding of the basics of running SDT than I ever had before.

Tonight I waited until after extern for all the busts to clear, then I off-robbed all three reds at our base then started the Team SDT with 0 errors. So I want to say thanks for all info. The team SDT I am using saves the last steal port and the last bust port.

Yes, busts are set to clear daily, and extern did run. I did eventually get TSDT to run and cashed a little over 100m. The following day I fired up the script again, and it fake busted at the first port. I checked the logs to see if the script made an error, and confirmed that the port was not the last port robbed or the last bust for this player. The script did not make a mistake as far as I can tell, but it got a fake bust.

That smells like a bug in something.

+1, and the reason I picked up TWX in the first place.

@Helix and Micro if your using Xanos among others TSDT script there is not true bust checking in that script. While it does store to a variable where you last busted it can be overrode by the player or a crash, which it does frequently. Other TSDT script don't even have that variable, and the inert TWX tracking is if I remember correctly buggy in the newer versions.

Might have something to do with prompt aborting, might not.

Yes, we noticed that. There is a field in TWX to track sector busts, but it does not appear to contain any data.

So should we improve on already written TeamSDT scripts to eliminate fake bust chances?

These scripts track busts and last steals once they are started. The problem is starting them and/or restarting them after a crash. If you can provide the script with correct bust data at startup it will run fine.