I want to use playerscripts, but I don’t want roblox scripts to be automatically added.
I use multiple scripts to make sure no player gets the camera and control default roblox script.
This feels redundant so a single option to NOT get roblox basic scripts in StarterPlayerScripts would be nice.
If you add a LocalScript called CameraScript or ControlScript to the StarterPlayerScripts, they will overwrite the default ones.
What instance do you need both of them disabled for anyway?
For the sake of forwards-compatibility I presume, although I’d opt for the property to be named CoreDisabled.
My RTS currently only uses the leaderboard and chat, which is scheduled for replacement as well, I could see ticking this to true to keep Roblox from adding anything else to my game later on, as I’d basically have my own standalone game at that point.
I was about to make a post similar to this today too. Darn.
My proposal was based more on organization and usability. It makes a little more sense (I think at least) to have a property that disables the insertion of the camera and control script models (fun fact the rbxmx files for the scripts and the loading script can all be found in the fonts folder). The organization argument being I don’t have to memorize the location of my client main when I have 3 scripts that all start with C, two of which do nothing.
It would be really cool if this could be an added property by the time StarterCharacterScripts gets enabled and if the property found it’s way onto both containers.
./wouldntitbenice
If this works, then I’d say this is the best solution for now. However, it would be cool to have a flag available to indicate whether or not we want scripts like that injected into the game.
