View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0025257 | AI War 2 | Bug - Gameplay | Jun 15, 2021 12:03 pm | Jun 17, 2021 6:55 pm | |
| Reporter | Ecthelon | Assigned To | Chris_McElligottPark | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.104 Option For A Distributed Economy | ||||
| Fixed in Version | 3.202 General Bugfixing | ||||
| Summary | 0025257: Telling a fleet to stop on the planet its on in galaxy view doesn't have any effect | ||||
| Description | If you order a fleet to move to another planet and it's on its way there, I often change my mind and want the fleet to stop where it is. However, there doesn't seem to be a way of doing this from the galaxy view. If you select the fleet and order it to move to the planet its already on, it totally ignores this order and continues with its previous instructions. I'm not sure if this is a "bug" but I would expect the fleet to cancel its move order in this scenario and stay where it was. If you have various fleets moving around and you select all of them, telling them to move to a planet, any fleets on that planet already will ignore the order and continue with what they were doing before, while all the other fleets act as expected. tl:dr in galaxy view, if a fleet is moving from planet A to planet C and must transit through B, but wants to stop at B while on B, you must exit galaxy view and issue a move order in the planet view. | ||||
| Tags | No tags attached. | ||||
|
|
Note that this issue has an easy workaround: tab into the planet with the fleet and issue a move command for that fleet |
|
|
That is true, while a little inconvenient if trying to manage multiple fleets around the galaxy. A problem I have hit multiple times though is if I select all my fleets and tell them to move to a planet, I may not notice that one of them was already passing through that planet. Hence that one fleet can end up miles away from the others before I notice. |
|
|
I think backspace also clears the current orders, but yeah. And I do see the core of the problem that you're describing, for sure. |
|
|
Thanks! * If you are on the galaxy map and giving ships orders between planets (say, a group of ships from planet A to planet B, and they are all on planet A right now), then previously if you were to give a conflicting order to the planet they are already on (hey you ships on planet A, go to planet A), then they would just ignore those orders and keep going to planet B. ** Now, in the even that these ships are planning to leave the planet, all of their orders get cleared. So the example ships above would stop doing anything and stay on planet A. ** There's a third category of ships -- those on planet A, but that were never planning on leaving planet A in the first place, and which you told to do something else, like shoot some guy. These ships will carry on shooting the guy, because they are both already on the planet you said, and have no travel orders to go elsewhere, so they may as well disregard what you said since it has no meaning. *** The fourth sub-category of ships who have some other orders and THEN a move order (hey you ships on planet A: shoot that guy, then go to planet B) WILL have all their orders cleared, including the non-travel-related ones, when you order them to the planet they are already one. This seems excessively niche. ** In testing, this now works as one would respect, is the TLDR. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Jun 15, 2021 12:03 pm | Ecthelon | New Issue | |
| Jun 15, 2021 12:04 pm | Ecthelon | Description Updated | |
| Jun 15, 2021 12:05 pm | BadgerBadger | Note Added: 0062099 | |
| Jun 15, 2021 12:07 pm | Ecthelon | Note Added: 0062100 | |
| Jun 17, 2021 6:34 pm | Chris_McElligottPark | Note Added: 0062137 | |
| Jun 17, 2021 6:55 pm | Chris_McElligottPark | Assigned To | => Chris_McElligottPark |
| Jun 17, 2021 6:55 pm | Chris_McElligottPark | Status | new => resolved |
| Jun 17, 2021 6:55 pm | Chris_McElligottPark | Resolution | open => fixed |
| Jun 17, 2021 6:55 pm | Chris_McElligottPark | Fixed in Version | => 3.202 General Bugfixing |
| Jun 17, 2021 6:55 pm | Chris_McElligottPark | Note Added: 0062138 |
