Troubleshooting
How do I keep finding Phantom Battery after it moves?
Phantom Battery can relocate during the engagement, while Emergency Move can also make your own firing origin stale.
Quick answer
Treat both sides of the geometry as changeable. After Emergency Move, rebuild or narrow down your Nest's current firing origin with multiple Position Reports. Gather fresh reconnaissance, deal with enemy Spotters when useful, acquire a fresh Phantom position, and fire a concentrated AP salvo. If Phantom relocates, discard the old target solution and reacquire it before firing again.
Relocation workflow corroboratedCorroborated scopeChecked Aug 14, 2026
The current reacquisition loop is supported at strategy level. Exact post-Patch #4 timing, spawn, route, and damage mechanics remain unresolved.
Version context: Current post-Patch #4 workflow corroborated; balance-sensitive values intentionally excluded
Still uncertain
- Exact post-Patch #4 counter-battery timers and time gains
- Exact Phantom spawn, route, and relocation rules
- Exact reconnaissance freshness duration
- Exact current hit count and ammunition comparison
Evidence and verification context
- Official Patch #4 — Aug 12, 2026: Establishes build 1618 as the current baseline and explicitly records a Phantom Battery balance change. It does not establish the omitted exact values.
- Current post-Patch #4 community discussion: Research reviewed on Aug 14, 2026 supports the broad Emergency Move, Position Report, reconnaissance/Spotter, fresh acquisition, concentrated AP, and reacquisition loop.
- Full-release pre-Patch #4 community and developer material: Provides historical corroboration only. Balance-sensitive timers, gains, routes, and spawn assumptions are not presented as current facts.
Scoped to version 1.0, Patch #4 / build 1618 research. The workflow is corroborated, but exact timers, time gains, routes, spawn coordinates, reconnaissance freshness, hit counts, and post-patch balance values are not claimed.
Run the reacquisition loop
Recover your firing origin
After Emergency Move, start with multiple independent Position Reports from known references. Do not trust firing geometry built from the pre-move Nest position.
Gather fresh target information
Use reconnaissance or observers to search again. Enemy Spotters can be searched for and destroyed when that helps the strategy.
Acquire a current Phantom position
Build the next firing solution only from the current Nest origin and fresh target information, not an earlier Phantom location.
Use concentrated AP fire
Current community strategies use concentrated or twin AP fire. Treat this as a practical strategy, not a guaranteed hit count or internal damage rule.
Reacquire after relocation
When Phantom moves, discard the old target solution. Search again and rebuild the solution before the next salvo.
Still stuck?
Two Position Reports still leave ambiguous geometry
Get another independent report instead of forcing one exact Nest position. The added constraint is safer than assuming two reports always resolve the origin.
I found Phantom earlier, but it moved
Treat the earlier location and firing solution as stale. Reacquire a fresh position before firing again.
An older guide gives exact timers or a fixed route
Do not plan around those values as current. Patch #4 changed Phantom Battery balance, and this page intentionally omits unverified post-patch timers, routes, and spawn assumptions.
Common mistakes
- Reusing a firing solution after either the Nest or Phantom has moved.
- Forcing two Position Reports into one exact origin when the geometry remains ambiguous.
- Treating a pre-Patch #4 timer, route, spawn, or time gain as current.
- Turning repeated community AP strategy into a guaranteed hit count or ammunition hierarchy.
Why this works
Current post-Patch #4 community discussion corroborates the broad Emergency Move, Position Report, reconnaissance/Spotter, fresh Phantom acquisition, concentrated AP fire, and reacquisition loop. Official Patch #4 notes establish that the mission balance changed, so earlier exact timers, gains, routes, and spawn assumptions are deliberately excluded. The stable value here is the stale-geometry model: your firing origin and the enemy position can each require reacquisition.