I've come up with a couple alternative paths forward here, because multiple sequence points is a necessity:Īllow linking of Sequencers into Logic Gates: logic gates like OR are already the established way of resolving multiple input signals into one output, so it's natural. The issue that is connected to this is #2540, and it might be a good idea, to discuss this a little bit further.Īn alternative might be a way to dynamically change the values of an sequencer, like for example changing the value of a sequencer to that of a connected sequencer and allow multiple sequencers to be hooked to one sequencer.īutton -> Sequencer A -> Sequencer B -> Rail. I suggest that because of the advantages the bugged Version presents, that the bug should be turned into a feature.
This seems to have been a bug, but everyone thought of it as a feature, since it enabled a vast amount of customisation to mechanisms, and limiting them to only being able to alternate between two states, would limit there usage quite a bit, and would probably be not well recieved, as the "Bugged" Version was vastly superior in its versitility and worked without creating any real problems so far. In the latest Update, 20w27c, there was a change, that limited mechanisms like rails, to only have sequencers.
0 kommentar(er)
