I have a loop what is meant to detect if a bool value is either true of false. The loop always detects it as false although when I look in the games explorer while the game runs the bool value is positive. The false if statement continues to run and never switches over to the true if statement. Both this script and the script that changes the bool value are server side.
while true do
wait(1)
if game.Workspace:WaitForChild("boolvalue").Value == false then
print("not running") -- this continues to be printed although in the explorer the bool value is true
else
print("running")
end
end
Hmm, maybe I misunderstand what you mean.
Oh, maybe the time that the boolvalue changes and detecting the boolValue does not match. So, maybe it’s timing problem.
Use :GetPropertyChangedSignal as it fires when the given value changes. A while loop is obviously not efficient in this case.
workspace.boolvalue:GetPropertyChangedSignal("Value"):Connect(function()
if workspace.boolvalue.Value then -- if it's true
print(workspace.boolvalue.Value)
else -- If it's false
print(workspace.boolvalue.Value)
end
end)
This doesn’t indicate that using a while loop will not work but it isn’t efficient to detect changes if there is a given event for it.
What you’re doing is changing it on the client which doesn’t replicate to the server.
To change it on the server, click on Current Client and then change it.
I know the property changed signal could work for this situation, but I actually want the condition to be checked every second and not just whenever the bool value changed.
For example, if the bool changed from false to positive or vise versa every minute, I would want either “running” or “not running” printed 60 times.
Also, I’m not changing the bool value manually, I’m just watching it change through the explorer. Its being changed by a regular script in the workspace.
while wait(1) do
local boolvalue = workspace.boolvalue
boolvalue.Changed:Connect(function()
if boolvalue.Value then -- true
print("True")
else
print("False")
end
end)
end
-- LocalScript @ StarterPlayerScripts, for it to be able to detect client-sided changes
local obj = workspace:WaitForChild("boolvalue", 10)
repeat
print(obj.Value and "running" or "not running (v == false)")
wait(1) -- I'll assume you know this isn't very accurate, regardless
until nil
This would theoretically set up infinite listeners, you don’t want that.
the problem seems to be outside of the detecting script, your value changing script might be at fault somehow or there are more than one object named boolvalue in workspace, I replicated it in an empty baseplate and worked fine boolvalue test.rbxl (18.3 KB)
