That’s not true. Clients can try and change the values but those changes will not replicate to other clients. The poster’s way of showing scores to clients is perfectly fine and safe from exploiters.
I ended up getting it working somewhere along the way. For whatever reason it doesn’t work when you change the value in explorer, you have to capture the flag. Thank you all for the help!
What you say is true, yet Roblox grants private servers, one maybe filled with a bunch of clients who exploit enmasse. It is not for us to stop them all, but we should always make it hard for them all. ReplicatedStorage
should only be used to store objects that are required on both the server and the client. To abuse this rule, in an off-hand way, is to open yourself to traps. If the client doesn’t need it, DO NOT replicate it.
I would agree with you, if the poster were putting maps and tools and random assets in ReplicatedStorage. The values he has in there are clearly there so that both the client and server can access them. They’re the scores of teams. There’s no reason to add a level of complication and introduce RemoteFunctions and RemoteEvents to the system. The values are secure from exploitation either way.
Unfortunately, I can’t agree with you. So we must agree to disagree.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.