Allow a property to stop the inserting of ROBLOX’ default scripts within StarterPlayer specifically .
This will allow us developers who care about our work’s structure to continue to thrive in peace .
Allow a property to stop the inserting of ROBLOX’ default scripts within StarterPlayer specifically .
This will allow us developers who care about our work’s structure to continue to thrive in peace .
Note: I know we can : Destroy ( ) , but I don’t even want to know of its existence < 3
Pretty sure you just put your own script in with the same name to override Roblox scripts.
Edit: I mentioned that the post above your reply, but thanks for your feedback.
What stops you from adding the same-named script with script:Destroy()
? Why do you need a new property if the current workflow already works?
The practice of adding a script with Name matching default Roblox inserted ones feels like a work around rather than a supported feature. I can’t fully assume the default scripts injected to PlayerScripts at runtime wont change at some point (in Name or source), potentially breaking customs systems built on top of or adjacent to them. With something like a boolean property indicating whether Roblox should inject latest default player scripts, I can be much more confident what to expect when building custom camera and control implementations.
Convenience, confidence, cleanliness ; lack of clutter improving the workflow in the community .
Some of us respect our entire game structure .
Just go on ahead and move to VS Code .
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.