Is this usable for fists? Do i just make attachments on the arm
2 Likes
Iām having some trouble with the hitbox being behind a moving player. Any way to solve this?
looks very useful! i might use this in future
Has anyone else gotten a bug where cloning a part that currently has a hitbox, applying a hitbox to the cloned part, then destroying the hitbox on the part that was cloned from? Usually results in the hitbox on the cloned part returning as nil.
I canāt say for certain, but if I had to guess Iād say you were casting the hitbox on the server. For more smoothness, try casting it on the client and then performing sanity checks on the server (is the hit object close enough, is it unobstructed, etc.) to make sure any detected hits are valid.
1 Like
Hey! Iāve been using this module for almost a year, but now I have this issue: Iām casting a hitbox (a short one, ~0.5 seconds long) in a tweened part (it is actually in a tool, which is in a tweened character) and the hitbox seems pretty delayed (I enabled visualizer), it isnāt even THAT quick (3 studs forward in, as I said, ~0.5 seconds).
There is any way to fix this or making the hitbox update quicker? I think that client casting is way too risky.
EDIT: also, just discovered another big issue which is that hitbox is not starting, I think this is happening because of this is a combo (which can be up to 2 hitboxes per second, each one 0.5 long), but Iām not sure since the hitbox is actually stopped before the next one in started (I already used some prints and similar to check); seems to be fixed if I stop the hitbox sooner, but anyways this shouldnāt happen (since Iām literally also stopping the hitbox right before starting a ānewā one).
Thank you for reading!
Hey! Iām sorry for my previous reply, I thought you were actually replying to another topic of mine.
I donāt know anything about spatial queries, do you have some API or topic to read more about it?
I guess the other options are: part hitbox (which I hate but may fit more this new type of game Iām thinking about) or .Touched.
Thank you for replying!
1 Like
You can read more about it here Introducing OverlapParams - New Spatial Query API - Updates / Announcements - DevForum | Roblox
2 Likes
Thanks, this will really help me with a sword system I am making! 
if you have a debug setting, itās gonna hide the hitbox
Can it be used to detect a part, not just a humanoid? For example, when the player uses a sword and hits a wall, can the OnHit event know that it hit a wall?
Edit: OK i found out
How would i detect where raycast has collided with a part so i can place a particle emitter at position where it collided?
Iām already using PartMode though. Oh wait, nevermind I was using Default lol
Is it just me, or is the āOnHitā event pretty unreliable for constantly active hitboxes. I have a forever lingering hitbox that is just there to detect a specific part, but its detection stops working when any other hitbox collides with that part. Refreshing the hitbox via HitStop and HitStart doesnāt seem to fix the problem either. Keep in mind that this is all client side. Iāve done my best to ensure it wasnāt my code that was dropping the signal, and Iāve found out that the raycast still detects the part, but the āOnHitā event simply doesnāt fire. And yes, I have the signaltype set to āDefaultā, so that it fires to multiple connections. As of now, Iām somewhat sure this is a bug, perhaps a byproduct of āGoodSignalā, nevertheless I hope you can get back to me on this @TeamSwordphin.
Yeah, Itās always been set to āBypassā. As I said, Iām pretty sure this is a bug with something related to āGoodSignalā.
Has anyone experienced an error similar to this?? Iāve been trying to integrate the module in our game for our melee weapons, works great as far as hit detection goes but this error keeps popping up sometimes. I canāt figure out a pattern as to why itās appearing. Can anyone shed some light on this??
Iām creating a hitbox based on the SetPoints function and Iām destroying it after a while. The main issue is that the Hitbox:Destroy() function sometimes is working properly, other times this error appears.
If more information are needed, please let me know!
Hello! Iām having issues with getting the hitbox to ignore players. I am trying to get it to ignore all players, but still hit and deal damage to NPCs. How would I go about defining that? Any help would be much appreciated!
make all players on the same team
2 Likes