In every big game there are privately passed scripts that aren't given to any but the Chosen Few. One of these is the L. O. L. A. P. I'm not going to divulge who wrote it, who has it or what it's purpose here as it is used in an ongoing game; I just want to know what the heck does it stand for? I thought of, "Love our Land and Peoples". I can't think of anything else it could be.

Man, you nailed it. That's exactly what it stands for.

Could stand for "Laugh Out Load Akors Podded" heh just kidding with you akor no hard feelings!

Ok you got me curious.
Who wrote it and what does it do.
I have to be me.

quote:Originally posted by TheButcher

Could stand for "Laugh Out Load Akors Podded" heh just kidding with you akor no hard feelings!
No big feat to do that.

quote:Originally posted by Wildstar

Ok you got me curious.
Who wrote it and what does it do.
I have to be me.
See why I was curious? If you write a script and call it by initials and someone sees the name, they gonna get curious.

my guess is if you were suppose to know, you'd know. If it's private, why ask about it?

quote:Originally posted by Akor I just want to know what the heck does it stand for? I thought of, "Love our Land and Peoples". I can't think of anything else it could be.


Akor,

Lurking, Off-line Loading, Adjacent Photoner. So, you decided to check here finally, huh? well, nothing to see here, move along.
It's one of my better ones. [:D]

Good idea man

First time I have heard of it... Sounds nice... good idea...

Traitor, how about you break it down for us? Give us the specs, then you can give in and post it

I like to think of myself as an idea guy. Some are bad, some are good and get shared, some are so good that I keep them to myself, and some are so far outside the box it's like trying to read black on black. If you figured this out, don't tell Ender. heh!
I think this is a full list of my combat scripts:
L.O.L.A.P
O.L.A.P
Dock-Killah (I wrote t_buster specifically to counter this script.)
Auto-Grid (Now I just use Ram's stuff...mostly, heh)
ship-cappo
cit_t_killa (faster than oz's, but more dangerous to user. still buggy)
Ambush! (heh. just heh. I can't wait to use this on someone!)
Quad_X_port_Grid
Photo_Phinishem (photon, surround, cit/cannon kill. just several good scripts strug together.)
Aunti_Photo (anticipating, good against random chargers)
pod_chaser (yes. And I'm surprised peeps hadn't thought of this one sooner. it's not finished, and it's slow, but it gives a range of possible locations.)
Honestly, there are a lot of good public scripts out there, and I use the public ones more than my own. I mostly wrote mine for very specific situations. Of the ones that work, I've given out about 3/4 of those. The rest of the scripts are in various stages of not-quite-working-the-way-I-want.

My fig-watch, dataminer, and movehelper are in various stages of being re-written for TWXProxy 2.04. When finished, they will work together in ways that scare even me. Once those three are re-written to my satisfaction, I'll rewrite most of my others to take advantage of the database manipulation power the above three scripts give.

I'd say I'm about 75% of the way there on the inital re-writes. A lot of it was waiting on a versin of twx proxy that supported some of the ideas I had. The two big areas I'm working on are making most of my scripts able to load while off-line and turn on when needed or manualy invoked, and using sectorParameters to share data between scripts. The first thing is for convenience. The second will mean big, big changes in how data is managed and shared between scripts. Imagine if all your scripts shared data seamlessly. If they knew where all your figs were. Or your limps, or mines, or the DE's or Tunnels, or MSL's or bubbles. Imagine no more clunky files all over your twx directory.
I have a LOT of ideas. I wish I had more time.
Nothing personal Ender. Even EP hasn't seen them all.

So how is the new twx ver going to improve data sharing between scripts? Something better than a saveVar/loadVar stack?

Ahhhh. I sometimes think I was the only one who screamed when Xide got rid of the global variables. <sigh>

Anyway,

quote:
using sectorParameters to share data between scripts
So, for example, I have a script that all it does is track figs; enemy fig hits, and whenever you drop a fig. It sets a sectorParameter called "figged" to 1 in any sector there is a fig. A second script, like an adj photoner, looks for the "figged" sectorParameter to see if it's set to 1 or 0. If it's set to 1, then the sector is figged, and it warps and photons. BUT, if the "MSL" sectorParameter is also set to 1, it won't leave your planet there. (I like to grid MSL figs just before extern [:D]) And if the "ADJtoDOCKorFED" is set, it may or may not even bother going, or it might assume that they are trying to surround, and try to get ahead and run the PIG/Cannon or maybe a dens scan photon instead.

That is a small sample of the things you can do with working sectorParameters. And DB lookups are as fast as Array lookups for all practical purposes. You only notice the difference in speed when you start doing 1000's of lookups. Even then it's very slight. But compared to file lookups...much much faster. (Although EP even has devised a way to speed up file lookups too. So you can read a file into an array and then do an array lookup almost as fast as you can do a DB lookup. Writing to a file is still dog slow tho.)

Enjoyed your hidden descriptions of your scripts.
If you do feel like releasing them, I'll be at the head of the queue.