Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Enable undeploy-and-<do something> orders for deployed actors #16607
Abbreviated history of the evolution between #16142 and now:
Problem: (from #16142) handing activities between actors is going to cause maintenance issues.
Problem: Using alt to activate the undeploy orders clashes with
Problem: Further discussion about the cursor problem in Discord and #13039 made a reasonable argument that the alternate transport mode has been partly superseded by the newly fixed ability to queue multiple enter orders, and on balance it is better to sacrifice that feature than to bodge this one.
If there is a consensus that this is the wrong call wrt AlternateTransportMode I can drop the last two commits - but please test the behaviour on the 4th vs 6th commits before arguing for this. IMO the current behaviour feels much nicer.
Punsho left a comment
I did some testing in ra and ts, conyard undeploy is bugged. If tania places a c4 on a conyard and then it's undeployed using this method no animation will be played and conyard will instantly turn into an mcv. Same goes for chrono vortex.
tovl left a comment
Fixed both issues.
There is a problem with "attack ground" - if a deployed unit is ordered to attack ground outside of firing range it would undeploy, move into range and just stop.
I'm not sure what the behavior should be here. Either one of these:
The last one seems most useful because the player probably would not want to undeploy when target is out of range (imagine a group of deployed artilery units). This however goes against how the force move modifier works.