What method would you use to make a large, moving hitbox?

Help and Feedback Scripting Support
#1

So far i’ve use RaycastHitBox and Region3 but none of them would be effective for what i’m trying to achieve rn.

#2

Would using a large basepart with an align position or a linear velocity work? Then all you need to do is add a Touched event through a script.

1 Like
#3

Yeah i know the default answer is Touched event, but it sucks, i was looking for other methods

#4

Try the spatial query stuff, like workspace:GetPartsInPart

2 Likes
#5

How is that used in a moving part?

#6

Call the spatial query on an interval. The lower the interval, the more frequent you check for collision.

local interval = 0.5 -- Time between checks (in seconds)

-- Loop that constantly checks for collision on a part
while true do
     task.wait(interval)
     local results = workspace:GetPartsInPart(PART) -- Returns a table with parts it hit.
end
1 Like
#7

would making loops for the hitboxes affect the performance negatively? The loops would have to be tight if i want a accurate hitbox, and there would be multiple of these hitboxes in the game at the same time too

#8

You can run the queries several times per frame without much of an effect (or any at all) from my experience.

If your hitboxes are box-shaped, you can use GetPartBoundsInBox instead of GetPartsInPart for more performance but less accuracy (it checks bounding boxes instead of the actual geometry).

3 Likes
#9

Do it on a runservice event like heartbeat, since it likely won’t move more than once a frame. Also yea, performance should be fine unless you do an insane amount in the thousands or something in a frame.

#10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.