I will be putting up proZTM31 for download this Sunday. If things go well, it will be released on a friend's site. I may end up using the new site for all script releases that I do in order to, hopefully, generate some additional traffic to that site. No, it is not a porn site.

Anyway, testing has shown that I am hitting about 99.998% accuracy in a 20K (6 warps missed), but I have seen a major speed improvement. I have been able to get the time required from 6 hours 14 minutes to 5 hours 39 minutes.

Part of the speed increase is due to EP and his thoughts on efficiency / plot. I started experimenting with warp/plot numbers and found, IMO, a critical spot in plotting the first warp that would allow a change in the plot method. The change provides a higher degree of accuracy w/o dramatically increasing time required. The accuracy allows the reduction of time in later passes.

Dependng on how much I feel like working on the script between now and Sunday, I may implement another option that will reduce the time by 45 minutes to 1 hour. The option, if used, would reduce the accuracy from 6 missed warps to approximately 550 missed in a 52,595 warp game or 98.95% accuracy.

I now believe an accuracy level of approximately 99.5% is possible in less than 5 hours. My original goal for the ZTMs was a very high accuracy level in approximately 5 1/2 hours for a 20K edit.

The numbers from testing:

start 00:43
PASS 1 01:59 46218 87.875%
PASS 2 02:58 50150 95.351%
PASS 3 06:16 52523 99.863%
PASS 4 06:22 52589 99.998%

5 hrs 39 min

               / Promethius / Enigma / Wolfen /

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

I usually like accuracy over time..

although.. if we had an option of speed vs accuracy. We could always run a quick ztm to get something we need at first.. then later use the highest setting for best accuracy when time permits.

doesnt seem to make a difference but with proztm30 i noticed it opens new windows on a disconnect/relog. the original windows contiune to update but will open new windows on each relog.

edit: only reason i mention it is because i remember reading about a bug having to do with closing the proztm windows.

I believe I have that issue fixed in 31. I lost a connection while testing and saw the multiple windows open so sometimes me losing a connection is good. Usually I am testing in an environment where I don't lose connections. I appreciate the information on it though since people can sometimes run into things I don't in a "safe" testing environment, and feedback is the only way I will be able to fix issues.

I've got a couple of more test runs to do on the script and hopefully the person whose site I am posting it on will be able to get it uploaded.

               / Promethius / Enigma / Wolfen /

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