You fixed the bug where someone just adj plocks and blasts
the xport ship to bits when you bring the planet in? Seems
like a very easy way to shut the script down.

Discussions about tactics that undermine the fundamental
concepts of a script do belong in script discussion.

Works fine if you scan ahead of time. In this day in age, tho,
that's a novel concept. But this isn't a thread about that. If
you want to derail your own thread doing so, ok, but that's
not really productive.

Anyway, so, how do you prevent someone from plocking and
blasting the gridder ship?

It hits, xports out, pwarps in, xports back, and sits a
small amount before scanning the next sector.

If I plock and blast immediately, I'll kill that empty ship.
Guaranteed, I can do it every time. Script shuts down
then because one of its ships is missing.

Add in an IG, and you've got a minute or two to take the
shot. All the time in the world.

1. Plock happens before you hit the sector, so calculation speed
is irrelevant. But yes, I'm very fast w/ it. 1 lag cycle, max. Its
all scripted.

2. Guardian bonus doesn't apply to empty ships. Only manned
corp ships over corporate planets.

3. I'm not going after you (well I could, but not for this tactic),
I'm going after the empty ship that sits in the sector.

4. If you don't xport out, then obviously I've stopped the gridder.
I'm not talking about citkilla, I'm talking about a blaster. 4 or 5
rounds of figs, then done. Not enough to be a problem. Most ships
do not have gbonus, however. Especially gridder ships.

5. You'll have to get rid of the walking xport ship to fix this issue.

Most scripts can be stopped one way or the other.

1)First you have to know it is being run.

2)Then you have to be at keys (for the most part)
(I suppose you can write a script to analyse fighits and choose a counter script but I never have)

3)Third write/Dl a script to counter and use it.


Frankly if someone can do the 3 above fast enough to kill a SINGLE Mow then they deserve the kill.


The "Easy" Kill issue only comes about...If your at keys AND figure out which script is being used by jumping adj and scanning AND the Gridder is using it over and over again.


........................................................................................................

P.S As a side note I find the practice of denigrating each others scripts in public distasteful.
Lets try and keep the discussion of weaknesses etc polite please!

Too bad you were on the other team, lol. We had a
small tutorial on exactly this during HHT practice.

Well enlighten us all then. Give us all a lesson on how to:

Kill a single mow while your busy doing a buydown.

Enquiring Minds want to know!

Well, assuming there's a move delay... LOL, it's not hard.
Might not be worth it tho, given the cost in ore. First 2 or
3 hits can be compressed tho.

We usually ran with 2 planets at a time. One for buydowns,
and another for torper. The torper, or "combat planet" was
the same one we pgridded with. It never, ever, ever went
back to base.

But basically the method we used was a binary search. Torp
w/ SS holoscan on. Use that info to tell whether there's an
empty ship, planet, or nothing in-sector. Branch from there.
It's possible, in 3 or 4 hits, to isolate pretty much any
gridding pattern and react accordingly. People can then mix
up their gridding, but that just means we have to do less
prediction work (even a broken clock is right twice a day).

In the case of a mow, you'll pdrop into their path and catch
them on an IG in most games. Well, assuming move delay.
All depends on what you assume as your starting point for
the search.

Ah! so no super secret buydown kill script then! Just TW 201 class.

TW 201 > Super secret buydown kill script

Much, much >