Matrix Games Forums

Platform: Steam
Build version: started with v1.1.8.7 Beta
Severity: Medium
Annoyance factor: Medium
Confusion for new players: High
Saved game:
While 1st Fleet, an automated attack fleet, was taking care of 2 Gravillex in the Perilous Cauldron system (black hole), the game also assigned 2nd Fleet, my other attack fleet, to the same threat (2nd Fleet is also automated; it was at the capital, its home base).

Not only was assigning a second fleet not necessary (1st Fleet easily took care of the problem). But now that the threat has been eliminated, 2nd Fleet is still going to the black hole!


I've seen similar behaviors a few times in my current game and in my previous one.

Thanks, we'll take a look.

I have been playing a game using version 1.1.8.7, and 9 attack fleets keep being assigned to the same targets that one ship from one fleet could easily solo.

This has been an ongoing issue for a while now. It's happened in every version of the game I can remember.

I'm fairly sure DW:U had a smarter fleet attack assignment. Sometimes, you would see multiple fleets attacking one target. At other times, they would all attack multiple targets simultaneously.

StormingKiwi wrote: Sat Jan 13, 2024 3:45 am I have been playing a game using version 1.1.8.7, and 9 attack fleets keep being assigned to the same targets that one ship from one fleet could easily solo.

This has been an ongoing issue for a while now. It's happened in every version of the game I can remember.

I'm fairly sure DW:U had a smarter fleet attack assignment. Sometimes, you would see multiple fleets attacking one target. At other times, they would all attack multiple targets simultaneously.

We recently released 1.2.0.0 as a public beta. Have you been seeing the same behavior on that version? If so, please upload a save.

MaximKI wrote: Tue Jan 16, 2024 8:11 pm

StormingKiwi wrote: Sat Jan 13, 2024 3:45 am I have been playing a game using version 1.1.8.7, and 9 attack fleets keep being assigned to the same targets that one ship from one fleet could easily solo.

This has been an ongoing issue for a while now. It's happened in every version of the game I can remember.

I'm fairly sure DW:U had a smarter fleet attack assignment. Sometimes, you would see multiple fleets attacking one target. At other times, they would all attack multiple targets simultaneously.

We recently released 1.2.0.0 as a public beta. Have you been seeing the same behavior on that version? If so, please upload a save.

I am fairly sure I have, yes.

Which issue - investigate dangerous locations taking numerous fleets, or queued attacks against Enemy Targets taking numerous fleets, or both issues?

Has either been addressed in the latest patch?

If you have saves for both issues that would be great.

We've made many improvements to fleet logic and behavior, though there are some areas that we may have missed and are working wrap those up.

Here are saves from a game that started in 1.2.0.2 and was left to run almost entirely under automated control.

The player/automated "Teekan Testers" and the Haakonish Astral Enclave.

Four fleets from the Teekan Testers are stationed at a refuelling base near the border, at Kandumar 3 Mining Station. 5 Haakonish targets are queued. The fleets become allocated to all attack the same research station. The Boskara destroyed that, so these fleets were all reallocated to attack the next research station. There are saves of targets queued and targets allocated. I declared war just after battle was joined.

There is a third save from later in the war - where two fleets have been allocated to attacking Astra Station. Using that save, focus on the invasion fleets. One is attacking a planet, one is loading troops. When that mission is completed, it is also allocated to attack Sondare 1 but the invasion concludes before it gets there.

In keeping with the OP, one fleet would have been sufficient for each of the four scenarios presented, so four fleets could have gone and attacked four targets, and one invasion fleet could have been kept in reserve.

I have not noticed the issue for dangerous locations in 1.2.0.2.

Thanks for the info! We'll investigate.