Yes, it does ensure safety, but still, big game devs and company devs do NOT want their code to be stolen. People will claim the code is theirs when really someone else made it. This creates an issue for devs because devs don’t want to release their code, but they don’t want it taken down with this update. I use admins, application centers, nojump scripts, and many more things which all run off private modules. My business will be screwed when this update happens as we use these kinds of things to our advantage to give people the best possible experience.
Yes and I completely understand that and support it. There was a comment I made sometime ago about how Microsoft keeps developing microsoft defender. Defender keeps you safe while using microsoft products and safety is one of their number 1 priorities as well. But you know what microsoft gives us that ROBLOX won’t? Microsoft gives users the option to disable defender at their own risk. ROBLOX would NEVER give creators an option to disable this “firewall” and let us explore, browse, and use these module scripts at our own risk.
This is not “patching a bug”, and I don’t believe its as simple as “patching a bug”. My point is, this is a system that many developers rely upon in the community for the safety and satisfaction of users/customers. Countless groups will be forced to close. Countless games ended. This is not a bug, and it should not be “patched” like you said. This is a system that was exploited by users attempting to do harm to other users. Plus, in your response, you didn’t even acknowledge the fact that ROBLOX isn’t going to provide a way to “disable the firewall” that they are creating. I understand this is in the interest of safety, I understand people exploited this private modules system, and I understand that ROBLOX could have been loosing out on profit because of it. But to disable the system means that a lot of hard work will go to waste unless these developers make their modules open source. Which then, they would loose credit for what they have created. So again, this is not a “bug”. This is a matter of protecting what developers have created while protecting players from potentially harmful scripts. ROBLOX needs to evaluate this issue carefully in order to provide the best possible outcome for all parties, or else this will end in more chaos. Which it already truly has turned into chaos.
It was NEVER intended in the first place. That’s the definition of a bug. Why don’t you follow my quote link up and read some of his responses in the thread.
I urge you to stop referring to it as a ‘system…’ because it was not. It was a bug.
You can’t fault the company for patching a potentially malicious bug. It’s not their fault that some people found out how to exploit the bug for business opportunities. - like I said before, if this patch prevents even ONE person from seeing something they shouldn’t, it’s a win. Safety always has priority.
there are also a few feature request threads in #platform-feedback for this that would be a great spot to put your suggestions
As much as it was a bug to begin with, it’s important to note that it became documented behavior. There was a page on the wiki that even helped guide you to making your private modules even more secure. So while it was a bug originally and I entirely agree that it should go, it’s not very fair to play it off like a simple unintended bug being patched.
Lots of groups rely on these “companies” (I know many people don’t agree with calling them that, but you know you I’m referring to). These companies rely on private modules to protect their IP. The issue is, most of these groups don’t want to open source (for obvious reasons), and they don’t want to make their product(s) free. This means many of them will close, or stop selling scripts and instead just sell assets like models of meshes, but when these groups close, the groups and games that rely on them will struggle massively to find alternatives to what they were using. Most of their games will break and they won’t be able to fix it.
This change is now live. It is no longer possible to require third party modules that are closed source. Module creators who want to make their modules usable again are encouraged to make their modules open source.
Thank you all for the feedback about this change! I want to assure you that we reviewed every post in this thread to make sure we heard everyone’s voice. Much of the feedback centers around a desire for official support for third party code in games. If you would like to see this happen, please file a feature request and continue the discussion there.