sanity checks/ client to server

[slow valve]

im going to switch my hitboxes to client and so im wondering what type of sanity checks il have to do. I cant do magnitude checks because of delay and i need to some how do check to prevent remote event spam

[ornate python]

you could look into server authorative rollback netcode

definately not easy to do

but not only does it provide good security but also lag compensation

[slow valve]

do you think there are any alternatives? but from my research i couldnt find much documentation on this and so it would be hard for someone like me to implement this

[ornate python]

search up leaky bucket to limit remote event spam

you cant prevent the client from spamming the remote event but you can validate it on the server

so if damage requests are sent in an appropriate rate it would be considered valid

[slow valve]

yes but now heres the problem. how to validate that the damage request would be possible

since if someone is over 40 studs away and attempts to damage someone whos the same distance

its easy for long distances but it would be hard for short distances

sure i could make it about 10 studs to conpensate for lag but thhen if exploiters were to find this vunrability they would have extra range on any weapon/attack they do

[ornate python]

yea thats tricky if theres a lot of latency and if your characters can move very fast

[slow valve]

movement is average speed so that dosnt affect the latency

[ornate python]

if theres a lot of lag and characters can move quickly in your game (such as dashing) then there will be a greater discrepancy between the clients position and server position

[slow valve]

that is a slight issue but if it means having responsive and smooth hitboxes it is a small price to pay

[ornate python]

if you want responsive and smooth hitboxes while also being secure the only solution ive found was server authorative netcode

[slow valve]

this would replace the default system for characters?

[ornate python]

you could if you want but i think thats a lot more work.

[slow valve]

i found something like this

https://devforum.roblox.com/t/chickynoid-server-authoritative-character-replacement/1660558

[ornate python]

yea

they use a custom physics engine so it allows for validation and also lag compensation

which is the rollback part

[slow valve]

so if i were to experiment and implent this it would fix latency and potentioal exploits ?

[ornate python]

yea it would but it may have an impact in performance

[slow valve]

onto the client or server?

[ornate python]

also it wouldnt work for super high latency like above 300ms

[slow valve]

thats fine

[ornate python]

both, although it seems to be more efficient than default if theres a lot of players

[slow valve]

ok il try and use server authoritative netcode

thx

[ornate python]

np

[slow valve]

hmm it is quite confusing

i dont udnerstand quite a few things lol

is there any other ways?

what do most popular games do?

[ornate python]

iirc games like arsenal and bedwars use something similar

a lot of games will try use client side anti cheats but its very easy to bypass

the only other good option is to moderate manually with a report system

[slow valve]

Might just have to use magnitude and check how fast events are fired