Anti Leak system for resources.

[David_]

So, there has been a lot of drama with mcm and [Censored]/BS recently and they are continuing leaking even more and more developer resources. Just today I saw WifiSpy or what's his name leak a 29.99£ resource which is terrible.

I believe there should be something in mcm backend that developers or resource creators could implement into their work so it wouldn't be so easy to leak everything.

I'm pretty sure spigotmc.org has something like this so mcm should too.

I'm pretty sure I haven't seen this suggested, sorry if I missed it.

 

[Justis]

What Spigot provides is easily removed from the source even without decompiling, just simple bytecode editing. The protection it provides is extremely minimal. That said, developers can use it to make cracking at least more difficult, through their own means, and for that reason alone, it is already planned and under development.

We’ll also be providing additional restrictions and functions for creators to have at their disposal for protecting themselves against leakers. However, the best protection will always be the protection the developers implement themselves, because it’s unpredictable.

Moreover, we’ll be drafting additional wikis for our creators and pursuing our own legal actions.
We encourage every creator to pursue legal actions as well, to take down their own content. Not just to protect themselves, but to make maintaining these sites and leaking other creators’ content more difficult for the thieves behind them.

 

[Eccat]

Could you have a database that resources have to connect to to verify?

 

[Zyger]

Could you have a database that resources have to connect to to verify?

Pretty sure they could just remove it from the code

 

[BOOP]

Pretty sure they could just remove it from the code

Just have all the code on a database and the plugin connects to and pulls from that, only allow one server to connect with certain credentials at a time. ezpz problem solved suggestion closed and accepted there we go

 

[DarkKnights22]

Just have all the code on a database and the plugin connects to and pulls from that, only allow one server to connect with certain credentials at a time. ezpz problem solved suggestion closed and accepted there we go

Theoratically this is a good idea lol. Practically, I don't really think so as it would take ages.

 

[vk2gpz]

What Spigot provides is easily removed from the source even without decompiling, just simple bytecode editing. The protection it provides is extremely minimal. That said, developers can use it to make cracking at least more difficult, through their own means, and for that reason alone, it is already planned and under development.

We’ll also be providing additional restrictions and functions for creators to have at their disposal for protecting themselves against leakers. However, the best protection will always be the protection the developers implement themselves, because it’s unpredictable.

Moreover, we’ll be drafting additional wikis for our creators and pursuing our own legal actions.
We encourage every creator to pursue legal actions as well, to take down their own content. Not just to protect themselves, but to make maintaining these sites and leaking other creators’ content more difficult for the thieves behind them.

If your understanding of spigot’s protection is just user I’d inserted and you can simply remove it, then you don’t understand what that system is capable of. One can properly exploit spigot’s system to prevent leaking.

 

[DarkKnights22]

DarkKnights brings a good point. When you offload a plugin to a server, that means taking out the logical functions from the purchased copy, and putting those functions on a server that communicates with the purchased copy, sending data back and forth. While giving more control to who accesses the full plugin, this new form of communication now has latency (time to communicate data) between the server (minecraft server) and the processing (thinking/functions) server. This latency is further amplified if the servers are further apart. One might argue to get more logic-servers in different regions, but that obviously increases costs on the developer's end, and ultimately will reflect onto the price of the plugin itself. In an ideal world, the idea of having processing/logic servers would be perfect to solving the issue of pirating/cracking, but latency and some other minor factors make this impractical, despite sounding good on paper.

Exactly this. If in the future the costs go down or some kind of new miracle machine comes out, we'll all switch to it xD
For now, though, I think its best not, unless you have some sort of crazy idea..

 

[Mick]

What Spigot provides is easily removed from the source even without decompiling, just simple bytecode editing. The protection it provides is extremely minimal. That said, developers can use it to make cracking at least more difficult, through their own means, and for that reason alone, it is already planned and under development.

We’ll also be providing additional restrictions and functions for creators to have at their disposal for protecting themselves against leakers. However, the best protection will always be the protection the developers implement themselves, because it’s unpredictable.

Moreover, we’ll be drafting additional wikis for our creators and pursuing our own legal actions.
We encourage every creator to pursue legal actions as well, to take down their own content. Not just to protect themselves, but to make maintaining these sites and leaking other creators’ content more difficult for the thieves behind them.

Denied, thanks for the suggestion.