heh alright, glad I discovered a bug there then!
Will it work with only when A's value is 1 and B's is 0? because this is important.
I just had them both in the same event to show which of both it was picking, as I can't sort it out with the values aswell.
It's like I need to pick then both in the same event, or at different times in the event...
it needs to pick the collided ones, then make sure they both have the correct values, I managed it with one value, but not with both.
+ A (pick) and B (don't pick) overlap
-> A: rotate 10 degrees
+ A (don't pick) and B (pick) overlap
-> B: rotate 10 degrees
so out of the B's with m=0, if one collides with an A, it will unpick all the B's, pick matching A's, then pick the A's out of these with n=1 (and vice versa)
The problem with that is, you put in B.value('m')=0 first, and then it picks the A's in it's container, so it will only count the collision with the A's in it's container, which I don't want it to count! If you put B.value('m')=0 after, there are no B's picked at all at that point, so it's useless.
Maybe it's possible with the function object forgetting picking or something???? (I have no idea lol)
Oh, and I can send you an updated runtime if you're desperate to try this out.
would be nice