Laff. There isn't much to a citkilla. It scans the sector and adds the results to the DB. Then parses the stuff from the DB.

Prior to an upcoming release twx proxy had no SECTOR value for beacon, just a getSector (which I hear is way slow, but seems to be fine for me). This means that most versions won't see a beacon and will waste a wave on them.

Also a lot of them aren't too happy about feds being in the sector w/ you. This doesn't happen very often since it's rare that you're pdropping zyrain but it can happen in the areas around fed, MSLs or dock. Aliens also can cause problems since they don't show in the DB either. All of that would be a rockin addition for the next release (hint, hint) of twx proxy =).

There's also a corp bug where if you name yourself "Name [2]" or whatever it will mess w/ the enemy's corp targetting. There's a super easy solution to that... simply get the last word instead of getting between [ and ]. That won't fix the problem if they drop corp to spoof you... but if you're playing against those kind of players you have far worse to worry about than your citkilla. Another rockin addition to the DB would be the trader's corp number along w/ everything else... parsed using ANSI codes instead. Hint, hint. =)

When lifting to attack I use 3 as the magic number. It's slower, but... smarter. I have a little script I call "dumb reloader" that sits in the sector for xxx milliseconds, lands, refills figs, relifts. The point is to mess w/ citkilla... you have a 2nd corpie sitting on a planet running his killa and you peg the enemy as they lift. It's not a complex script, all of 30 lines I think so I'm sure you'll see others doing the same thing (ie: alex loves doing this while he pgrids) in their own way. So less is more, IMO.

My capture version sends 1 wave per scan. Slow, yes. But accurate and safe provided you can handle eating a wave yourself.

Then there's the gbonus mothing which is an infamous waste of figs. It's trivially easy to solve this too, I use load a file that contains the names of gbonus ships. One of my next public projects is going to be a citkilla that can handle gbonus ships better... so keep an eye out for that if you want.

The macro to use is a bit more complex. If you take a wander over to my site and looksie at the macro tutorial you'll see the macro I use and why I use it. It takes afew more commands but isn't going to send you warping or mess w/ navpoints or such.

Traitor's script is good. It's a refined public version of a semi-private script that everyone has and uses without really understanding. All attack scripts are a dual edged sword and you shouldn't really run them without understanding their flaws. In BG4 we scored an early planet when someone on the enemy corp had citkilla and ptorper running together. We planet gridded into their drop sector and his citkilla started lifting him... only problem was he had autoflee on and he warped out when we fired back, leaving the planet to fend for itself.

I had someone try an auto-attack pwarp torp on me the other day... it fired a torp then proceeded to charge into my sector. Only one problem... I was pgridding w/ an lv6. So uhm, don't be dumb. That's one of the reason why I don't generally pass out attack scripts, people use them when they shouldn't and get upset. It's not the script or the scripter's fault. Use as directed, see the warning label for details. Some conditions apply. May cause birth defects in new players.

As for traitor, heh... we all know he's not REALLY going to leave forever. The question is how long till he comes back. Laff.

See here:
http://www.blacksuntwgs.com/interviews/Traitor.htm

He even admits it. And that was a long long time ago. =)