This is the beta release of a citkilla I wrote. I've tested all of the major functions and now need to get some game testing in. This citkilla is similar to most out there, except it has some additional safety features I've added to help prevent some of the more common anti-citkill strategies.

First, ships with guardian bonus can be put into the file "gbonus-ships.txt"

The script reads this file and won't attack matching ship types. It is case insensitive and will work with a substring so if you're trying to prevent "Subterfuge Enterra" you can either put "subterfuge enterra" or just "enterra" in the file.

I would like to compile a list of the most common gbonus ships. I know there's probably a dozen or so common edits that have a dangerous gbonus. I plan to code these into the next release so that the file will only be used for lesser-played edits. If you run into a common edit w/ a gbonus ship let me know what edit it is and what the ship's name is. I'll compile a list of these for the next release.

It does verify that there's more than 1 planet in the sector before determining gbonus, so if their planet warps out... they're history.

Afew other safeties... I keep a running track of your fig wave and the count of figs on the planet. This is used to help determine if you're running low on figs on the planet, or if you're in a pod (in some edits, big figwave pods won't trigger it). I may add more pod detection later if it's worth doing, but for now this'll suffice. If it thinks there's a danger it'll shut itself off.

Script uses a safe macro that won't screw with your navpoints or anything like that. It fires 3 lift-attack waves, then rescans. This puts you back on your planet more often and makes you harder to kill during a counter-attack. This is compiled into a single macro and send in a burst, so it's likely to get sent in the same packet... and is going to be as quick as possible.

Script checks it's status every 20 minutes. It does this by getting your prompt and figwave. If you're not on a planet it'll shut down, if you're on another planet or have a different figwave it'll use the updated information. Makes it easier to use in a game w/ a lot of corpies. Sucks to fire partial waves because of outdated wave info, or to get stuck in sector trying to land on the wrong planet. It also has an invisible keepalive to keep you from timing out, jIc that's a problem for you.

Also a small CN fix routine to turns off autoflee so you don't get chased off your planet.

Also a whole bunch of spoof safety that makes it very hard to spoof. If you find a way to spoof it let me know and I'll harden it some more.

I would like constructive feedback, feature requests (but I'm not going to slow it down... so, not all features will be added), bug reports and gbonus ship types.

You can download this at:
http://www.navhaz.com/files/dny_citkilla.ts

Thank you sing, we moochers appreciate all you do for us who lack the coding skills!

Nice piece of work Sing. I use a change in sector navhav to start a pod check.

Thanks Sing, I will let you know how it works for me.

Cerne

Good idea phead, props. I've added that and uploaded the changed version at the above URL. It's now stamped version 1.1.

If the navhaz in a sector has changed since last scan it'll now check the quickstats and see if your shiptype is EscPod... which covers 99% of the pods out there (special pods being the exception, like subzero's redrum pod). Still, the default redrum pod's figwave is only 100... which'll be picked up pretty quickly on the next check.

SetTextTrigger mined :mined "Mined Sector: Do you wish to Avoid"
I add this in case someone is moving the planet around by hand. You dont need it per se. but its handy. and script? command is nice

may i ask what

"SetTextTrigger mined :mined "Mined Sector: Do you wish to Avoid""

does for you?

If you pwarp a planet under an enemy mine then scan from cit you will get this message and be stuck at a yes/no prompt.....requies a carrage return to clear it. Sing's "cooridinator script" does this for those that use that and  most bots do or should handle it. But if you are running a citkilla script and nothing else you may get stuck here at the wrong moment. As I have not tested Sing's Citkilla yet I dont know if this is an issue as he may have handled it in a buffered macro instead of a trigger which is usually the best way to handle these things if at all possible.

oh, well i know oz's sends szn, guess i haven't tried the new ones out.

Mine sends " s* "

It isn't a problem from within the script. That's a very simple detail.

"szn*" is oz's approach. Which is exactly 2 keys more than you need.

Ya, if someone's sends just "s" well, I'd be wary of their scripts
however, sing, yours, what if you are off the planet (for whatever reason) and it triggers and you are not photoned and you have a holoscanner, and there are mines in the sector?
From what I can tell, you'd be stuck at the y/n prompt.

Slim, nope... it's fine.

Edit:
There's really 2 questions here tho.

1: If you hit S manually and it triggers the citkilla, will it hang on mines? The 1.1 might've, I've added an extra "*" at the beginning of the attack macro sequence now and it won't. So if you're using this... get the updated ver.

2: If there is no target you'll stick on the mine prompt and have to hit N manually. That's annoying but not a problem for the script. I probably won't mess w/ that since I don't want to cause conflicts w/ other scripts. I did add a "*" before the scan macro... for:

send " * s* "

So now if you are at the manual scan sticky and someone lifts again it'll take care of that for you.

Sing has posted version 1.2 on his web site.
http://www.navhaz.com/files/dny_citkilla.ts
Get your updated copy and register at Sing's fine web site while your their.