Created a QOL Hitdetection module, would love to hear thoughts on it

[subtle cape]

Would you guys use this?

    local Params = OverlapParams.new()
    Params.FilterDescendantsInstances = {Character}
    
    local HitboxInfo = Hitbox.CreateHitboxInfo()
    HitboxInfo.Size = Vector3.new(7,7,7)
    HitboxInfo.Type = "Box"
    HitboxInfo.OverlapParams = Params
    HitboxInfo.Debug = true
    HitboxInfo.CFrame = Root.CFrame * CFrame.new(0,0, -HitboxInfo.Size.Z/2)
    
    local FilterInfo = Hitbox.CreateFilterInfo()
    FilterInfo.FilterType = "Tag"
    FilterInfo.FilterBy = "Balloon"
    
    local HitboxInstance = Hitbox.new(HitboxInfo, FilterInfo)
    local Hit = HitboxInstance:Create()
    
    print(Hit)```
usage example

filtering is kinda bugged right now but you get the point

hopefully 👀

just fixed it rn actually

will send updated scripts later

[torn plaza]

Idk man, cool concept but I don’t see how it’s any easier than just manually coding in those things you need.

I personally wouldn’t use it over creating my own systems for each need

[grim bridge]

fuck no.

shapecasthitbox exists

[subtle cape]

ye but its unoptimal for certain types of game spatial query is better for most projects rather shapecast most importantly in performance

[grim bridge]

i wont use your module though

there are few features that you will need to implement more

such as signals.

hooks

[subtle cape]

i'm not forcing you to use it, I'm just taking on notes

[grim bridge]

your current module is just basically a wrapper

[grim bridge]

thats why im giving feedbacks?

[subtle cape]

there is no point for signal hitdetection just return a table

[subtle cape]

your first messages don't really indicate that yk

[grim bridge]

there is.

[subtle cape]

and that is?

[grim bridge]

like shapecasthitbox module

it gives u tons of signals

onhit, ondestroy

basically features rich

if u dont know the module

https://devforum.roblox.com/t/shapecasthitbox-for-all-your-melee-needs-v025/3624241

[subtle cape]

I already read the api of the module

its just give you features for handling the destruction of the hitbox

which is basically btw, disconnecting it or, removing it from a table which is used for data in a runservice connection

but I will take that into account lets say a hitbox which stays for certain amount of time then is destroyed, or just creating the hitbox and that hitbox returning information every second

yes

there is alot of customization that could be made

thank you @grim bridge

[grim bridge]

if you want to make your module more safer

separate the constructor and metamethods

for your debug mode

you could probably provide optional part

but your oop implementation is already good

can say it's not bad