Yeah, as stated earlier its obviously not going to work perfectly fine, but it could work until they find a better alternative for private modules.
1 Like
Imagine this scenario
A bad actor creates a useful (or reuploads someone elses) module that is genuinely good, and people use it and say itâs good and what not, because it is at that point, then suddenly, the bad actor changes the code afterward, which being private you canât tell at all, then adds a backdoor to all the games using it.
If there is ways to cause harm to games, people will do it. Canât rely on people to do âbasic researchâ if itâs really not easy to do in the first place, especially for new/young developers
Thats exactly what the permission system would prevent; If you take away its permission of adding new Instances, backdoors canât be added without you knowing.
1 Like
I see your point, but I still disagree.
I think that it still matters to be informed about Private Modules and how they can be manipulated to harm your game. It is just highly frustrating to me to see a good feature, in my opinion, to be removed without any alternative mentioned.
1 Like
Very true, I would be happy if theyâd atleast work together with the community and find a good suitable solution to this problem. I think its unfair towards us to simply change things up just like they want to and we have to deal with it.
2 Likes
I believe my post earlier was flagged because I recommended roblox become like EA, and work on working with their community. EA actually listens to their community and works on their feedback, why wonât roblox? This isnât meant to bash roblox, but merely to suggest they improve their relations with the community they say they listen to.
3 Likes
I completely agree. Once again not to bash ROBLOX but I believe ROBLOX struggles with communicating and listening to their community. Especially the ones developing it.
2 Likes
Aye. My post may have been too harsh with the truth, but I was merely pointing out how another company listens to their community and is improving their relations with their player base.
2 Likes
Iâm sure if theyâd listen to what we have to say and what we have in mind, this whole topic wouldnât be a problem for anyone really. It would be a plus on both Robloxâs and our side.
2 Likes
Exactly!!! They need to start listening, or the drawbacks will show. Especially with this, the drawbacks will show with people not even wanting to develop anymore. Terebytes went and created their own gaming engine just because of this. Whatâs to come next now?
1 Like
itâs February 1st, but it looks like private modules are still working??? (this is in my friends game and he doesnât own the module) is it because iâm in the team create, or iâm friends with him??
also works in another friends place (not in the placeâs team create)
does it just work with friends or have they not disabled it yet?
2 Likes
They havenât disable it yet. Maybe they are discussing on whether they should really do it.
4 Likes
I seriously hope thatâs the caseâŚ
5 Likes
I think that is probably the case and I seriously hope theyâre discussing it because this could be a change that could seriously effect the development community.
6 Likes
I believe itâs a fast flag that they have set to just flip at midnight, but Iâm not sure. Hopefully they re-evaluate their decision soon.
2 Likes
It is something they can do without updating the client. Since it is done through http. It is 4:25 Pacific Time, so I expect at around 5:00 they will go offline.
1 Like
To sum up most of what I have said on this thread:
I want to continue to bring up the point that modules were a method of making money on Roblox and with the removal of private modules, certain services can no longer be licensed out to games which means that this change is essentially eliminating an entire method of making money on the platform.
They should not be able to remove a feature that multiple developers are reliant on without some sort of alternative feature to compensate. It is not fair to the people using private modules for a good use when we are punished due to the malicious actions of others.
If I were to make my work public, because it would not function without having access to my proxy whitelist anyways, people could still copy my server-sided scripts and UI design and I have no way of stopping them because making the module public requires me to void the copyright that I am given when publishing a model that is offsale.
Some sort of solution needs to happen because I can no longer make money off of my service that I have been selling for two years and I will essentially have to discontinue it without giving refunds because I do not have enough Robux to do so. I will also basically be losing a lot of loyal customers because of something that is out of my control. That is not fair to me as a developer, and Roblox should be focusing on developers.
There are plenty of good ideas that Roblox staff could use in the mean-time while they come up with a more elaborate solution (if they even do), but right now I feel like I have no voice in what happens on this platform even though, from my understanding, this platform is meant to give developers a way to express creativity or âpower their imagination.â
This change discourages me to develop because I can no longer license out my work properly. As a primary source of income, the sale of my licensed service was important to me as it encouraged me to continue to develop and create on the Roblox platform.
I assume the primary reason for this change is to prevent people with backdoors to have put their modules into games. However, whoâs to stop these exploiters from marking their modules public? Sure, their code is compromised, but they probably donât care as long as they can still have full script context access to games. This âsolutionâ wonât do anything to circumvent this.
Although this change will not stop exploiters, it will stop many dedicated players and groups who want to make a difference on this platform from doing so. Application centers, gun systems, group ranking systems, and more will all be destroyed due to this change. It is important to keep some code private to prevent people from finding ways to easily exploit your code and manipulate it to how they would like it to be manipulated.
Furthermore, as someone who works as a developer for 3 large groups, one with over 200k members and the other with over 300k members, I rely on private modules to ensure that these groups have the most updated scripts without allowing them to re-sell my code, or worse, have a new owner leak it (which has happened before).
Please, please, please reconsider this change, Roblox. Private modules were a staple in the way I developed as it provided me ease of mind that my code would not be altered, tampered with, resold, given away, or similar. I know this is the same for many other developers who are inspired by the things they can create on Roblox but are pushed backwards due to this change.
13 Likes
I am curious, what is stopping people from open sourcing their backdoors? A lot of backdoors are just admin scripts (based off what Iâve seen)
These admin scripts donât need to hide anything.
Now, I understand since theyâre open source you can now view the source and determine itâs a backdoor, however this doesnât help. The users who let in backdoors wonât know how to check the source, or they may just not check the source either way. As said in this thread, roblox is against an option to enable them because a malicious script could just load in a gui saying to enable them, however the same users who fall for that most likely wonât check the source of the required (open source) modules.
1 Like
To add onto this post, most loader scripts are in some way obfuscated and hidden in the script somehow, and this means that most users who do not know exactly what they are doing are fully vulnerable.
what do we want? private modules back (or a compromise or some sort)
when do we want it? as soon as possible please 
2 Likes
Theyâve already shutdown their program.