| Tracking a fleet through a wormhole |
Tue, 16 September 2014 16:10  |
|
 skoormit |
 | Lieutenant |
Messages: 665
Registered: July 2008
Location: Alabama | |
|
I observed the following interesting behavior when tracking a fleet that jumped through a wormhole.
Year 0:
I give fleet Z a waypoint of enemy fleet F. I set the speed to warp 0.
Meanwhile, the enemy gives fleet F orders to move through a nearby wormhole.
Year 1:
Fleet F has moved through the wormhole and is still on my scanner (although fleet F is no longer in range of fleet Z's scanner, he is in scanner range of a planetary scanner of mine).
Fleet Z's waypoint has moved to the deep space location where fleet F entered the wormhole (which is not where fleet F actually is).
Fleet Z's waypoint target still refers to fleet F by name. It does not say "Deep Space." But if I click the blue diamond to change the target selection, the only option is "Deep Space" because nothing is at that location. However, I don't change the target selection. I leave it referring to fleet F by name.
I do *not* get the standard message about "the fleet you were tracking...appears to have outrun the range of your scanners." Which makes sense, because fleet F is still in range of my scanners. So even though the location of the waypoint for fleet F is visually out of whack, fleet Z is still apparently targeting fleet F.
Meanwhile, the enemy gives fleet F orders to lay mines.
Year 2:
Fleet F lays mines.
My planet nearby to fleet F is destroyed. Fleet F is no longer in range of any of my scanners.
I get the standard message about "the fleet you were tracking with fleet Z...appears to have outrun the range of your scanners."
Here's the interesting part: fleet Z's waypoint for fleet F has now moved to the actual location of fleet F and the waypoint now says "Deep Space" (since fleet F is not on my scanner at that location).
(I presume that if fleet F had still been in scanner range in year 2, my fleet Z would have been targeting it directly (instead of Deep Space), and I would not have gotten the standard "appears to have outrun the range of your scanners" message. But I have not tested that.)
In other words, it seems to take an extra turn for the waypoint location to update on the map when a fleet you are tracking jumps through a wormhole and is still in scanner range.
[Updated on: Tue, 16 September 2014 16:11]
What we need's a few good taters.Report message to a moderator
|
|
|
|
|
| Re: Tracking a fleet through a wormhole |
Fri, 19 September 2014 12:16  |
|
| skoormit |
| Lieutenant |
Messages: 665
Registered: July 2008
Location: Alabama | |
|
iztok wrote on Fri, 19 September 2014 04:32Hi!
> it seems to take an extra turn for the waypoint location to update ...
Umm, no. This is the consequence that the pursuing fleet can't "automatically" follow target's fleet through WH.
The behavior you described is known - moving through WH "breaks" interception. If there's a WH near a fleet I'd really like to intercept, I usually send two fleets - one for the target fleet, the second one goes through WH.
BR, Iztok
I know that Fleet Z can't follow Fleet F through the WH in year 1.
It was interesting to me that, in year 1, Fleet Z's waypoint was pointing to the place where Fleet F entered the wormhole, and then in year 2 Fleet Z's waypoint was pointing to the actual location of Fleet F.
I'm glad this behavior is known. Regardless, perhaps my posting it here will prove helpful to someone in the future.
Cheers.
What we need's a few good taters.Report message to a moderator
|
|
|
|
Members
Search
Help
Register
Login
Home
