doc on Formations#783
Conversation
|
Ugh finally done... This turned out to one hell of a document. |
1bf9c1c to
aceaf61
Compare
| subformation[2].order_units(formation_type) | ||
| subformation[3].order_units(formation_type) | ||
| subformation[4].order_units(formation_type) | ||
| subformation[5].order_units(formation_type) |
There was a problem hiding this comment.
heh, that is the interesting part :) how does the ordering actually work? and how is it combined with pathfinding? might be something for another pull-request though.
There was a problem hiding this comment.
shouldn't be that hard to come up with and algorithm. I'll have a look and write it all down..
| case 912: | ||
| case 947: subformation[1].add(u) | ||
| break(); | ||
| case 906: subformation[2].add(u) |
There was a problem hiding this comment.
can you pls do:
for unit u in player_selection do {
switch (u.GROUP_ID) {
case 912:
case 947: subformation[1].add(u);
break;
case 906: subformation[2].add(u);
....this is more conformant with our code style then.
| .1.2.3.3.3.2.1. | ||
| .1.2.2.2.2.2.1. | ||
| .1.1.1.1.1.1.1. | ||
| ......... |
bcc70e4 to
af94283
Compare
af94283 to
58bbceb
Compare
|
I've added pseudocode for the |
|
Ready to merge? |
|
@TheJJ yup :) |
This PR aims to summarize all results from #705 which @Piruzzolo and me have discovered. I think nobody wants to read through the lengthy discussion to get something done.