Hi @guavaman, I just bought and started working with this package. Seems really handy and easy to work with. Is there a "Rewired way" to treat triggers as buttons? I mean: is there a built-in way to use button style actions for trigger hardware? So, there might be a GetButtonDown result that is only true for one frame after the trigger crosses some axis threshold. End-users or developers could map button actions to triggers and button handling code would "just work". I can just manage this myself, but I don't want to reinvent something that you already support. EDIT: Separate question: Any assigned input event callback for AddInputEventDelegate fires constantly. This was surprising, due to how the normal C# event subscription pattern works. I can exit early based on the passed data, but seems like the callback should not fire at all if the action didn't occur (if no input changed related to the action) and if the action isn't mapped to anything. Otherwise, this seems to have no advantage over the normal polling paradigm. Am I missing something?