Best method of hit detection for large projectiles?

[sloomingbla]

When it comes to non-hitscan projectiles, if they are a large size what would be the best method of hit detection? .Touch seems as though it would be way too buggy, and if the projectile is large enough raycasting from the corners/center wouldn’t work either (which is also a messy solution anyways). Findinregion3 could possibly work, but seems like a laggy solution.

I still haven’t decided on the movement method for the projectile either, but I figure it would probably just be cframed client side or use a bodymover.

Thanks in advance for the suggestions ^.^

[Operatik]

What's the most efficient way to make a slow moving projectile that can hit multiple people, but only once each?

So after deliberating and testing every option I’ve been given so far as I can recall (whitelisted ontouch, gettouching parts, Wulfes Raycasting idea) I’ve come to an unsteady solution. The raycasting idea is entirely a bust from the get go since we aren’t making a bullet, we’re making a fireball. You can’t expand the hit area for a raycast, it hits the exact area it’s told to (or whatever might be blocking it). As a result we made a fancy small slow moving bullet, not a fireball. GetTouching p…

Probably somewhere between the lines in the topic above. If statement would probably stop the touch function from running the chunk of code.

[0x_7777]

Depending on your projectile geometry, you could simply approximate the projectile as a rectangle and every character as a point. Then, for every cycle, simply check if a character’s point is inside the rectangle.

If your projectile geometry does not allow you to approximate it as a rectangle, and your desired fidelity requires it, you could create a convex hull of your projectile. Then, every game cycle, perform a transform on all hull points (due to projectile movement), and check if the point is inside the hull.