Loading...
  OR  Zero-K Name:    Password:   

Post edit history

Better ui for transports project

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
6/3/2018 7:31:39 AMunknownrankShaman before revert after revert
6/3/2018 7:30:33 AMunknownrankShaman before revert after revert
Before After
1 An interpretation of the ferry command could be the following. 1 An interpretation of the ferry command could be the following.
2 \n 2 \n
3 HOLD shift to add waypoints. 3 HOLD shift to add waypoints.
4 \n 4 \n
5 Read these in IssueCommand 5 Read these in IssueCommand
6 \n 6 \n
7 Store these x,y coordinates in an ordered table. 7 Store these x,y coordinates in an ordered table.
8 \n 8 \n
9 orders[1] will be the center of a circle in which we get the nearest self-unit within that circle with no orders and issue a pickup order on said unit. 9 orders[1] will be the center of a circle in which we get the nearest self-unit within that circle with no orders and issue a pickup order on said unit.
10 \n 10 \n
11 orders[#orders] will be the drop off location. 11 orders[#orders] will be the drop off location.
12 \n 12 \n
13 All other values in the orders table will be move points.
14 \n
13 on completion of the drop, issue a reverse orders table worth of move orders. 15 on completion of the drop, issue a reverse orders table worth of move orders.
14 \n 16 \n
15 If the user issues a command to the unit that is not a load or unload unit order and is not part of the reverse lookup coordinate table, clear orders table. 17 If the user issues a command to the unit that is not a load or unload unit order and is not part of the reverse lookup coordinate table, clear orders table.