Making a timer in a game using FE?

✓ Accepted answer

You should do as little as possible in the client besides display the value.

--script
local timer = game.ReplicatedStorage:WaitForChild('IntValue')
timer.Value = 300
while wait(1) do
    timer.Value = timer.Value - 1
end

--localscript
local timer = game.ReplicatedStorage:WaitForChild('IntValue')
local label = --path to gui
timer.Changed:connect(function(val)
    label.Text = val
end)

AnonymousDec 24, 2016Permalink

9 comments

Where is your remote event he is going to want a script

AnonymousDec 24, 2016#

If you're using .Changed, you don't need a remote event.

AnonymousDec 24, 2016#

It is not a good idea to do this as you rely on the network speed ect to replicate this change which may take more than one second and will be inconsistent due to the change not being done instantaneously for all clients.

AnonymousDec 24, 2016#

Also you should do as much as possible (that is safe to do) on the client side.

AnonymousDec 24, 2016#

Wrong. One, network speed issues are the players' problem, not the scripter's. And if you are implying to do the timer loop on the client, that's guaranteeing even moreso an inconsistency, as you can't synchornize the loops. .Changed events are synchronized. Three, no, you don't do anything on the client unless it is gui or input work. Do not encourage new scripters to give power to the client (th

AnonymousDec 24, 2016#

e opposite of filtering enabled philosophy). Thank you.

AnonymousDec 24, 2016#

I would use a RemoteEvent for this, but yeah, the loop should be done on the server to keep everything consistent.

AnonymousDec 24, 2016#

Thanks for your answer Cabbler! :D

AnonymousDec 24, 2016#

Np. It is only the standard model for replication. Ignore people like kingdom5 who don't quite understand filtering/networking.

AnonymousDec 24, 2016#

Making a timer in a game using FE?

1 answer

9 comments