Hello, My Name Is Nehoray
I Wanted To Know If An Exploiter Can See / Change Values In ReplicatedStorage
Thanks.
Hello, My Name Is Nehoray
I Wanted To Know If An Exploiter Can See / Change Values In ReplicatedStorage
Thanks.
They can see and change them, but they won’t replicate without a remote.
ok Thanks So Should I Use ServerStorage Instead of Using ReplicatedStorage?
You shouldn’t be trusting the client. If the client absolutely needs to access the stuff, then ReplicatedStorage. If they don’t need to, then put it in ServerStorage.
The Client Should Access It,
But I Don’t Want Exploiter To See The Values.
You don’t have to be an exploiter to see those values. The contents of ReplicatedStorage are replicated to all clients. If the information is so sensitive that you don’t want an exploiter messing with it, then move it to ServerStorage.
It really depends if the client 100% needs it. If not, server storage
Use ServerStorage to store values and models.
If you want a client to see certain values that they are permitted to see, use a RemoteEvent or a RemoteFunction to pass those values back to the client(s).
Everything in ReplicatedStorage is replicated to everyone, as the name implies. This is why it is used to store publicly accesible things like remotes but not data that could be sensitive.
Idea: You can add a fake remote event in the ReplicatedStorage attached to a server script so the exploiter would be kicked if it’s activated. It still can be useful.
Honeypots will work in the short term but once they have been found out to be traps they’re basically 100% avoided