How to make a script using "ReplicatedStorage" or "Workspace"

These are accomplished with remote spy, when a remote is fired it is flagged by the spy and tells you the remotes name, the directory which is commonly in replicated storage. There are basics tutorials on remote spys so do check them out! 

Example:

game:GetService("ReplicatedStorage").Cash:FireServer(99999)

You get the service where it is held, which is replicated storage the remotes name is Cash and you fire that remote with the value which I did 99999, this would give you 99999 cash everytime you fired the remote.

Hope I explained well.

Im dum and the only thing i know with replicatedstorage that you can make is 

1: storing ip addresses,

2: loading screens

@eb_

hmm I did the thing you said I used remote spy but I don't know that much can you send me a link please?

@_realnickk fair enough I didnt mention DeX tho but games like adopt and raise a cute baby with scripts like these it's very unlikely you'll get banned. But yea I guess

@_realnickk fair point 

@_realnickk

Crap like..

ReplicatedStorage is a service meant to be used by the server to store assets in a non-physical environment and replicated to all clients when it is needed. This is oftentimes used to store events objects, module scripts and objects that for some reason need to be replicated to the client (often seen in more client-aimed games/places).

You can simply index it with game:GetService("ReplicatedStorage"), then if you wanted to view the contents, you could simply loop through all of them, although solutions such as the Dex explorer solve that for you by giving you a GUI to work with that is similar to Roblox Studio's own explorer. As others have mentioned, your prime toolkit here consists of a piece of code that can intercept and log event fires from client to server, as there you will be able to observe when an event is fired, what the event does, and what data is being sent. Using that information, you can attempt to tinker with the data being sent, or even how many times the event is fired. Of course, this is something that you will rarely get lucky with, as this is only really exploitable when the developer you're targeting is an idiot who is either too lazy to properly implement a good client-server system or is too bonked on the head to understand the need to not trust the client.

@53326why is it impossible!?!?!?