As far as I can understand, this ask is for uniquely addressable collision masks, as today every collision mask is treated as part of the same mask during runtime.
As a reminder, a base expectation for feature requests is that you are searching for existing requests and voting on those instead of making new threads.
Hello y’all
I’m letting you know that this feature request has been closed and merged with Silver’s suggestion: Handle multiple collision masks independently
Future readers: please head to that topic to discuss it further.