UI mod request, stop base ctrl+k
-
Deny ctrl+K orders when more than certain amount of unit types are selected simultaneously (from 8 to 10 can be default)
this is so players can make sure to stop themself from ctrl+k-ing their base when they rage or something like that.
-
Make it whenever more than a single mex is selected and I’d probably use it just to keep my once every thousand games mistake of ctrl-k all t2 mexes when I meant to only do one from happening.
-
The "ACU Self Destruct Confirm" mod by @HollowSubmarine could be a starting point/inspiration.
-
@exselsior said in UI mod request, stop base ctrl+k:
Make it whenever more than a single mex is selected and I’d probably use it just to keep my once every thousand games mistake of ctrl-k all t2 mexes when I meant to only do one from happening.
interesting idea.... maybe whenever single mex + some other buildings are selected...
like storage or factories... ( i ctrl+k-ed my HQ couple of times by accident when trying to ctrl+k t1 pgens next to it)my idea is only to stop people from ctrl+k their base to ruin the game.
And try to not create problems anywhere else
so people can still ctrl+k part of their army or part of their base to not give veteranicy for example
imho a typical base will have at least 8 types of things...- t1 or t2 mex
- pgens
- ACU
- land fac
- air fac
6-7) pds or units or planes - t1 engies
so people could voluntarily install this mod so they don't ctrl+k their whole base and don't ruin games for other
-
Except for walls, and probably T1 pgens. Since this is how I reclaim them.
-
If you want to stop others from doing it its not a ui mod but a sim mod
-
It has been partially implemented at least in the past it seems. Not sure if it's maintained or working
"ACU Self Destruct Confirm" UI mod -
If someone tries to ctrl-k more than half of their mass in a team game, change the order to "ctrl-k the acu only and nothing else"
Maybe make an exception if there's only a tiny number of units selected, like if someone ctrl-k two monkeylords to reclaim them you don't want that to be interpreted as a "throw"
-
Better to just not execute it then. Don't want to accidentally have your com explode.
