Yep highly agree, I don’t understand why the source code access was seemingly taken away from us. It’s only yet another item on the list of the other internal things that have been weirdly taken away recently. 
I do not understand why the engine is or needs to be, more and more of a black box. We should have the freedom to tweak and modify, scripts that are running inside our own experience, as reasonably possible. This somewhat sudden, change of direction concerns me very much, in many ways.
Didn’t they say this wouldn’t happen because CoreScripts are currently in bytecode, not readable Lua?
Roblox is not likely to to this. At least they should make stuff like the playermodule to be shown in edit mode so we dont use workarounds like play testing and copying.
If I recall correctly, this change was caused by optimizations within the engine. I don’t think this stops Roblox from providing this code in an open source format, like a Github repository.
If I’m misunderstanding, I apologize.
As for the original topic of this post, I do agree that these scripts should be open source. There has been time and time again where I need to copy a script from a running game just to sift through lines of messy code to fix a problem that has been, or has not been already addressed.
A good example of this was when Roblox had issues with the animate script that was causing blending issues with other animations. This was patched relatively quickly, but for less noticeable issues, this is still a concern.
you dont just write bytecode, you write lua then it gets converted into bytecode
Refer to @Vyntrick’s post above as it explains what I said with more detail. I wouldn’t be a programmer if I didn’t know that
Yeah I do agree with this post. It would be cool to be able to look at the CoreScripts
Obviously not all of them for security reasons and such but some of them
arent they in ur game files? or is that old
I’ve noticed a lot of random warnings and errors with massive react stack traces from the core scripts. Like a lot of new Roblox features, it feels like they haven’t been thoroughly tested, and I definitely agree that they should be open source.
I’m actually not sure but I’m pretty sure they are.
Using some common sense told me yes
im pretty sure they are but they arent actually the corescripts and editing them doesnt have an effect, i know some of them are located in the datamodelpatch and looking into roblox studios memory some of them are in there
Security over obscurity isn’t a good idea either. Storing sensitive stuff should be on the server instead of the client.
You know the CoreScripts are bad when Chat GPT 4 can’t understand how it works 
would make making topbar-style things easy again
With Roblox seemingly dragging their feet on TWO major slowdowns regarding their corescripts, perhaps due to being stretched thin on engineer time, I think it’s time to bring this up again. If the corescripts were open source, not only would it benefit developers aiming to understand how they function and let us see what Roblox expects of their own codebase, it’d let us help Roblox staff in diagnosing performance issues/bugs.
I (and many, many other developers) would not mind saving Roblox staff’s time where possible by taking a look at the source, analyzing possible issues, and suggesting possible fixes.
when the corescripts were open source you could get them running in-game with a little modification
i tried to get the modern playerlist in game and gave up due to the amount of dependencies
Its probably never going to happen but I’d support an open source mirror of the Lua codebase
Even just the builtins since they were removed just to reduce the bundle size of Studio’s download package.
Bump! It would be great if the community was allowed to contribute to corescripts in a github repository or something similar to allow us to efficiently report, address and fix the issues that the corescripts have for roblox!
I 100% solemnly agree. If it were open-sourced, I would spend time on fixing many issues that are present in CoreScripts.
