I want to publish a plugin but I do not want the users to change the author and the name of the plugin, for this I would like to make some kind of obfuscator just like svile does not change the propriety that I am, I know svile does with which in the function onEnable if it has not written the name of it in author in the plugin and the name of the plugin the plugin will not work, I would like to do the same, which type of encryption does svile use? and is it possible to break it? and also if you take some part of the code in onEnable the plugin will not work correctly
This has already been discussed here: https://forums.pmmp.io/threads/how-to-make-phar-files-unreadable.3370/ In a nutshell, you can't prevent anyone who can code a plugin from doing that; you can only use obfuscation to make it too difficult for non-programmers to do so on their own, or too time-consuming and not interesting enough for anyone with the necessary skills to bother.
I agree with @Awzaw, it's difficult, annoying and time-consuming to work with something like svilex's SW, it feels like you'd be better off writing your own SkyWars plugin and no I'm definitely not talking about myself.
you cant this is the shortest possible explanation ever even if you did it someone will happily undo what you did for breakfast
so is it possible to break the svile obfuscator so easy? there must be some that are almost impossible
None actually. No matter how you obfuscate your code, you'll need to deobfuscate the code while you're executing the program. Which means for every PHP obfuscator, there must be a deobfuscator.
link it and maybe ill do it for breakfast also encrypting means no one can use it yes you can encrypt your plugin but now users cant use it unless you give them the encryption key BUT that key will also give them the source code that's encryption dont confuse it with obfuscation