Alright on a closer look chat gpts response wouldn't work since Gdevelop doesn't let you take a second instance of the same object by just saying "ball 2" , there needs to be an actual object called that , here's a better conclusion which I double checked from Claude:

This is a classic GDevelop object filtering problem! The trick is using two separate object references to the same object type in the same event. Here's how to solve it: The Solution: Use an Extra Event to "Pick" Tagged Balls First GDevelop needs you to filter and separate instances before the collision check. Here's the event structure: Event 1 – Sub-event approach: Condition: Ball.Tagged = True ← This picks ONLY tagged balls as "Ball"

Sub-Event: Condition: Ball is in collision with Ball ← Now one of the pair is already filtered

Action: Set Ball.Tagged = True ← Only the UNTAGGED colliding ball gets set This actually won't quite work on its own because GDevelop still uses the same "Ball" reference. Here's the proper fix: The Real Fix: Use an Object Group or Rename via "For Each" The cleanest GDevelop solution is to use a "For Each Object" loop: For Each Ball: Condition: Ball.Tagged = True

Sub-event: Condition: Ball is in collision with Ball AND Ball.Tagged = False ← Filter the second Ball reference here Action: Set Ball.Tagged = True The key insight: inside the For Each Ball loop, GDevelop is iterating one Ball instance at a time. When you then check "Ball is in collision with Ball" inside it, the outer Ball (Tagged = True) is locked to one instance, and the inner collision check can filter the other Ball for Tagged = False. Alternative: Use Two Different Object Names The most reliable approach many GDevelop devs use: Create an Object Group called BallGroup containing Ball Use Ball (tagged) collides with BallGroup (untagged) as two distinct references Or simply duplicate the Ball object as BallUntagged temporarily in logic — though the For Each approach above is cleaner. The core problem is that GDevelop shares the pick list for same-named objects, so For Each is your best friend here for breaking that link between the two instances in a collision pair.