I really hoped that there was a better solution than that. That means it needs to be called in a for-each loop to have it operate over a set of sprites.

Thanks though, I'll stop looking for the correct way to deal with them.

When I call a function from within an event, it doesn't use the event's filtering context and so selects all types.

https://drive.google.com/file/d/1NI-hMiXB-6pyWLQ3UQFIbpZn9nSx7UnC

How should I call functions?

I think your left and right are the wrong way around though.

Thanks Asmodean. It had just clicked that I was making it insanely more complicated than it needed to be.

Your suggestion if really nice and clean.

Aye. One was A C and the other B. The still fired the collision event.

OK, that makes some sense. It also explains what those angle compactors are there for.

I'm trying to tell whether a sprite is colliding with another sprite from the top, left, right or bottom. I thought I could it with a combination of the angle of movement and the size/position of the sprites (assuming they don't rotate).

It's a fairly involved calculation, so before I went too far down that route, is there a simple built in thing that can tell me the position where on a sprite a collision occurred?

Failing that, is there a way to get the angle of motion from a sprite immediately before a collision? Getting it on the collision returns 0 (which is technically correct and useless in this context).

Demo: https://drive.google.com/open?id=1pFre_1_kpMwmhPsk4iXKhXkoITL7qgAv

Can I use Jump-thru as a one-way door? such that I can fall through it, but not jump up it?

Am I using it wrong? I'd have thought that these wouldn't collide because they have different tags:

Found it! It's hidden away in the Misc section. Of course.

Cheers dop2000,

Where is that filter?