Add "Set to" hotbar action for block parameters
I feel that this is missing action on hotbar. We have "increase" and "decrease" actions for almost all block parameters, but there is no way to set to a desired value quickly, aside from going to the terminal, finding the block and then changing it.
Since the hotbar action with argument is already in game (programmable block "run" command asks for argument), I don't think it would be hard to allow action to set a parameter (that can be already manipulated with "increase" and "decrease") to a specified value. It can even use normal text argument (like "run") and do nothing if argument can't be parsed and clamp to max/min if it's outside allowed range.
Advantages:
+ ability to quickly and precisely set parameters on blocks via hotbar instead of pressing increase/decrease action set amount of times, that still adds only roughly to what you want
+ enhance timer block usability, because it can set exact values without assuming and/or using stacks of "increase"/"decrease" actions
Disadvantages:
none I can imagine
I like this feedback
After programmable block has been moved to "experimental mode" using Timer blocks and event controllers has become the new vanilla way to automate staff. I also like it. The limitations you face often have to be overcomed with "clever" overengineering solutions, often leading to dozens of additional timer/event blocks envolved. This suggestion points to an obvious missing fature for when you setup actions.
Some trivial example where it might be used:
* Setting wheels height offset to a specific value, you often need 2 positions, a lower one and a high one, maybe a middle one. I wish I can have just those 2 buttons in hot bar that would always bring the suspentions to exactly desired heigth. There are also much more comples scenarios where you have many different axis you want to fine tune for full loaded wehicle or an empty one, where you just cannot think about olways using increae/decrease as it is not precise and just a mess if you try to controll things that are in more than 1 diffferent groups.
* Controlling complex craines. You often have some complex configurations for many of the rotors/hinges/pistons involved. Here you can easily have an exponential explosion of timer blocks needed for the build.
* Set specific overrides to thrusters, gyros...
In addition I wouldlike to remind about another obviously missing feature: copy/paste all settings of a block to another. So you might have sozens of timer blocks to increase/decrease some value. Now imagine you need to move all them in some other place. Good luck wasting your life on porting all the actions and settings from to another. Even more trivial example: your cockpit sits on a block you want to remove, or you just wanrt to relocate it, ot you want 2,3,4 cockpits all with the same settings and identical hotbars. Again, it is so tedious to reconfigure the same thing more than once. Then thiong aboutrotors, pistons, hinges. Usually many of them share the same setting. The list goes no forewer.
After programmable block has been moved to "experimental mode" using Timer blocks and event controllers has become the new vanilla way to automate staff. I also like it. The limitations you face often have to be overcomed with "clever" overengineering solutions, often leading to dozens of additional timer/event blocks envolved. This suggestion points to an obvious missing fature for when you setup actions.
Some trivial example where it might be used:
* Setting wheels height offset to a specific value, you often need 2 positions, a lower one and a high one, maybe a middle one. I wish I can have just those 2 buttons in hot bar that would always bring the suspentions to exactly desired heigth. There are also much more comples scenarios where you have many different axis you want to fine tune for full loaded wehicle or an empty one, where you just cannot think about olways using increae/decrease as it is not precise and just a mess if you try to controll things that are in more than 1 diffferent groups.
* Controlling complex craines. You often have some complex configurations for many of the rotors/hinges/pistons involved. Here you can easily have an exponential explosion of timer blocks needed for the build.
* Set specific overrides to thrusters, gyros...
In addition I wouldlike to remind about another obviously missing feature: copy/paste all settings of a block to another. So you might have sozens of timer blocks to increase/decrease some value. Now imagine you need to move all them in some other place. Good luck wasting your life on porting all the actions and settings from to another. Even more trivial example: your cockpit sits on a block you want to remove, or you just wanrt to relocate it, ot you want 2,3,4 cockpits all with the same settings and identical hotbars. Again, it is so tedious to reconfigure the same thing more than once. Then thiong aboutrotors, pistons, hinges. Usually many of them share the same setting. The list goes no forewer.
Replies have been locked on this page!