1.7.8.2 enhancement - allow cancelling assisting of already started buildings

Add a feature like Supreme Commander where if an engineer is building a building in a queue, and you select that engineer, you can shift-right click to stop it from assisting that building and have it move on to the next building in the queue.

Also add the ability to move building already queued up but not yet build like Supreme Commander.

I know that there's a default off widget that allows you to move move orders around like supcom. I don't think that you can move building commands though, and when I was using it it felt a little off and hackish. I don't think it worked on buildings.

You can cancel orders by re-issueing the same order.(move commands, fight commands, build commands.) But if a building has started, you cannot easily un-queue that building, because the engine will not accept a build command where a nanoframe has already been placed. If I want a coffee to not build an llt somewhere and just continue on a long mexing run, but it had already started the llt, I will often just take the 10 seconds to re-do the whole quewe to leave that llt at 10%. I'm is different for a couple to build a building and repair a nanoframe.

Your first request is just a UI oversight and is fairly standard. You can already cancel a command by shift-queuing an identical command on top of it. The issue in the case of construction is that shift-right clicking issues a repair command, whereas units often have build commands. The commands are distinct so fail to cancel out. I've added a bit of logic to a related widget to implement the correct behaviour.

Commit: https://github.com/ZeroK-RTS/Zero-K/commit/dd3b98fc8af4f8be8e1bdd5bb43e45d3ebcacb5a?w=1


There is a widget for moving commands and construction around. You can enable it through the ingame F10 menu. It has a few rough edges, including clashing with the UI and possibly a performance issue (if my commit from 9 years ago is to be believed). I don't personally see the appeal of moving commands around as I tend to use quite simple queues. The gamestate changes too quickly for much else. Nobody else has put work into making it able to be the default, so it is just sitting there in the menu.