Currently, utilizing GetPartsInPart with OverlapParams lacks sufficient granularity, specifically in filtering Parts based on certain properties like CanQuery. This limitation is hindering development, especially for custom .Touched and .TouchEnded detection systems.
Problem Statement
At present, it’s challenging to exclusively select Parts with CanQuery enabled using OverlapParams. This lack of control complicates efforts to implement precise interaction systems, particularly in scenarios involving Player.Character body parts.
Proposed Solution
Introduce enhanced functionality to OverlapParams that allows developers to specify which Part properties should be considered when retrieving Parts. For instance:
- Case 1: Retrieve only parts with CanQuery = true.
- Case 2: Retrieve parts with CanCollide = true and CanTouch = true only.
Use Case
I require a robust solution for custom .Touched and .TouchEnded detection, specifically for detecting interactions with Player.Character body parts such as UpperTorso and LowerTorso. These parts inherently possess CanCollide = true and cannot be altered, complicating the detection process. The current workaround involves detecting movements of Player.Character’s HumanoidRootPart within other Parts, which yields accurate but less efficient results due to unavoidable detection of UpperTorso and LowerTorso.
Additional Context
Enhancing OverlapParams to support selective property filtering would significantly improve the precision and efficiency of interaction detection systems within Roblox games. This feature would empower developers to create more immersive and responsive gameplay experiences without the current constraints.
This enhancement would greatly benefit developers aiming to implement sophisticated interaction mechanics within Roblox, enhancing both gameplay quality and developer productivity.