The issue is as the title says.
I’ve never had this happen to me before, and I’m assuming it’s some sort of studio or engine bug. For some reason bug reports are group locked so I posted this under here.
Feel free to correct me if I’m wrong.
2 Likes
Hey @flowfate!
I am not sure if that’s a bug… Judging by the video, it seems that it is a LocalScript running through StarterPlayerScripts and with code lines working as expected. Do you want to transform it into a server script or am I missing something?
1 Like
The reason your server script is running in that area is because you set the RunContext of the script to client. That means it will essentially function like a LocalScript, while being able to run in places LocalScripts can’t run in (e.g. Workspace).
You can learn more about it in the announcement they made 2 years ago:
It’s a local script, not a server script. It doesn’t use run context either it’s the legacy version.
Thing is, code DOESN’T run normally in the original StarterPlayerScripts instance, so I’m confused why it does now.
? LocalScripts will always run in StarterPlayerScripts upon a player joining, thats nothing new
What do you mean? Using the picture below as a reference, the ClassName is Script, indicating that it is a server script, and the RunContext is Client, not Legacy from what I see. Setting the RunContext to Client means it will function like a LocalScript, therefore it will work in StarterPlayerScripts.
1 Like
Oh that’s odd, I didn’t see that. Question is why does it run inside there? It’s weird but thanks for pointing it out.
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.