Asset Escrow
Last updated
Last updated
Over the past few years, we’ve seen resource authors go to great lengths to use obfuscation, IP locking, remote code loading and other methods in an attempt to protect source code. Unfortunately these methods each come with a plethora of issues that many are all too familiar with. Not only do most of these tools significantly slow down the performance of your code, they also impose a wide variety of security concerns. As a result, we do not condone such content on our platform as outlined in our .
We are great advocates of open source, and encourage the community to share their research and resources so that everyone can collaborate and build off each other. A community functions best when working together. At the same time we understand that some resource developers would like to keep their code and their assets under their control. If you are one of those people, this is for you.
The Asset Escrow system, developed in partnership with , provides a reasonable alternative to obfuscation and IP locking. By ensuring purchase ownership, your content will, and can only run on the servers of your customers, nowhere else. On top of that, your resources will be encrypted to prevent your work from being leaked.
In this initial version we focused on support for Lua 5.4, YFT and YDR files. If you use Lua scripts, make sure to enable lua54 'yes' in your fxmanifest.lua. Support for the JavaScript and C# runtimes, and other file types is coming very soon!
Note that you need server version 5181 or above to run resources using this feature.
Your server artifacts are likely outdated. Update your server to version 5181 or above.
Try restarting your server and make sure your server license key is correct. If you bought the resource on the wrong account, you can transfer it to another account on keymaster.
Files were possibly corrupted during transfer. Ensure hidden files are copied; the .fxap file in a protected resource must be included. Some FTP programs skip these files.