Re: timing - driver build and packet hit. |
Thu, 08 June 2006 11:52 ![Go to previous message Go to previous message](theme/Stars/images/up.png) ![Go to next message Go to previous message](theme/Stars/images/down.png) |
|
vonKreedon | ![](images/lt.gif) | Lieutenant | Messages: 610
Registered: March 2003 Location: Seattle, WA USA | |
|
bigcanuknaz wrote on Thu, 08 June 2006 08:38 | no, it was a warp7 that fired at warp10, and I had it built when it was in space, though not when it was fired.
turn1
I colonize planet and put warp 10 dock in queue
enemy fires packet from warp7 driver at warp10
turn2
I build warp10 dock
packet is in space
turn3
my pop is wiped out.
------------
I thought the driver should have caught the packet.
naz
|
As described that does seem wrong. So, the enemy's firing planet was more than 150ly from the target planet so that it took three years to arrive at the target, correct? You finished building a SD with a Warp 10 driver at the target the year that the packet was visible in space going Warp 10, then the next year the packet arrived and despite the presence of a Warp 10 driver the packet killed off all the population, correct? Assuming all those factors are correct I believe this would be a big bug, but it is not something that I'm aware of happening and think that I would, so I'm still expecting that you missed something in the sequence described.
Report message to a moderator
|
|
|