Ok so , as a small developer that already released some stuff either free or paid, i saw my scripts getting leaked or even getting sold (even at higher prices that my own) !
this is a very good way now to handle these type of problems
BUT
if i want to purchase some script, as a customer, i dont want it to be encrypted , i will always edit them so much no matter how perfect they are, i just love to play around with them and adopt them to my framework and add new things or even remove unused stuff…
i suggest any other developers to not encrypt main files
so anybody that is paying for it , can edit it as they like to (they paid for it at the end so, its kinda unfair for it to be encrypted)
BUT …
maybe have some of the functions encrypted in another file like a utility file…
i think this will be the best of both side
TLDR:
from a developer to other developers
Dont encrypt main files , so the buyer can modify it as they like without any problem (it would be also a lot easier for you, because you don’t have to edit them for each customer)
on the other hand , encrypt some functions (maybe some that don’t need any editing anyway)
(this is just my idea, not that i am saying everybody should do this, but i think this is better than just encrypting everything)