I know several games that have managed to create a ‘Player:Kick’ function whenever it detects an external injection from an executor. For instance, the game: New User Machine - Roblox. I am not certain of this, I have only heard it from various sources, but if it is in fact true, you could probably manage to make some form of intense AC that will defend your game. However, if there really isn’t a way to detect external injections from an executor, there are many videos on YouTube that cover topics like this. Some aren’t those little kitty AC’s but actually some very advanced one’s. I recommend checking them out.
Hi, I must say that I don’t really agree. A lot of the people that are experienced with copying models just re-uploaded meshes.
I don’t want this to be a step by step explanation of how to steal games, but I now understand the process of how they do it.
They for one, re-upload important meshes and two, do something (that I am not gonna reveal so people don’t copy this method) do something so the game, even if it gets reported won’t be taken down.
1 Like
That also won’t really work, if people inject the external software while the game is loading, they don’t get kicked.
Your reasoning is sound.
With this, it’s important to acknowledge that many of the people who do receive these assets don’t do much with them.
Looking at OP’s game, it is successful enough that many likely already recognize the assets. Should his meshes be in a different game, the legitimate creators will be obvious (combined with the common hostility towards bootleg games, it probably wont take off).
Unfortunately, this situation is not likely to occur for smaller developers.
Something has to change for sure.
1 Like
Not sure how that’s gonna stop anything since it’s not tied to an asset ID, they re-upload it as their own.
Try converting your assets into packages, or specifically reserve the right to configure them only for yourself and the other developers. Once exploiters try to steal your assets or even republish your game, they will come across this error:
Credit to @rockfarted for the image.