De/active Collision 2d

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.

I’d recommend voting/hearting on that existing request instead of making a duplicate thread: Handle multiple collision masks independently

1 Like