[Client Beta] Input Action System is now available to publish in experiences!

Hello all, the update to exclusive bindings and improved input sinking is out. As a reminder please take these steps if you see issues in your places.

:double_exclamation_mark: Fix: Exclusive Bindings (may require action)

To ensure the Input Action System remains predictable and performant, we are changing how InputBinding handles multiple input sources.

Starting 2/24, an InputBinding will only listen to one input source at a time. If you have multiple sources configured on a single binding instance, the system will now prioritize the KeyCode and ignore the others. This means:

  • For Boolean Actions, If a single binding has both a KeyCode (like [E]) and a UIButton assigned, input from the UIButton will be ignored.
  • For Directional Actions, If a single binding has both a KeyCode (like Thumbstick1) and composite directions (like WASD), input from the composite directions will be ignored.

If either of the above scenarios apply to you, the fix is simple: split the input sources into two separate InputBinding instances.

Before After

227x64227x64 227x81227x81

:double_exclamation_mark: Fix: Improved Input Sinking (may require action)

We’ve fixed a highly requested issue where IAS was not correctly respecting input sinking from other systems like UI and CAS.

Starting 2/24, if you are using IAS to map to Thumbstick1, GamepadA, ButtonR2, or Shift, your actions may be sunk by default character controls in our Player Scripts. This will be resolved once we migrate the default Player Scripts to IAS. If you rely on this functionality before then, you can send us your PlaceID (in this thread, or in a DM to @AykeriZero) and we can flip this flag off for your experience until the new Player Scripts are live.

Thanks for all the feedback and for using IAS.

3 Likes