"Clear defences" doesen't work.

[oJy]

I chose clear defences on a enemy colony and all my fleets did was.

Engage space bastion untill hull was around 20% then stop and just do nothing while the rest of the space bastions shoots at my ships. They do engage some enemy fleets that might come and defend afterwards. But they completly missed the point of clearing the defenses.

However, if i enable "war missions" in empire policy they go berserk and actually do what they are suppost to. They will bombard and genocide everything in their path. I had to manualy take controll of my fleets to stop them from commiting relentles genocide. It's pretty anyoing that you hafto babysit your fleets, otherwise they will do something stupid.

[Nightskies]

*Major edits done.

If your fleet was on Manual, the default engagement range is set to Nearby (5000). They will not engage other bastions that are more than 5000 away if left to that default setting, even if they're getting shot at.

They typically start engaging other targets when the current target is about to blow, a method to reduce overkill. Even a manually controlled fleet will do this to some degree.

This is an expected behavior of less-than-"Location" engagement range when engaging a non-specific Attack Target like a colony. This command does not override engagement range.

They should not be idling if enemies are in that range. Assuming you are at war with the target.

If they are idling with targets in range, try saving and restarting the game. If they still idle, consider if the system is being overworked: do research projects complete about when expected, or is it delayed by a month or more; if so, system is overloaded, consider slowing the game down or making a new, smaller galaxy to play with.

If they are inexplicably not engaging targets in range when they should and the system isn't overloaded, please make a bug report.

[oJy]

Originally posted by Nightskies:

*Major edits done.

If your fleet was on Manual, the default engagement range is set to Nearby (5000). They will not engage other bastions that are more than 5000 away if left to that default setting, even if they're getting shot at.

They typically start engaging other targets when the current target is about to blow, a method to reduce overkill. Even a manually controlled fleet will do this to some degree.

This is an expected behavior of less-than-"Location" engagement range when engaging a non-specific Attack Target like a colony. This command does not override engagement range.

They should not be idling if enemies are in that range. Assuming you are at war with the target.

If they are idling with targets in range, try saving and restarting the game. If they still idle, consider if the system is being overworked: do research projects complete about when expected, or is it delayed by a month or more; if so, system is overloaded, consider slowing the game down or making a new, smaller galaxy to play with.

If they are inexplicably not engaging targets in range when they should and the system isn't overloaded, please make a bug report.

Hi, my fleets was on automatic, i'm not sure you even can que "clear defences" on manual. Considering it was around mid game the system shoulden't have been overworked. Do you just restart whenever it's overworked?

I also would encounter problems with fleets not engaging other fleets after the first enemy ship was destroyed in early game. That was on manual however. The ships would idle instead. It was the same for the enemy fleet.

Also, if empire policy is set to soften up targets, fleets shoulden't bombard any longer then 50% of defences destroyed. My fleets would not stop bombardment untill defences are nearly destroyed.

[Nightskies]

Restarting is a good first shot at fixing bugs. For example, a ship that repairs itself but remains unresponsive: just restart, and the ship will reset its state and be responsive again. Sometimes reloading the game does the trick, but excessive reloading can cause problems too.

I haven't really tried the bombardment policies yet. Always have manually controlled bombardment. I'd suggest getting a save of the fleet bombing far more than specified in the policies and send that as a bug report on Discord or in tech support.

Entire fleets idling when they should be fighting, *as far as I've seen*, only happens when the system is overloaded or when the engagement range is too small. If its only a few ships idling, don't mind it too much- they're still fighting, just not very efficiently.

In other words, if an entire fleet is idling and it isn't one of those two cases and restarting doesn't fix it, also make that as a bug report. Unless someone else has seen that and can weigh in with another possible cause!

Just to be clear though, you're not getting a feeling the game is bogging down in midgame in any other way, right? Someone else said they were getting that (I'm not observing that).