Well, I have made about 40 plugins using Eclipse. I am fully aware that some people prefer NetBeans, but I don't understand why. After viewing Nikikokun's plugin tutorial the handle, I was "inspired" to write and compile a plugin using NetBeans, and while it seemed to be a similar experience, there were a few things that I noticed right away that I didn't like: Ease of use towards lazy people was not great. When I type in something like Player player = event.getPlayer() and I haven't imported player into the class yet, with Eclipse I just double click on the underlined Player and I click import org.bukkit.entity.Player. Using NetBeans, however, afaik the easiest way is to right click and choose "Fix imports", wich you can do with Eclipse as well, but I didn't like that I couldn't just double click any problem and get what Eclipse calls a "Quick Fix". How stupid it was to make a new YAML file (plugin.yml). I finally found new yml file and clicked it. I named it plugin.yml, which for some reason saved the file as plugin.yml.yml. The worst part though, was after saving it and just assuming that it would be included in the .jar, after starting my test server and seeing that it didn't include plugin.yml, I was disappointed. After a simple file move, I realized that it was pretty easy to do, you just had to know how to do it. In eclipse though, you just make a new file called plugin.yml and edit it, it is included in the .jar in the right place. I was also pleased with the relatively (to eclipse) quick startup time of NetBeans, but my slow Eclipse start is most likely due to the ~50 Java Projects in there. I was extremely satisfied with the "Clean and Build" option, but displeased with the annoying process of navigating to the project/dist folder just to copy + paste the test version onto my test server. In Eclipse it isn't much better, when exporting a project it exports it as the last used jar name unless you specify otherwise, with no consideration of what project you are exporting. For example, if I export 3co as 3co.jar, then click on SimpleAdmin and export it, it would export it as 3co.jar as well. The plus side to Eclipse's way of doing things is the ability to have 1 folder where all of your jar exports are located. Lastsly, I realize that most of my problems/gripes could be easily fixed and that I am just a total n00b to NetBeans and to the more intricate side of Eclipse. Thoughts?