[Automatons Beta] Event Controller needs to handle more than just one event

[High Templar of Allium Cepa]

If you agree then vote here:
https://support.keenswh.com/spaceengineers/pc/topic/27377-automatons-beta-event-controller-needs-to-handle-more-than-just-one-event

[Yahweh's Grace]

It's more interesting in terms of engineering gameplay that every event needs its own block, that logic takes space. Otherwise a single controller becomes the entire brain of the grid. I understand your desire for convenience, but the point of the game is solving fictive problems.

[High Templar of Allium Cepa]

Originally posted by Xii:

It's more interesting in terms of engineering gameplay that every event needs its own block, that logic takes space. Otherwise a single controller becomes the entire brain of the grid. I understand your desire for convenience, but the point of the game is solving fictive problems.

Well, I just want to save block space for other things. If I want to build a small grid walker, then I can imagine the Event controller can help with triggering joint movement.

Now, with at least 3 joints per leg, plus hip and at least 2 per arm I'm already needing 9 blocks for this.
And more likely there will be another 2 to 6 events to control. That adds up quickly.
If there was the ability to define several events within one controller you could still use one for each event if you have the space, need the challenge or want it better organized in the control menu.

Same goes for drones. The more I can save on space with less controllers the more I can add other functions, AI blocks , hinges, thrusters, pistons, timer blocks, sound blocks, etc and keep a small footprint.

[WildLynx]

Upvoted at Keen site.

[SirSpence]

You can use a timer block to trigger multiple actions. As long as that is the case, limiting to one action doesn't make sense.

The problem is that you are stuck with one input and can't do logic based upon more than one input.

That said, I do think each block should be able to control one "event" that is, one set of inputs and outputs.

[High Templar of Allium Cepa]

Originally posted by SirSpence:

You can use a timer block to trigger multiple actions. As long as that is the case, limiting to one action doesn't make sense.
...
That said, I do think each block should be able to control one "event" that is, one set of inputs and outputs.

Not sure if you are for or against based on that. Regarding timers, of course you can plug in a timer block and trigger several actions that way, but I'm talking about having several events monitored by a single controller. On top of that, I want to be able to set those events using the PB. Just like using the sound block allowed playing only one sound that was selected, but now you can change the selection interactively via script.
It was just too limiting that you needed to put down a block for each sound you wanted to play. But hey, each their own.

[High Templar of Allium Cepa]

Originally posted by WildLynx:

Upvoted at Keen site.

Appreciated!