I have just spent the past few days on codecademy working on the PHP. I have just finished it and feel pretty comfortable with the language. I'm sure this is a stupid question, but what next? Where should I go to start creating plugins, because I know there are certain functions that must be used in pocketmine. Please help!
Read the PocketMine source code. If you feel you are OK enough, you should be able to understand the whole code if you read starting from PocketMine.php. But the above is a semi-troll, because it is very hard to understand the source if you are new. The best is to read some documentations and tutorials, like those at the resources subforum of this plugin development forum. (You can find it above this thread)
I learn something's by looking at some peoples plugin codes but sometimes I also learn php from php.net but most of the time i just ask the great and genius PEmapmodder and swagboy47
Where is this located exactly? Or should I just feel comfortable with the all the files in /PocketMine-MP/src?
If you go to the "Plugin Resources" section, @shoghicp posted some links to important stuff such as a plugin tutorial to get you started, and I think links to PocketMine's GitHub (where the source code is located).
you can also check our organization for leaning pocketmine development . we haven't started yet vecause we are waiting for new students. here the link to the thread http://forums.pocketmine.net/threads/learning-development.3907/
looked at some plugins, the source code, and a few other things and I've got to say, my confidence has been demolished. I felt pretty good on codecademy but now I feel SO lost. Are there other things like codecademy I should do before diving into plugin development?
Actually, correct me if I'm wrong: The pocketmine source code is a bunch of code that creates variables, methods, classes etc. When you make a plugin, you extend the plugin class and reference methods and variables defined in the src. So you use php for the "structure" but pocketmine-created things for "the meat" of the plugin if you will. The trick is just figuring out which things to reference in each specific occasion.
PocketMine-MP had a wide range of class usage (as you see, so many classes, one file for each). Look at the documentation comments to help making plugins.
Yes. doccomment, the ones surrounded with /** blah blah blah @param blah $blah @return blah */ They are most useful, and more useful with tools like PHPStorm.
