How do i make a infinite countdown loop

[DelnRDev]

this is my script:
local seconds = script.Parent.Parent.Time

script.Parent.Text = seconds.Value

for i = 1,seconds.Value do

wait(1)

seconds.Value = seconds.Value - 1

script.Parent.Text = seconds.Value

end

this is the like:https://www.youtube.com/watch?v=flRfJBP3kdw&t=1s

what i what the code to do is when the time = 0 then countdown again

[sjr04 (uep)]

Are you trying to nest the loop in an infinite one, or replace what you have now with a loop or what?

[DelnRDev]

im try to make countdown loop for reward .

[DelnRDev]

cuz mine is just countdown 30 sec and its end

[sz_s]

I think you need to give us some more information. Can you describe to us what exactly you want the code to do?

[DelnRDev]

alr i added a link ----------------------------

[sz_s]

That video just shows the same code you already have. You haven’t explained clearly what you want to change about it.

[Secretum_Flamma]

I believe he’s trying to make it so that when the timer hits zero, it rewards the player, than the timer resets back to thirty seconds. You could solve this with a simple

if seconds.Value == 0 then seconds.Value == 30.

[Secretum_Flamma]

This should work:

local seconds = 30


while true do

     wait(1)

     if seconds > 0 then
         seconds = seconds - 1
         script.Parent.Text = seconds
               else
	               seconds = 30
                   script.Parent.Text = seconds
	               -- Award the player here
end


end

Edit: @waterrunner is correct.

[DelnRDev]

thankyou so much,<3________________________________

[NeoInversion (Inversion)]

Alternatively, cut out the middleman, wait(1) and do

local seconds = 30
while wait(1) do
    if seconds > 0 then
        seconds = seconds - 1
        script.Parent.Text = seconds
    elseif seconds <= 0 then
        seconds = 30
        script.Parent.Text = seconds
        --award code
    end
end

Either one works of course, but you can skip a step this way.

[DelnRDev]

what if i have another award script from ServerScriptService i want to run it at the same time without delay
my award script:amount1 = 10 --amout to give each time
amount2 = 20
amount3 = 40
amount4 = 80
amount5 = 160

timedelay = 10 --give delay
currencyname = “Bucks”

for count = 1, 2 do
wait(timedelay)
for i,v in pairs(game.Players:GetPlayers()) do
if v:FindFirstChild(“leaderstats”) and v then
v.leaderstats[currencyname].Value = v.leaderstats[currencyname].Value + amount1
end
end
end

wait()

for count = 1, 2 do
wait(timedelay)
for i,v in pairs(game.Players:GetPlayers()) do
if v:FindFirstChild(“leaderstats”) and v then
v.leaderstats[currencyname].Value = v.leaderstats[currencyname].Value + amount2
end
end
end

for count = 1, 2 do
wait(timedelay)
for i,v in pairs(game.Players:GetPlayers()) do
if v:FindFirstChild(“leaderstats”) and v then
v.leaderstats[currencyname].Value = v.leaderstats[currencyname].Value + amount4
end
end
end

wait()

while true do
wait(timedelay)
for i,v in pairs(game.Players:GetPlayers()) do
if v:FindFirstChild(“leaderstats”) and v then
v.leaderstats[currencyname].Value = v.leaderstats[currencyname].Value + amount5
end
end
end

[Secretum_Flamma]

Please correct me if I’m wrong, but wasn’t there a post here that explained doing while waits was inefficient/bad practice?

[waterrunner]

cc: @Secretum_Flamma, I think this is the thread that you are on about:

Avoiding wait() and why

This is an adaptation of a Twitter thread I made a while ago. This is simply a better formatted and more fleshed out version. Let’s talk about wait(). Not wait(n) (although if you are using small n values to where it’d be barely distinguishable from wait(), you’re probably going to hit the same issues mentioned in this thread). We probably learned about wait() at first as the solution to “why are my infinite loops crashing me?”. It’s a super easy solution and it works! This starts a bad habit…

You should try and avoid wait() and any infinite loop in production code if you can:

Lua is single threaded meaning one task runs at any given time and the task scheduler decides when each task is ran. Each time you add a new script you aren’t actually creating a new thread for that script because the script has been coroutined. coroutine or spawn(f) don’t actually create new threads like in multi-threaded languages because Lua is single threaded at this present time but instead it is telling the task scheduler to run the code in a manner that looks like it is running at the same time.

You may be thinking why does this affect wait() and I have had no problems with using wait(). Whenever you call wait(), you are yielding the current ‘thread’ and letting other ‘threads’ run. The problem then comes when the wait() has finished waiting because it needs to wait for a slot to resume. When your code becomes more intensive wait starts waiting several seconds longer than you specified it to wait.

To avoid using wait() and loops you should always use events when you can because Roblox has events for everything you can think of. For your use case you could use RunService.Heartbeat and check the time difference through tick(). From my knowledge Heartbeat is more reliable than wait and a better option than using a loop. Here is a little bit of code that should serve your use case:

local RunService = game:GetService("RunService")

local Duration = 3
local StartTime = tick()
local EndTime = StartTime + Duration

RunService.Heartbeat:Connect(function()
	if tick() >= EndTime then
		-- Do what you want to do when the time has reached 0
		StartTime = tick() -- Puts the start time to the current time
		EndTime = StartTime + Duration
	end
end)

Sorry if this code looks messy but you should be able to modify it to fit your use case. You should also note that you shouldn’t overuse Heatbeat.

[0_salcret (salcret)]

RemoteEvent. If your timer is in a localscript, which it should be, you can set up a remote event in ReplicatedStorage.

When you want to award the player, fire the event from the local script:

game.ReplicatedStorage.RemoteEvent:FireServer(plr) – make sure you are passing a 
value that refers to the player, else they can’t recieve rewards.

To recieve the function in your server script (Parented by ServerScriptService) you will write your function like this:

game.ReplicatedStorage.RemoteEvent.OnServerEvent:Connect(function(plr) -- make sure 
the player value is the same as the one in your LocalScript

Of course, round it all off with:

end)

at the end of your code

Feel free to ask any more questions, but this should be all you need!

~ salcret

[NeoInversion (Inversion)]

You are correct, waits in general aren’t as efficient. Both of our examples suffered this, @waterrunner has listed a better example. I’ve never really done that to tell you the truth, but I can definitely use that as a reference from now on.

[DelnRDev]

game.ReplicatedStorage.RemoteEvent:FireServer(plr)

where should i put this?

and thx for helping me <3

[0_salcret (salcret)]

You should put in the LocalScript where you want the rewards to be given.

[DelnRDev]

so confuse ------------------------------------

[DelnRDev]

what about
game.ReplicatedStorage.RemoteEvent.OnServerEvent:Connect(function(plr)
where to put this