Projectile movement overlap unintended feature or intended bug...

So yea, another day another bug, I guess. We’ve made projectile with proj movement and added overlap collision for it. When it touches (or basicaly goes through) skel mesh it calls overlap for each bone passed. Is it a bug or “intended feature”?

Steps to reproduce: make 2 bps. First one - base character w/ skel mesh (make sure it has phys asset seted up, I’ve used crunch). Second one - any actor w/ proj movement. Bind print on proj begin overlap (opt add print w/ other actor + other comp). Make sure that bouth first actor’s skel mesh and proj’s collision seted up to hit each other and overlap events are being generated.