Reply to overlapping hitboxes + touch()
If you don't have an account, just leave the password field blank.
I'm trying to run some code once the hitbox of dink overlaps with the hitbox of another sprite.
Apparently touch is NOT run when the sprite and dinks hitboxes overlap, but when dinks depth dot is INSIDE the sprites hitbox, disregarding dinks hitbox. This becomes very obvious when dink is replaced by a bigger sprite.
My second attempt was using brain 11 (missile) to trigger the function, but that has the same problem but in reverse as it checks if the sprites depth dot is inside dink's (or another sprite's). Offsetting this with range would work if it was square, but not on a thinner rectangle.
Is there really no way to get a callback when two sprite's hitboxes overlap? I notice that even just walking around and collision with hardness is done with just dink's depth dot disregarding dink's hitbox. How would you handle this case?
Apparently touch is NOT run when the sprite and dinks hitboxes overlap, but when dinks depth dot is INSIDE the sprites hitbox, disregarding dinks hitbox. This becomes very obvious when dink is replaced by a bigger sprite.
My second attempt was using brain 11 (missile) to trigger the function, but that has the same problem but in reverse as it checks if the sprites depth dot is inside dink's (or another sprite's). Offsetting this with range would work if it was square, but not on a thinner rectangle.
Is there really no way to get a callback when two sprite's hitboxes overlap? I notice that even just walking around and collision with hardness is done with just dink's depth dot disregarding dink's hitbox. How would you handle this case?
