Development
=== DEVELOPMENT ===
Hey guys, this plugin is written verry... let's see.. open. As for this I support you with as many help as I can. This plugin has no so called API, it is written well enough protected so I can share the most of them with you. I use the static possibilities often, so sometimes it is just calling a static method to do your stuff. These static "points" are listed below in this article lower. First of all, some words to you, on the beginning of your journey in my plugin or in the middle of the development; I'm very happy if you do develop expansions to my plugin, and sure I will share them with the public on these pages too, if you want. I'm making so many efforst to make the plugin the best for users, and for developers also. If you have any doubts about your success with your project... if you can write a plugin, you can make an expansion to this plugin too, it does not mean much more knownledge, and there are tutorials written by me detailed enough to learn which module how works. If you have any questions, feel free to ask me on the forum (which is not yet created, since the plugin is under development atm).
The plugin is structured into layers. The deepest layer is the kernel, which only be handled by bukkit. The kernel is paired with a plugin shell, which basically the core of the plugin. It contains the ZoneManager, the command handler (ZureExecutor) and so on. You should use the shell for handle my plugin. Do not forget to chech the static methods of the ZureExecutor class too.
First step - setting up
Either if you use Eclipse or NetBeans, you should set up your project, I don't think if you have problem with that. After this, add the Zure.jar file to the libraries. For development there are no other versions currently and no javadoc online, but I do comment many things and will post the javadoc later on.
Second step - hello world
There are two possibilities, making a set-up-addon for my plugin, or making your plugin and just hooking into Zure. I will detail the first one, if you choose the second, you have your own way. To make a set-up-addon, first, add a .yml file to the project, just like as you make a plugin. Instead of "plugin.yml" name it "addon.yml".
Messing aroung
- creating a new flag
- modding an existing flag
Comments