I know this is old but I recommend calculating what targets are hit by the hitbox on the client because its more responsive and it puts less of a load on the performance of the server. From there, you can just run sanity checks on the server to make sure the target is actually in a reasonable position to hit the target through magnitudes and dot products.
thats true but the point of the video was to show the mechanism behind hitboxes and method of use. It's better to have client side hitboxes but then I would have to cover sanity checks / anti cheat and i didnt wanna go in that direction yet, would be too long to cover in the vid
one thing that i will mention is that using touch event will make it so its super easy for hackers to control how big the hitbox is and they can hit anyone on the map if they wanted to, so to prevent that you can add a check that checks how far away the attacker is from the victim and based on that the server has to decide on if the attack should be allowed or not, so the max distance that the server allows the attack to be from has to be decided by you based on how far away the attack usually goes. you should also make the distance a bit longer than expected so that laggy players can still hit people, but the down side of doing that is that hackers can now hit players from further away so you really need to balance the max attack distance value
it should be mostly fine since the hitbox is created in the server, but this could be bypassed by teleporting the player to the enemy but at that point its a whole nother' issue
@@SolepsusYTvery true if anyone is interested i'd recommend watching suphi kaner's video on anti-cheat, he's one of the best roblox tutorial channels there is he talks about checking position with respect to character speed and doing an action based on the outcome, this battles instant teleportation to an object
@@SolepsusYT if the part is a parent of the player(hacker) then the touch event works based on how the player detects it as in it wont matter if its a server script because the detection is client sided either way. so touch event should never be fully trusted. an example of this is that classic swords have a server script and it uses a touch event but any time you join a game like sword fights on the heights there are hackers who make their sword hitbox size 1024(the biggest part size) and then they kill everyone on the map
for a more advanced hitbox, i suggest when the input is detected send it to server, then on server play the animation with a marker, and use invoke to get the hitbox from client, checking if it is valid, then doing a sanity check with magnitude, regardless this is great for someone just learning, a follow up video on a more advanced hitbox would be sick
i dont understand why the hitbox has to be instantiated from the client. It doesnt make a lot of sense to have the sanity check either, if the only way to "cheat" the hitbox is by teleporting the player to the enemy, you would be making useless calculations by grabbing the magnitude (as teleporting the plr with hacks would result in the cottect magnitude anyway)
@@SolepsusYTalways use hitboxes on the client. It makes the game much more smoother. Same with animations. You just need damage on the server. Yes it will be more exploitable tho
Currently shapecasting is pretty new and is not recomended for hitboxes due to how collison detection works, if you wanna make a good hitbox use raycasting and attachment points.
