Relevant documentation: http://docs.pocketmine.net/d5/d36/interfacepocketmine_1_1plugin_1_1_plugin_loader.html
pmf is easily decodeable I would go a php encoder and just have server owners need loaders to run them if you want to protect your source and or make sure none copy it
We had a discussion on this at the General Discussion forum about making code close-source. Our conclusion was that, However, this extension doesn't exist among the extensions in PocketMine-MP. Also, I don't recommend making plugins close-source as it will make it hard for other plugisn to interact with it. Why do you want your plugins in PMF?
The human race goes on and thrives because the descendents develop basing their knowledge on their ancestors. Otherwise, if Walt disallows anyone to use steam engines after his death, what will happen to us now? Moreover, hiding your source isn't necessary. People would not get better than you if they use your code. Moreover, if you are going for a great plugin, you must make it open-source. A great plugin always allows interaction with other plugins.
I have to agree with this. First of all, if you release your plugin, other people can't steal your code and release it in the repository and, if somehow there is a slip-up, you can just report it and it'll be removed. Second, what's the point in hiding the code? Every great plugin I've ever seen, Bukkit and PocketMine, have been open source, and allowing the community to help fix bugs, give suggestions to the code, etc have only made them better. Third, if you use the aforementioned ways to make it closed-source, it won't be able to be released in the repository. And finally, there's no true way to make anything closed-source. Even if it's extremely difficult to do, if a computer is able to read it, there will be a way to make a program to decompile it to an understandable format. So, all in all, making it closed-source has very little benefits and closes the windows on the many great benefits of open-source.
No. The way MCPE is compiled can make code close source. Just cache the compiled version of the PHP code.
GOOGLE LOADERS drop in your .so .dll into bin/php and then edit the php.ini file for example to use ion cube encoded files you add the loader for the version its encoded by. then add this to php.ini Code: zend_extension_ts = "ioncube_loader_win_5.4.dll" Extensions are super easy to install and use if your plugin needs it then add the extension and instruction on how to install it for users. You may say why go closed source when open source is better for everyone else. I support Open source myself when releasing stuff to public that I intend everyone to use, like I did with my PDO class that I hope people use more But what if you want to code a plugin for someone and there paying you to do so, you can not sell plugins themselves due to minecraft eula, but you can pay someone to code it for you, that is fine just as long as you don't go selling that plugin. Closed source allows you to do this with out worrying someone will just steal that plugin and all that work you put in. This is something I support 100% and well is really good way to protect your self as a developer
