Using 'e' to clear away rubble with a shovel is too cumbersome when not under threat #12114
Labels
<Enhancement / Feature>
New features, or enhancements on existing
Info / User Interface
Game - player communication, menus, etc.
<Suggestion / Discussion>
Talk it out before implementing
Let's assume the fight is over and the character is not threatened by anything. In a situation like that, the game should relax the need for micromanagement.
So I suggest that if I hit 'e' once, it will highlight the tiles you can examine, like now. But then if instead of a direction I hit 'e' again, it will perform an action on all the tiles. Right now this can be tricky or even bad, because the game uses 'e' for so many diverse things. You can use 'e' to look at a list of items on the neighboring tile. Or you can use 'e' to clear away rubble. Or you can use 'e' to interact with a vehicle.
When it comes specifically to clearing away rubble, I'd like to be able to clear it away en-masse, without getting picky about which specific tile right this turn. So maybe the double-e will do something magic if you have a shovel and are surrounded by rubble and are not under threat? Or maybe a more elegant solution is called for. I don't know.
What I do know, is that right now I don't like looking at a 50 tile of rubble or crash site pile up and thinking how many times I'll need to hit 'e'+direction to get through it all. I wish there was an easier way.
Maybe I should be able to select a wide area and say "till all this land in rows" or "clear away all the rubble in this giant 10x5 tiles square." Then I let the game handle the minutia. Then if a monster appears, this process stops and we're back to manual control. Once I have dispatched the monster, there should be a "continue the previous process". So if I was clearing away rubble, the game can take over my character and continue using the shovel to clear it away.
Tilling land and clearing away rubble are the only two tedious things I can think of at the moment that I sometimes may want to do a lot of in a row.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: