Anyone else find this confusing as h3ll. :huh:
I can’t wrap my head around the documentation found here (near bottom):
https://docs.coronalabs.com/daily/guide/physics/collisionDetection/index.html#TOC
Normally I use groupIndex to work my way around collisions, but I’m at a point where I need multiple different collisions to not trigger or trigger… so groupIndex would be too limiting.
Initially I thought the maskBits number reflects what it can collide with that has categoryBits value of less then the maskBits value…
But the more I read, the more confused I get and don’t know how to come up with collision logic that I can understand.
Anyone help me here - not sure how to get this… I can’t be the only one?
OK So I decided to draw out the chart in the example with my own things… think this will help me considerably.
-EDIT - SOLVED. I’d recommend to anyone to draw out the chart and approach it like that. I couldn’t imagine doing that without drawing it out… then figuring the category/maskbits from there.
phew