I had a thought. It was biggie and it hurt a little, so I'll try to be as articulate as possible (self-depreciating humour is a gift )
Okay down to biz.
I would like to toss into the ring the idea of a the Standardization of 'Custom Sector Params' --beyond the inherent.
Not being fully versed on the aspect of using Sector Parameters, I have been told using too many Custom-parameters can be counter productive and drastically bog a DBase.  Naturally, if one were to use only Private scripts this probably wouldn't be an issue. Thinking with a long term mind-set and hoping to be proactive, I am wondering about the feasibility of  drafting up a voluntary set of Standardized Custom Sector-Parameters. I think having such a Set of 'Universal' Sector Parameters will avoid what I think will inevitably result in bloated DataBases. There may already be such a Set in the new release of TWX, which would, perhaps make this post most irrelevant.
Obviously this is an altruistic idealology that probably goes beyond the  credo: 'It's just a Game!' ..if so, then please ignore my ramblings. However, if the converse is true, then I'd like to start with a simple and obvious suggestion:
setSectorParameter {SectorIndex} "Scratch" {value}
The nomenclature is important, but I'm suggesting "Scratch" only to illustrate a possible Universal Sector Param for temporary data. Another, and less obvious suggestion:
setSectorParameter {SectorIndex} "Score" {value}
let us assume values between 1 and 10 (0 indicating not used), give an indication to the 'relevance' a sector has with respect to Gridding. 1 being not important, and 10 indicating high priority-target.  Probably tipping my hat here.. but somehow I doubt it.. hehe..
Anyway. Minus the self-depreciating humour, it'll be interesting to read what more experienced scripters think.
Lone
 
 
 

I may be wrong, but I think Sing had something setup for standard settings.

               / Promethius / Enigma / Wolfen /

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

Traitor and I spoke on this many moons ago, and I've spoken with Sing about it as well. It's certainly scripter preference, but between Traitor's standard list and Sing's standard list, we could probably hash out a combined list of the most commonly used sector parameters.

I do see the need for this, and appreciate you bringing it up LoneStar. In truth, Sector Parameters have been under utilized to date, but a need for standardization will grow as more scripts make use of them, which is inevitable.

It'd be nice if the standard is somewhat based around the TWX 2 Export criteria, as posted on Swath's site.

+EP+

How about giving TWX the ability to modify/rewrite files? That is true power right there!

Perhaps if Sing and Traitor would post the list here we could come to a concenus on the issue and the best way to use them (0 vs 1) or (0 vs qty) for mine data etc as to promote compatability between scripts of the same or similar function.I use them in a certain way but would be happy to change to promote better functionality in public scripts or soon to be public scripts like unlim gridders etc.

I've been using Traitor's list pretty much verbatim with a few minor exceptions. Sector parms are case sensitive, so I uppercase all of mine to remove issues there.

I talked to MD about this too a while back, we had a few we hashed out then.

Been trying to get this done too, but it always seems an uphill battle. One of the reasons I'm eager for the 2.04 final build is to get the parm loop bug cleared up for the public release... allowing me to write more public parm-related scripts. The few I have on my site experience the "unknown error" bug probably 50% of the time. I figure the more public scripts use parms, the more likely others will adopt the same ones.

And yea, obviously you're trying to do datamining. There are a lot of ways to do this. I don't use a scored sector since the score itself would change based on who I'm playing against. Ie: Some players never build in DEs, some always do. Sometimes I can probe, sometimes I can't, etc. Sometimes people move their base from an unexplored DE w/ none of my figs nearby to a random already explored 3-way with 1 of my figs adj. You get the drill. What I prefer to store is this basic information... then crunch it on the fly.



Those are the ones I initialize for every sector.

Other stuff I set along the way:



I don't use the ADJ to fed very often because of this little snippet:



Frankly that's such a trivial thing I see no reason why to spend more time w/ a DB call bloating it further when that will suffice... 99.999% of the time.

And p-head... consensus, LOL. We can't even agree on an edit most of the time.

 
I'll check the Export criteria for my own edification, and perhaps contribute some more ideas.
Thanks for the info.
Lone

Great list of params. I think they'd make a great foundation upon which to build from!
Thanks for sharing.
Lone

EP BTW, I always get this message a few times after using your script and once I get it, I always get it upon attempting to trade for that game. I tried to reset it w/ that other script, deleting the files, so related to a loadVar I am assuming.


Agreed, 150 units.

We'll buy them for 12,996 credits.
Your offer [12,996] ? Unknown script run-time error 'EP_BETA06G.TS': , line 698

Script terminated: C:\TWXProxy\scripts\EP_Beta06g\EP_Beta06g.cts

12996
You insult my intelligence, but we'll buy them anyway.

Looks like the parm bug to me. IIRC this has been fixed and is awaiting release.

Traitor's list is good enough for me.Thanks for the input.