So it wouldn't be "YES" then? k. So then you can't update your exploreds from the CIM.

Any way to do that?

No, TWX has to scan the sector for it to be YES, by entering it, or through a holo scan, or a probe.

You could hook a TWX session up to another TWX session and fake a probe or holo scan. It would be kinda nice to have a Sector.Explored value of CIM though, where you know the warp data is complete, but not necessarily any of the other sector data.

I sometimes use a seperate Text file to exlude Targets from a generated Grid-List. For exmaple, games with long Citadel build times. I can use a seperate list to remove --filter out-- 'Blocked' DeadEnd's on day 4; logically a base wouldn't be there so need to grid there.


{EDITED}

Which poses the question... if you weren't using twx then, how do you transfer it?

I've had this problem before when I had a DB get corrupted and suddenly an 80% probed universe vanished from view. Would be nice to have a way to fix that, since obviously if a sector comes in thru the warp CIM then it's been viewed.



Nod. My grid list is manually generated, filtered a few different ways and then plugged into a gridder. One of those filters is an "explored" filter, letting me filter out explored sectors from the list.

Doesn't happen often, but sometimes that list gets messed up inside the twxproxy DB. As it is now I either export from swath (which has it's own issues) or use the in-game list to filter against the list, but would be nice to be able to manually update some of those data arrays. For instance we could manually update the limpet array from a k2 (or mines from k1) instead of using a parm.

An import from Swath still only gives you CALC. Seems like the best way would be to capture the results of CKE, which TWX doesn't currently do.

I understand the logic behind TWX listing those as CALC, and it seems like a better idea to have your script parse the CKE list rather than have TWX list any sector that it didn't actually scan (into it's current db) as YES.

If you have to parse the CKE list each time then that makes the entire SECTOR.EXPLORED array next to useless. It's also a big giant step backwards from the common standard.

IMO if it's explored, it should be marked as explored. Either from the CKE, a CIM, or from an import. But that's why it'd be nice to have these arrays writeable, if someone wants this functionality they could just write it themselves... while leaving everyone else to their own.

Actually I've had this problem while probing unexplored sectors, but if I do a CIM it fixes the problem. I use Rammer's probe script.

I'd be interested. I've been writing some of my own scripts recently. Gotten some great pointers from a few people (tks again everyone!) but could always use more help.

LLH