I don’t really. That is up to the end-user to implement, as there’s no perfect solution for every game (see the Important notice under How to Use).
For my game, I sanity check by backtracking the animation on server, get the attachment the client raycast from, and calculate how far off the line the sent position was.
The “line” is the direction between the backtracked attachment’s positions.
Also: if you don’t feel comfortable making your hitboxes more lenient in exchange for ping compensation, you can always just set no owner for the ClientCaster and instead just calculate it on server.
tht kinda just beats the point of me shifting 20 different scripts to use this and also i feel this is just a version of raycasthitbox which is harder to use and has lesser features… but its alr i cn tell u put a lot of work in it
It’s up to you to determine how useful you deem it. I’ve actually been using Swordphin’s hitbox before, but my playerbase complained about hitboxes missing and being inaccurate, so I ended up making ClientCast to fit for these new fits. While it’s hard to re-create complex systems like in CS:GO where they accurately backtrack from where the client shot due to Roblox’s packets being unordered, it is nevertheless industry practice to calculate hitboxes on client, and validate them on server - and that’s for a reason.
I know, but it’s still more cumbersome than using this module. I’ve limited knowledge on how using swordphin’s module to support client context would work, but at least with ClientCast you don’t need to setup anything on client - all you need to do is just Caster:SetOwner(Player), and you’re set.
Switched to ClientCast as stated. It was only a year later that I got more paranoid about exploiters being able to slightly increase their hitboxes, and so I improved the security through implementing backtracking.
As it is now, probably a bad idea. I’m too unmotivated to continue developing any projects right now, so only hope would be that someone would make a fork to add this:
I’ve read around and had an interest in using this for my game with large, fast moving projectile orbs. I have tried to implement many solutions but due to replication lag it seems impossible to make these fast projectiles have accurate hitboxes if not on the client.
However, these projectiles come from an enemy boss and I am unsure of the thought process I can take to ensure that exploiters can’t just delete the projectiles and their hitboxes to immunize themselves. Would you be willing to give me any insight into what to do about this? I don’t know if a backtracking method like you’ve described would work if a client could just completely delete the hitbox and prevent any calls to do damage from happening at all.
Why would your hitboxes have replication lag? You should follow a structure where the server creates a hit box, and the client creates effects. The server should not need to replicate anything other than sending the client a remote to create the effects on client.
Addressed a bug with Caster::Destroy accidentally destroying the whole object - this was a bug related to how debug trails were cleaned up. cc @rohangulapa
Destroy fully destroys the caster object, cleaning everything up and not letting it be used again. Stop allows you to temporarily stop the hitbox, and then resume it again by using Start.
You can think of it as Part:Destroy() vs temporarily parenting the part to somewhere else.
Thank you for the reply. Do I need to edit the module or is there a way to show the debugrays when :Start() is called. The same applies for when :Stop() is called to hide the rays? I thought
ClientCast.new(Instance, RaycastParams.new())
would initialize and not activate the rays until :Start() has been called.
I don’t really understand your issue. Are you saying that the debug rays are being shown even before Start is called? or are you saying you want the debug rays to show without having to call Start? Or something else completely?
That’s weird - shouldn’t happen. Go into the main module and in the Settings table, set the debug value to false. If that doesn’t work, then try calling :StopDebug() right after creating the caster.
