![]() ![]() at the moment, asset stealing really isnt a problem. ![]() in the future, i think roblox should penalize devs who are caught with stolen assets, but that involves a whole different slew of politics that i dont want to get into right now. ![]() While we can make our games less vulnerable with better network code, there’s nothing we can do at the moment about stolen assets. to take this a step further, you can use an obfuscation program to make your code even harder to read (but still not absolutely safe). this should keep your code more protected, but the lua bytecode can still be decompiled, albeit in a much less readable format. after you require the modules, delete them the code will continue to run as long as you dont delete the script used to require the modules. to keep your code safer ( that is, a lot more inaccessible, but not completely safe), you can place all of your main code in modules. The same methodology for stealing assets applies to stealing scripts. anyone trying to steal your assets wont have any choice but to wait until they actually appear in the workspaceĪny code in a game published on the site is no longer safe accessing the cloned models in the scripts memory will be out of the question, as the small amount of competent v3rmies actually capable of doing so probably dont care enough to try. for models that need to be accessed by the client, clone all of the assets in the replicated storage, delete the originals, and hold references to the cloned models in the script. to lower of the chances of massive asset leaks, store all of your models or maps in the server storage rather than in replicated storage. personally, i dont think leaked assets are that big of a problem because most of us have the integrity to not use assets stolen from other devs’ games, but others may find it much more upsetting. Many of these injectors include some sort of function that allows exploiters to save instances to the disk, any asset in the clientside datamodel can be stolen. protecting your assetsīecause these id7 exploits have become so accessible, from now onward, you should make all of the following assumptions:Īny asset that appears in a game published on the site is no longer safe since the problem stems from lua itself as a programming language, and its unreasonable to expect roblox to completely restructure the entire security system from the ground up, it’s up to us developers to use more responsible coding practices to keep our games safe. not only will the amount of people using exploits increase, so will the amount of competent people working to make new exploits. download the entire clientside datamodel as an rbxlĪs roblox grows, exploting games is going to become more of a problem.acess and edit the source of any script or module on the client.abuse devs’ uninformed network coding practices to exploit FE games.steal pretty much any asset that appears on the client.this is bad for a lot of reasons because exploiters can: Script injectors are programs that allow exploiters to run their own scripts inside of roblox’s lua environment. (august 2018 revision: updated this post to be less… annoying, also moved to learning resources) intro
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |