Hello, title explains it all. Is this is a bug? Is it happening to anyone else?
The error says you’re checking the “Value” property of a folder—which doesn’t exist. Make sure your path is defined correctly.
2 Likes
It is in the right path. You can clearly see in the second photo that the autofill says BoolValue.
It even prints TWICE to check if BoolValue.Value exists, and it works
The only times it doesn’t work is if it’s being used in an if statement.
I also tried
local bool = boolValue.Value
print(bool) -- this part works
repeat task.wait()
until bool --still gives error
Can you post that segment of code, then? The if statement where it’s checked. The error says it’s a folder that’s being checked, and it also says it’s checking ReplicatedStorage.Stats.TutorialData.Data.1; from what I can see it looks like the path is wrong (note the .1 at the end). Just in case, please post the actual segment with the error.
1 Like
Another script(server) is adding folders as children to the boolValue. These folders are 1, 2, etc.
The if statement is the “until” part
Okay so I added a separate folder to put the children inside of, instead of putting it in the boolValue.
It still gives the error
Strange, I don’t see anything wrong. I’m not sure what’s causing the error, but the issue isn’t with checking for true or false; the issue seems to be the system misinterpreting what you’re checking, somehow.
The easiest short-term solution that I see is to run an if-statement beforehand (or simply change to a while not BoolValue.Value do instead of repeat until BoolValue.Value) since we can already see it’s printing beforehand.
To fix the actual bug, I’m not sure. I don’t know if it will do anything (and this is completely a shot in the dark), but you could try to assign a variable (that’s updated each loop) and check that? Something like
...
local isReady = tutorialDataIsReady.Value
while not isReady do
task.wait(5)
isReady = tutorialDataIsReady.Value
end
Once again this is a plain guess and I have zero clue if it’ll fix anything, but at the very least, the while not ... do should fix most occurrences of the bug.
1 Like
Could you show more of the error and the script?
Specifically, the line number of the error was cut out in your screenshot, and I assume this error is coming from another part of your script (perhaps somewhere where the tutorialDataReady variable is being modified)
Fixing bugs willy nilly is not something I recommend as that usually doesn’t work, and ends up just hiding the bug behind a nice coat of paint. It’ll come haunting you later
I forgot to say it but I found the reason why it wasn’t working, so sorry I made you type that whole reply out.
You were right about it being a different line.
The reason it was cut out is because it was outside of the frame. Roblox should fix that.
@CooKooBirdy5678 thank you for all the help!
3 Likes
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.