Why do my scripts stop working even when they're not disabled?
I'm working on a "find the lost item" quest, and in the item I have a spinning and bouncing script among a few others, but once the quest is started, if the the quest item changes parent, gets cloned, moved to workspace, or even newly cframed all the scripts inside it stop working, weird right
1 answer
There are many reasons for a script to stop working. here are some common ones:
1.Your script errored. Your script encountered an exception and therefore fails, thus it stops working. You can check the developer console (press F9) to see errors (red text). We can help if you don't know what they mean. usually this is the format of an error:
(time): (script that errored):(line that went wrong) (reason for error)
2.WaitForChild cannot find something. You used WaitForChild on something that takes forever to load, and the dev console would give you a Infinite Yield Possible warning, meaning that the game thinks the WaitForChild function will wait forever. the warn looks like this:
(time): Infinite Yield Possible on ("(what you used waitforchild for)")
3.The script is just messing with the wrong things an example is changing startergui when really you should be changing the localplayer's playergui, or tweening a character's position when you should just change the character's humanoid's walkspeed. stuff like that.
perhaps you should try this:
in explorer, disable all the scripts inside your item. then, at a separate script, enable the scripts after the item is cloned to workspace.
0