![]() ![]() This causes the script to have to execute the entire cycle before getting checked. Oh btw, for the Firefox application tab part, if you cant find use ROBLOX there, click use other, browse, then go to the folder containing RobloxPlayerLaun. The script would check at the top, run the first light effect, get yielded, run the second light effect, get yielded, THEN checking again at the top. The reason your lights were not turning off instantly was because of this. Using wait() yields the thread you’re running your code in, and while true do loops only check if the value is still true whenever it gets back to the top. ( feel free to research this on your own )Ĭhecking every time the light effect changes. The task library function are pretty much the same, but they’re better for reasons that i won’t explain here. ![]() If script:GetAttribute("Random") = false then return endīefore you were constantly spawning new threads for your light effect, which is a horrible practice since it’ll add another thing for the script to be running, slowing down the runtime. If script:GetAttribute("Random_Changer") = 1 then Assuming that the code you provided is in some kind of event connection, a much better way to do this would be: local Fixture_Array = :GetChildren() This is designed for Windows/Mac OS computers (maybe linux and it's distros.) Anyways, this application. The code you provided has a couple of bad practices that are leading to this issue. To play ROBLOX on Chrome OS, download it from the Play Store.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |