I'm sure you all people of the new roblox update, the one with the dramatic grey logo. Well, they not only updated the website but also the studio! Making prints look more nice and clean, and breaking tons of scripts when talking about server managing objects or values inside player.
Didn't realize it yet? Here's a small portion of my script, which is in workspace
called datastore
.
FE is on by the way.
Well our good friend "datastore" is going to save and load values in and out of our player, but whoops! Roblox update prevents you from doing that anymore. When in Client Mode
, I can see a folder I made with a script called "PlayerEquipment" (Saves a bunch of critical values I need for the game to function correctly), but when entering Server Mode
and go in the player in workspace, guess what? There's no "PlayerEquipment" folder! So the script, gives me an error when trying to look for it. This also applies to when looking into values inside the player through the server
Script:
--Code player.Character:WaitForChild("PlayerEquipment") --Code
Output:
Infinite yield possible on 'Workspace.wilsonsilva007:WaitForChild("PlayerEquipment")'
I'm unsure if this is an issue that roblox will discuss or if it's going to be like this always even tho because the update is brand new. What was the point of this update anyways? Probably prevent exploiters hacking? At what cost? Breaking scripts and games freatures?
I cannot carry on coding while this is like this, or atleast, while I don't know how to save these values without getting an error.
Any ideas on how to fix this? What's your throughts? Do you think it's a good improvement to roblox anti-exploit?
Thanks for your times guys.
By default, Roblox will warn you of some actions that you are doing. These will appear in orange text, it is identical to doing warn(text)
. This warning in paticular is nothing to worry about.
Infinite Yield Possible
just means that your script can hang forever if the instance it's waiting for does not load/does not exist. That's why it's implied in the name, WaitForChild. This warning will appear by default unless you use the 2nd arguement of WaitForChild
. The 2nd arguement is not required.
The PlayerEquipment
is not appearing for one of these two reasons:
FilteringEnabled
is now always on, which means that any changes made in a LocalScript
(the client) will not replicate to the server. That is why you do not see it.