The entire point of having that setting is to inform users that arbitrary code may be run though.
We need paid models. Has someone made a feature request like this before?
I really donât feel like the whole communityâs opinion is being taken in on this. I think this is a change that should not be made because there are TONS of services on ROBLOX that require Private Modules. Looking at others replies tells me that there are probably TONS of more options that should have been discussed before making a decision that would impact the developer community this much.
6 Likes
Most players absent-mindedly put closed source module backdoors into their games. Although removing closed source modules is a step in the right direction for reasons other then just backdoors, Iâm pretty sure the same type of people who carelessly insert random models will accidentally insert a heavily obfuscated backdoor. As Iâm sure that once closed source modules are gone, malicious players will just switch to obfuscation.
4 Likes
Like you said either way someone is going to get a backdoor into their game. So why remove Private Modules when you could take steps to make them safer on the developer.
If we are on a team create on the game, Can we use close source modules?
2 Likes
Why are you so sure they didnât discuss other options?
Obfuscated code can still be dissected and audited. You donât even need to deobfuscate it, you can just poke and prod with shim functions and log what itâs trying to do. You canât do this with private modules.
1 Like
I would have liked to been told what kind of options were explored then because it just really seems like they jumped to a irrational sulution, but we all have our opinions!
1 Like
Roblox is a ginormous company, especially on the engineering side. Itâs extremely unlikely that there were no other options discussed. Likewise, Roblox is not obligated to share other discussed options.
1 Like
I understand that but like I said it seems like they didnât. I also understand that ROBLOX is not obligated to share other discussed options but maybe it would have helped to inform the developers that this solution wasnât their first idea.
3 Likes
Third party private modules had flaws anyways. Iâm glad they are being removed.
Currently with these it is possible to trick someone into using a module that may do some real work, yet it has a hidden backdoor for its author to execute code in your server, or might just be plain malicious. Iâd rather use open source modules than risk my game getting hijacked.
There isnât a point in keeping your modules closed source either. Whatever you try hiding, there was always a way for others to get it. Even with closed source modules. Hiding/obfuscation is pointless.
In fact, we should embrace the open source movement. We can only benefit from sharing our code.
Will an alternative to private modules be provided? Will they, once removed, possibly come back, and be sandboxed? Only time will tell. But limiting yourself to open source modules rather is many times better than being under the threat of getting your game hijacked.
All this post really is atm is discussing with points that have already been told, I could probably give a reply to a lot of posts for the removal of private modules but it seems like everyone just brings back the same arguments even when they already got responded too.
I couldnât give a % for people for and against it, but from all the opinions I have heard (from players and developers) the majority is against the removal of private modules, I already know Iâll hear someone say to that âplayers arenât properly informed and therefore wonât be able to make such a decission correctlyâ in case that happens, my answer is very simple, players will be the ones thatâll suffer from this change too and therefore shouldnât be ignored.
Like my (and other peopleâs) replies to posts, itâs clear that the removal of private modules has these pros and cons
pros
- more open sourced scripts
- scammers wonât be able to abuse them (as much)
cons
- no replacement will be given (in a reasonable time)
- for a similar functionality you basicly need to put so much work (and maybe even money) in things like obfuscation, servers, âŚ
- some devs wonât even be able to find a similar functionality and will be forced to open source it which will result them not making money of private modules
- increase of botted models
- it will not stop scammers (or even slow them down)
Note, not all pros/cons are listed.
3 Likes
ROBLOX Airline groups will be heavily impacted by this. Companies like exaTech and Airplo rely on the modules to practically keep the games secure and functional. Although, it was a good choice to remove them because as said above, this system had small flaws and big flaws, basically each flaw is like one hole in a ship, enough of them to sink it entirely.
3 Likes
Not really, and obfuscation is pointless.
What? If they can make good modules, they can definitely make good games. They can make money off of the games they make instead.
1 Like
I said before that these arenât perfect, just similar and ânot reallyâ means nothing if you donât even take the time to explain what you mean with ânot reallyâ, obfuscation takes work, hosting servers takes work (and sometimes money), thatâs what I meant
I think you didnât read the part âof private modulesâ, and like I said on sh, game developing is more than just scripting, itâs a completely different thing
1 Like
Hosting servers shouldnât take a lot of work
Obfuscation might take work. It shouldnât be your only defence against people who copy scripts and whatnot. Itâs pointless. And Iâve already stated why.
Collaborate with other people. Or do it all yourself.
1 Like
Your first point âhosting servers shouldnât take a lot of workâ
This depends, for someone experienced in that field, itâs probably simple, but for people who know nothing about it, itâs very hard
For your second point, yes, I know that obfuscation is pointless, it was just an example
Itâs hard to find people trustable, and if you can trust people you can trust private modules too, whatâs your point? (People can do more harm than private modules, allowing them in basicly means they can do whatever they want with your game, even reupload it)
And making games yourself takes a while and isnât easy
Besides that, a point I forgot to mention, the overall quality of private (now open sourced) modules might decrease due to devs not making money of them (like you said, theyâd switch to games or something else)
yes, making money isnât a big factor for everyone, but generally itâs still a factor lots of people care about
1 Like
If trust is an issue then just do it by yourself.
1 Like
If you look up exatech, they donât even plan on open-sourcing a 2 year old product and they continue to say for security reasons. First off, not sure why you would throw a product used by so many in the bin, but also what is so important thatâd you rather hide from hundereds permanently then show? This is why private modules are bad. You have absolutely no idea what is running in the background or when the code is updated.
5 Likes
This might be off-topic, but Iâm sure it would help everyone, including Roblox staff, get a gist on the developer communityâs thoughts on thisâŚ
- I am against the removal of Private Modules.
- I am for the removal of Private Modules.
- I think Private Modules should be sandboxed instead of removed.
- I think Private Modules should have a
Allow Third Party Modulesbutton instead of being removed. - I think Private Modules should be sandboxed and an opt-in, instead of being removed.
0 voters
If it is off-topic, please let me know and Iâll remove it: slightly_smiling_face:
6 Likes