Something like this:
You should send an image of the Explorer where the scripts are at.
That’s the script editor tabs, not the Explorer. You can read my post I just made for an example.
However, based on this image it seems like you are using Server Scripts for all of them. Click Detect has to be a local script because you are detecting mouse inputs 
1 Like
Yup! clickDetect should be a LocalScript.
By the way if you go into the “View” tab, you can open up the console to see errors, which should show you that you can’t fire remotes from server scripts.
You can fire remotes from both the Client and the Server.
Haha you got me. I even went to test it 
(It’s called FireServer() for a reason, you are firing from the client to the server. Also when you do .OnServerEvent() it returns a player variable so that wouldn’t make any sense either loll)
Wait on second thought, if you mean’t firing to the clients then yea you can do that
I meant firing to the clients.
mbmb, probably would’ve been better to specify firing to clients in order to not confuse OP (and me ) lolllllll.
True. I definitely should’ve specified that.
It’s his second script that needs to be a local script we solved this earlier but we kinda went on a small side quest lol.
I’m back, I was eating!
Thanks for the tips, @Pure_Bacn ; I’ll convert clickDetect to a LocalScript.
):
Can you me what that script looks like as well as what line 6 is? Thanks.
local leaderstats = player.leaderstats
1 Like
Can I see the full script? (also try printing out player to see what happens)
You should use:
local leaderstats = player:WaitForChild(“leaderstats”)
local multiplier = player:WaitForChild(“multiplier”)
Try local leaderstats = player:WaitForChild("leaderstats")
also one thing I need to check, your multiplier value isn’t equal to 0, right?
1 Like