Hi! I have made a HingeConstraint spinning brick, and have made it into a kill brick using my collection service kill brick script.
My issue though, is that if the player is near, but not touching the brick, it still kills them.
See the video attached. At the end if you scrub through the video you will see that the player doesn’t actually touch the brick, but still dies.
As HingeConstraints use physics, could this be why? Is there a better way to approach spinning kill bricks?
most likely, due to every player having lag
if you want to “avoid” lag, you could try setting the network ownership of the kill brick to the nearest player so that its physics will be influenced under that player’s lag, but that would mean the lag will affect other players instead of the nearest player
but if ur game is soloplayer, doing the method above would work fine
The best way to go about this would be to let the client detect touches on the killbrick for their own character (use the humanoid.Touched event).
What I do in my games for physics objects (including spinners) is clone it on the client and let the client simulate it. This ensures no latency and there won’t be any weird issues if the player has an abnormally slow connection.
This comes at the downside of the spinner not being synced for clients. If you need the spinner to be synced, you can SetNetworkOwner(nil) on the spinner, but still only check for touches on the client.
Thanks for your reply! I have implemented a simple system where the physics models are cloned on each client. They don’t need to be synchronised!
However, wouldn’t letting the client detect touches on killbricks be an easy way for hackers to exploit, since they could just remove whatever it detecting touches on the client?
IIRC exploiters have the ability to not fire touch interests even if it’s a server owned part, plus fly around etc anyway, so you’d still be sacrificing the accuracy of a client-owned part for minimal benefit.
Great to know, thanks so much!