Hi all,

In one rare moment of insight, I nailed down a pesky bug that's semi-randomly plagued players across countless universes. It's fortunately simple to avoid, but if left unchecked can ruin your fleet moves, leaving your ships stuck in place just when your choreography is at its peak.

"Stuck" bug explained and circumvented:

- Let T be the Target fleet. Main pursuer would be M, and let's have some Secondary pursuer(s) S target the main pursuer. T can have a lower or higher ******** than M, and it can be a foreign fleet or one of ours, stationary or moving.

- Next turn, if M has a ******* lower than S, we find S has moved towards M, and M has moved towards T, as expected.

- If S has a ******* lower than M, we find S has moved as expected, and M is still targeting its goal, but hasn't moved. It even shows in foreign scans as stationary: M is stuck for as long as at least one secondary fleet with lower ******* is targeting it! (bug)

It doesn't happen if T is a fixed point in space, or a planet, or a minefield, or if S and M were at the same spot.

Fortunately, it is easy to avoid if you are careful. Even better, others cannot use it to freeze your interceptors, at least not in the several simple tests performed.

[some details removed pending 3rd party review of possible nasty exploits. PM for the ugly numbers]

[Updated on: Thu, 22 December 2005 04:56]

Report message to a moderator

Hmmmm very very interesting peter!

Did you do any checks if S was a different race? i.e. in a team game a persuer from multiple players? Remember my issue a few months back in Humanoid space? Where all our fleets went randomly all over the place? chasing other wierd fleets?

Report message to a moderator

OUCH!

This one is dangerous since it is too easy to exploit. Just think, target a ship that is likely to be targeting a minelayer and, if the numbers are right the enemy doesn't get to the minelayer ever. All you have to do is target it with one chaff scout and move at warp 1. I will test this and see what I can find out.

Well done! If this pans out I recommend a commendation for m.a @stars for his discovery.

Ptolemy


(updated for spelling since I can't spell worth crap when I'm tired)

[Updated on: Wed, 21 December 2005 06:29]

Report message to a moderator

TheJorrus wrote on Wed, 21 December 2005 12:18

Hmmmm very very interesting peter! Did you do any checks if S was a different race? i.e. in a team game a persuer from multiple players?

I didn't test that much, but it wouldn't be surprising. I hope it doesn't carry across different races, though.

TheJorrus wrote on Wed, 21 December 2005 12:18

Remember my issue a few months back in Humanoid space? Where all our fleets went randomly all over the place? chasing other wierd fleets?

I don't recognize you under that guise, sir, but indeed some weird reports from that age and place are among those who allowed this "new" critter to be studied and ultimately vanquished.

Report message to a moderator

Ptolemy wrote on Wed, 21 December 2005 12:20

This one is dangerous since it is too easy to exploit. Just think, target a ship that is likely to be targeting a minelayer and, if the numbers are right the enemy doesn't get to the minelayer ever. All you have to do is target it with one chaff scout and move at warp 1. I will test this and see what I can find out.

Mars, I sure hope that exploit can't exist, as the effect would be devastating.

Drats, I should have tested more before unleashing this. :-/

Update: I tested with the race owning T using some chaff (S) to target M at a very low warp. Using lower or higher you-know-what didn't trigger the bug, so M moved as expected. Phew.

[Updated on: Thu, 22 December 2005 04:59]

Report message to a moderator

Report message to a moderator

TheJorrus wrote on Wed, 21 December 2005 13:37

Yapyaps ring any bell? Discount my last turn ofcourse! *snarl*

Oh my... The horror, the horror!

Report message to a moderator

Report message to a moderator

Report message to a moderator

Since I arrived late, I don't really have that much idea what's involved, but be sure to check with S at warp 0, since its a common tactic for tracking enemy( or ally ) fleets.

Report message to a moderator

gible wrote on Wed, 21 December 2005 23:01

Since I arrived late, I don't really have that much idea what's involved, but be sure to check with S at warp 0, since its a common tactic for tracking enemy( or ally ) fleets.

Amazing. I've been testing with Warp1. I'll include Warp0 in the next batch of tests.

Report message to a moderator

Hi,

I've done my tests with foreign fleets targeting the main pursuer at Warp0 and even stargate setting. I've found no instance where a different player can trigger the "stuck" bug.

So, it's only a matter of your own Fleet IDs when setting fleets targeting fleets targetting fleets.

The golden rule to ensure your fleets obey their orders seems as simple as "first to move, lowest ID".

So I think this nasty bug should be added to the official list of them.

Comments, suggestions welcome.

Report message to a moderator