Asset Protection // License System

Hello! I own my own studio which makes scripts for other games to use. I have been looking into a couple ways to do licensing and so far it has been pretty obvious to use an API such as trello to manage licenses.

My question is, how would you approach checking a license to make sure a player owns the license and then implementing the script into roblox?

It seems like you can only hide a server script so much until it can be found and deleted and at that point even reverse engineered for someone with enough experience to figure out how to bypass the license.

Any ideas?

2 Likes

For your situation, I recommend using a hub service such as onPoint Vendr or Parcel, since it handles licensing and buying scripts from one place. Both of them have a licensing API included and you can implement your own logic if the user has or hasn’t got a license.

But if you still looking to use Trello, I recommend using a module to communicate to the Trello API with out writing a bunch of HTTP requests.

And to hide your scripts, You may be able to use (But people may think it is a virus since you are hiding the code) obfuscation, I personally wont recommend it though since it is against ROBLOX’s tos if it is distributed.

1 Like

Hey I’m couldn’t answer you I’m sorry, but out of curiosity, where do you advertise your studio? And how many clients do you get /weeks? Thank you .

That is beautiful but how do they handle the implementing of assets without giving away the code until the license has been verified? Unless they have a system that won’t let the script start until the license has been verified. I’m curious how someone would hide the code so it isn’t replicated easily or modified.

I’m very familiar with obfuscation but it still doesn’t prevent the code from being copied and pasted along with the UI for the script to work yk?

1 Like

You can’t prevent someone stealing or modifying code you give them access to.

Only way to do this is by having an external server-side API for most (if not all) functions that your code does. This way you can store the code you want to protect on a secure server. The client-side code will be mostly useless.

This is a bad idea for multiple reasons. Perhaps it’s better to accept your code will be stolen. There’s plenty of articles/videos about this concept. TLDR: usually the actual code isn’t the valuable part.

You can’t. Simple. The moment you put that asset on sale, the moment it becomes publicly available. The user may simply modify the code to remove the license requirement. And using obfuscation may get both the asset and your account terminated.