s
#Coroutine won't work
glossy atlas
If you're just going to immediately resume a coroutine and don't need to pause it for any reason you might as well just use task.spawn
Your coroutine is working tho
Your while loop's condition is false
So it doesn't even begin looping
opal phoenix
Your while loop's condition is false
after the condition changes to true it doesn't work
glossy atlas
after the condition changes to true it doesn't work
Yeah because once the loop finishes its done.
local condition = false
while condition do
print("This will never run")
end
condition = true -- this doesn't start the loop again
The program has already passed that point in execution
opal phoenix
```lua
local condition = false
while condition do
print("This will never run...
but my condition being changed is placed before the loop
stray surgeBOT
** You are now Level 4! **
opal phoenix
Under LLight Script
glossy atlas
Yeah inside an event (right?) which happens at a future point in time. After the while loop ends.
glossy atlas
```lua
local condition = false
while condition do
print("This will never run...
This can easily be adapted to this and the result is still the same:
local condition = false
Part.Touched:Connect(function ()
condition = true
end)
while condition do
print("This will never run")
end
It's important to realize that events are expected happen in the future. You should rely on some state from them in the present
An event may fire immediately, or 10 seconds from now, or never.
opal phoenix
It's important to realize that events are expected happen in the future. You sho...
so basically do I need the coroutine resume thing to happen while the while loop is at true?
glossy atlas
Yes and no. While that may solve it temporarily, as soon as your condition becomes false again the loop stops and can't be restarted
The easiest solution is to just have an infinite loop, that only executes code when your condition is true.
while true do
if condition then continue end
print("This will only print when condition is true")
end
Although this isn't that performant
Limiting the rate of polling (checking) you're doing can make it more performant. But it also reduces the accuracy.
while task.wait(0.1) do -- Now we're only checking every 0.1 seconds
if condition then continue end
print("CONDITION = TRUE")
end
The most optimal solution would just be to break your while loop out into its own function where you can spawn a new loop whenever your condition is true.
opal phoenix
this is what I came up with and it works
glossy atlas
For example:
local condition = false
local function Operation()
while condition do
-- Do some operation while condition is true
end
end
local function SetCondition(state: boolean?)
state = if state == nil then (not condition) else state -- Lets you pass in a state or just exclude it to toggle
if (state == condition) then return end -- condition already equals state
condition = state
if not condition then return end -- Exit early if our condition is false
task.spawn(Operation) -- Spawn our operation if state is true
end
Part.Touched:Connect(function ()
print("Part was touched")
SetCondition() -- Toggling state of condition
end)
Yeah that's the polling technique I was talking about
That should be fine
opal phoenix
That should be fine
my game isn't really gonna be big so I think it would be fine if I keep it like that but thanks
glossy atlas
There are some situations were polling is necessary, but a good rule of thumb is to keep everything event orientated.
glossy atlas
this is what I came up with and it works
Because with this technique you're running these loops even when the condition is false. Which means you're doing extra processing when you don't need to