I've using the Pack 2 probe script as well as RammaR's probe script and neither are correctly determining which sectors of mine are unexplored. Does this problem have a simple solution I am over looking?

Also, how does ZTM work now, I mean, do I just run a ZTM script while TWX is recording and TWX will automatically take the data gained into account?

Also, is there a hot key to end a script running under TWX that I can hit from within my terminal?

I'm in the dark ages here people, give me a hand

Bruce

It's probably more of a difference between what you are calling unexplored and what the scripts consider unexplored. I always wrote probe scripts to grab the unexplored sectors list from the game server, but those scripts may use another means, like the explored flag in the database that can be several different values. Review the SECTOR.EXPLORED system value in the script.html file. Also, more about the discrepency would help.

TWX will automatically process the ZTM data. Be sure to use a ZTM script based off of Rev's "pass" technique.

$z or $sz can be used to stop all scripts, or you can use $sk to kill a particular script. Also, some scripts have their own hotkeys.

Regards,
+EP+

I read up where you suggested.

Thing is that when I tell it via the menu interface within the script 2_probe (or 2_query for that matter), and I tell it to use unexplored sectors, it just goes about it's sequential or random routine without regard to whether or not the sector is actually explored or not.

The same happened with RammaRs probe script, which actually counts up how many sectors have been found within the probe criteria and displays them before starting the script. In this case, when I tell it unexplored sectors, it comes up with ~4750 targets for the probes (this is a 5k sector universe that I have already explored ~83% of using COMPLETELY crude probe scripts that I have scripted in a language no one here uses [That being COMMO script, which I used to write a rudimentary helper back in the mid 90s and I am still familiar with it and use it when I need to accomplish something fast])

I have NOT completed a ZTM, and I am not familiar with the method which you are speaking of, if you could give a bit of details about the most proper way to ZTM for TWX, I would be much obliged.

[edit: I downloaded Cherokees Public Scripts from Grimy Trader and would using that ZTM script be sufficient? How many passes 2-6? How long does each pass take?]

Thanks for the fast response.

Never used 2_probe before, but Ram's should work... I've used it before and it does a good job of grabbing unexp'd sectors. It's a bit slow on the distance calcs, but that's about it. If you're using the distance calcs you'll need a ztm, but if you're just using random unexplored you won't... I used to use it in games I didn't have a ztm for (usually at the end of an unlim or high turns game) and it worked fine.

And yes, CK's "6 pass" ztm is good. Prome's ztm is good too. The timing on the passes differ based on the universe, how it's laid out, and of course the size. A 10k takes about 3 hours to fully map, a 20k... I'd budget 6 hours. A 5k should take less than 2.

When it says "explored" it means the TWX database has to have it marked as explored (or probed). It will not pull data from the game, nor will it use the in-game "explored" list. So if you didn't have twxproxy loaded and set to record data it won't know that you've explored it. If you had twxproxy loaded, listening to the data as it came in and set to record (recording is an option in the pulldown menu) but it didn't... then odds are you've got a corrupted game database.

Long story short, you use a TWX:

if (SECTOR.EXPLORED[sector] <> "YES")
blah
end

Type approach for this. The explored parm has other settings and dscan hardly counts as explored.

oic.

Yeah, I had explored most of this before installing twx so I guess that makes sense. Wish you could tell it to pull from the game

Bruce

Nod, one of the features I asked for a long time ago... the ability to write to the game data arrays. Then you could write a script to pull the "explored" list and update accordingly.

ElderProphet is right on those ways to stop scripts , All scripts & system scripts.
I set a hot key as $sx this stops all non system scripts .

A system script is one with a line in it
system script

these run in background and are harder to stop unless you use ElderProphet's way
or stop them with Stop script feature in twx.

I'm not sure , but I thought with twx's record on if you cim sectors the twx will record these as seen.
But I'll let someone confirm or refute this.

Yeh, try a sector CIM... it might work.

It should work. I log in using an observer account and it lets me grab a complete map of the universe. I use it to post the maps for our ICE9 Building Games.

Thanks for the help everyone.

I ran a 6 cycle ztm using Cherokees ZTM script and then exported a bubble report from TWX which after I checked about 4 of them (granted I went and checked the bigger ones) turned out to be terribly inaccurate.

Have I done something wrong here?

I've restarted a new ZTM using the "horrendously slow" 1_ZTM script that came with TWX. ETA: 7 hours or so (which is fine by me really).

But, I don't want to do it for nothing. What do you all think?

Bruce

If I were going to spend all that time..I guess I'd rather use prom's ztm, seems you get more bang for your buck.


my unsolicited .02 $ ..worth every penny

TWX will grab all of the warp data visible in a CIM. It's a good practice to CIM before probing or ZTM'ing anyway.

I have a probe script and ZTM I should release. The ZTM isn't polished, but the probe script is, and is as efficient (time and money) as a probe script can be. This was the one I used in one of the TWX scripting classes from a while back.

Of course, if there were enough interest, we could do another script class, and then you could hammer something like this out yourself. You know, the "give a man a fish..., teach a man to fish..." paradigm.

+EP+

I would be interested, but it may be a bit beyond my means atm, EP. I haven't tried my hand at writing TWX scripts at all just yet, but I've been reading about it on pages like The Cabal's Secret Hideout and I can wrap my head around things like arrays. I was quite proficient with another scripting language so I imagine if I apply myself a little, that it should come fairly quickly to me.

Anyways, 40 minutes till this ZTM is done Hopefully, this one will paint an accurate picture of the universe for TWX. *crosses fingers*

Bruce

Nod, it's bubble report will be different than what you see visually, and there's a size limit in twxproxy you'll need to adjust. Ck's ZTM is slightly more accurate, at 6 pass, than prome's, but not by much. Or atleast it was, I think he talked about adjusting his algo. Xide's ZTM method is horribly inaccurate, IIRC.



Warp data yes, but will it update the SECTOR.EXPLORED[sector] to YES for it?



Nod, for the most part just probe by depth from dock, removing newly explored sectors from the list as you go.



Think of arrays like a tall stack of boxes. You give a name to that stack, then address each box by an identifier.

Ie:
SECTOR.EXPLORED[sector]

The name of the box is SECTOR.EXPLORED and the identifier is the sector number, so you'd have...
SECTOR.EXPLORED[1] to identify the 1st box (which would correspond to sector 1), etc, etc.

If SECTOR.EXPLORED was "NO", then it would be updated to "CALC". This is true for a warp or port CIM.