| Steve-Law | |||||
| What are the rules of order for processing turns? i.e. you have some ships that have pending orders from previous days' turns, some starbases due for maintenance, and submitted turns waiting to be processed (ships and starbases). (Also, I suppose, if it matters, are platforms classed as starbases or ships for the processing order rules, what about GPs, Agents/operatives, politicals?) As a further/specific example, let's say I had orders in today for a ship to dock at a starbase, but it ran out of TUs. It wil have enough to dock tomorrow. But the starbase is due for its maintenance day tomorrow (so I can't use the process after setting). Will the ship be there in time for the starbase to issue orders to it? (if any of that makes sense?) | |||||
| Rob Alexander | |||||
| Hi, I remember there being a list in one of David's proposals, but I think he's deleted it. However, it seems to be: [*deleted by me because it was wrong - see David's answer below*] rob | |||||
| Kragnost | |||||
| From experience I think its: 1) Starbases due maintenance run orders 2) Starbase maintenance runs 3) All ships and other positions run | |||||
| Steve-Law | |||||
| I think the actual maintenance is ran last. Can't be sure though. | |||||
| Kragnost | |||||
| If you have a ship going to interact with a starbase that is due maintenance that day and there are orders submitted for the starbase as well the order is: 1) Starbase orders run 2) Starbase maintenance run 3) Ship orders run This is what I see almost every day. | |||||
| Steve-Law | |||||
| Is this the same if the ship's orders are pending though? That's the bit I'm unsure of. | |||||
| David Bethel | |||||
| Order of things is [1] Weekly updates: Each position updates once per week and this includes starbase production etc. Orders for starbases and politicals are run here also if they are updating. [2] Runs: All other orders are run after the above, the orders are run in a random order which maintains sequence (apart from the known issue) [3] Battles [4] Update of Political Issues [5] Manifest section of all reports (this also prints any changes in between turn scans) It will most likely change to (not sure when) [1] All orders [2] Battles [3] Weekly updates (inc pol issue update) [4] Manifest | |||||
| Andy | |||||
| I like the new order sequence as that will allow ship orders to be done before starbase updates. If you deliver something to a starbase on te say of update, I would want to see it reflected in the starbase report. Andy | |||||
| Steve-Law | |||||
| Conversely though, if the starbase delivers to the ship it wouldn't show on the ship report. | |||||
| David Bethel | |||||
But this happens already, manifests are done after all turns are run and any actions that occur between the positions turn been run and the manifest being printed are reported on the turn (after orders/ before manifest)
Same as above. |