#Something to take away
#Reasoning
This is quite clear why only the LocalPlayer can see the Part created, it’s because of FilteringEnabled. If you’re unaware of this, it’s not good, It’s alright if you are new to ROBLOX’s Lua API, but this has been around for about two years, it is manditory you have a knowledge on how this works.
Please try to find more about this, also watch this to get a good understanding before continuing with more work.
#A brief rundown
This is because FilteringEnabled tells the Server to absolutely, never, trust the Client. The Client is your Computer.
Anything you do, will not be replicated to the Server, which replicates to all the other Clients - Players. Therefore when you created a Part on your end of the Server, it was told to not do the same for everybody else, primarily to prevent possible exploitation.
For the Server to replicate the Part to the other Clients, it must be done on the Server. Doing so isn’t hard at all, simply run the Instance.new function in a ServerScript, located in ServerScriptService.
This may be tough to continue attempting to do what your Code is running, as the Server cannot access the Client, therefore you can’t mess with the Player the way your Script appears to be doing.
You can get approved access though by loopholes. Those can consist of either traversing through the Players with array-loops, or getting the Player with listeners, passsing them through as arguments.
Either that, or depending on certain scenarios, you can use Remote Events and Functions.
4 comments
it is in a local script, maybe thats thr problem
yes that's the problem, create it via the server
Please read my answer, don’t accept, it won’t necessarily fix your issue, but you must know this
@Feahren makes you die inside, doesn't it?