You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While playing on 1.20.1 1.2.4 I discovered that linking multiple controller buttons to a single link causes the latter to only react to one of the buttons bound. For example:
Here I bound the link to -Y first, then to +Y and lastly to RT:
This is no buttons pressed:
This is RT pressed:
This is -Y pressed:
This is +Y pressed:
This is unlike the Create controller which is capable of such a thing.
I use keyboard if this info is relevant.
Edit: I've just read another issue where this is mentioned, so this issue may be redundant.
The text was updated successfully, but these errors were encountered:
Yes, this is related to a part of what #34 describes
The problem is that axis inputs don't behave the same way than button inputs do, for various technical reasons. I will try to make it behave more like buttons in a future update, so that cases like what you are doing will behave correctly. For now the best thing to do is to only bind button inputs to the redstone link when you want to bind multiple inputs on it
I will still mark this one as a bug, because the other issue talking about it reports two things at once and this problem is not the first thing reported
getItemFromBlock
changed the title
Redstone link only reacts to one of several buttons linked to it
Having multiple axis inputs bound on the same linked controller causes them to incorrectly override each other
Sep 29, 2024
While playing on 1.20.1 1.2.4 I discovered that linking multiple controller buttons to a single link causes the latter to only react to one of the buttons bound. For example:
Here I bound the link to -Y first, then to +Y and lastly to RT:
This is no buttons pressed:
This is RT pressed:
This is -Y pressed:
This is +Y pressed:
This is unlike the Create controller which is capable of such a thing.
I use keyboard if this info is relevant.
Edit: I've just read another issue where this is mentioned, so this issue may be redundant.
The text was updated successfully, but these errors were encountered: