This one is a bit hard to track down but in some cases, giving a new order won't be obeyed and the fleet will keep doing what it was told before that.
I'm 100% sure this only happens when they're loaded. An unloaded fleet seems to obey multiple move orders just fine.
Description
Details
- Commits
- Restricted Diffusion Commit
- Task Type
- Bug
- Affected Gamemode(s)
- Multiplayer
- Reproducible
- uncertain
- Last tested (version)
- 0.197.46
- Category
- Fleets
- First occurrence (version)
- 0.19618 (Dev)
- OS-Specific
- No
- Hardware-Specific
- No
- Video Card Vendor
- uncertain
1st test:
- issue move order
- press idle
-> doesn't go back to idle
2nd test:
- issue attack order
- issue formation order
- press idle
-> goes back to "move" with sector coordinates of the attack order
A move order is still persistent.
If you issue a "move"/"attack"/"defend" order to a certain sector, and interrupt that with any other order like "formation sentry". It will still remember that move order.
After you set it back to "idle", it will set itself to that old "move" order again. If it was an old "attack"/"defend" order it changes to a "move" order too
<replace this line with the file content>
<replace this line with the file content>
Status | Assigned | Task | ||
---|---|---|---|---|
In Queue | lancake | T1287 Fleets on defend/attack don't move back to assigned sector after combat | ||
Closed | lancake | T1180 fleets get stuck with old orders (sometimes until they are unloaded?) |
Event Timeline
-QA Testing-
- Switching to idle mode doesn't work when they're busy moving/attacking/defending/...
If you put a moving fleet in formation_sentry mode, they'll go in that mode and sit still. Switching to Idle does do something but instead of sitting still in idle, they'll go back to follow their move order.
So switching to idle just makes them continue their last move/attack/defend order if that was interrupted.
- Switching move orders to a new move/attack/defend order only applies after they've been unloaded, otherwise they'll follow their old order.
There might be more stuff but that's what I've noticed so far.
I was trying out the move fleet command while I was aligned to, and inside my ship. I was about to create a bug report, but then I found this ticket.
Version 19592 (current version)
- I'm not able to cancel the move order with the idle order.
- Flipping from move order, to formation sentry, then to idle will make it continue the move order.
- With a group of 3 ships... Interrupting a move order with another move order, to go back to where they started, sometimes causes the ships to get stuck in a zig zag loop. But it doesn't always happen.
- Sometimes the ship take a path that's not quite a strait line, like it's avoiding certain areas, but as far as I can tell, there is nothing in its way.
Can confirm a successful reproduce on 0.19592 on Mac OS X 10.11.2, also affecting single payer.
-QA Testing-
Only the first 2 things Kingofanime mentioned are relevant to this task.
Both of them happen but caused by the same issue, a move order is persistent, any other order only replaces it till that order is done (or you set it to idle). Then it gets set to that move order again to finish it.
Since today's official patch (v0.197.36) came out, I'm no longer seeing any problems with persistent move orders.
Should be correct.
The issue status was set to resolved before release, but as we did not have the time to properly test this, we did not put it to closed yet. =)