Proximity Prompts sink inputs from Context Action Service - There should be a boolean property within Proximity Prompts to disable this

[AerostyleDev]

I’d like to request a super easy-to-implement feature that apparently was already the case before 2021… namely, about this post:

ContextActionService BindAction does not work for keys used by ProximityPrompts

We apologize for not making this change in behavior clear ahead of time. It was an intentional change, as we expect user input to prioritize a nearby ProximityPrompt over a global action triggered with ContextActionService. For a workaround, you may be able to use UserInputService instead of ContextActionService to detect this input even when the input key conflicts with a nearby ProximityPrompt. In order for us to evaluate supporting the old behavior, can you share the use cases where this b…

My request is to simply add a “sink input” boolean property within proximity prompts, to ensure proximity prompts do NOT sink contextactionservice inputs. I’ve been using contextactionservice to make the controls more seamless and easier, but finding out proximity prompts sinks input specifically for contextactionservice has been a great inconvenience… and I’m honestly not sure why this wasn’t done in the first place.

[ZAPOTRO11 (ZAPTheEngineer)]

Welcome to the #help-and-feedback:scripting-support , where you can request help for your script…

if you want to suggest a roblox feature, you need to write it here: #feature-requests