This is an immature API!
This is not to say that it is immature itself
That is to say, it's just born, and it doesn't have any use (now except when you use the two examples PlayersAsMarks and Teleporter together, you can teleport yourself to other players).
In other words, if you're a user instead of a developer, this is currently meaningless.
This API is bidirectional
This API only provides the function of integrating and providing marks
That is to say, this plug-in does not store marks as you think, but needs to use other plugins to store them.
What can this plugin do? 1
For those developers want to record or use marks
For example, if you want a teleporting plugin, which can teleport a player to a residence, or to another player, or a mob, or a preseted position.
This plugin formerly need to ask for the residence plugin, get the player and mobs, and even write and save files.
The plugin will be very complex because there are lots of completely different logics to implement.
However, if the residence can provide the residence as marks, and some special plugins can provide the players, mobs as marks, and plugins provide save/write custom marks
——what you should do is, to get the mark, and teleport the player.
What can this plugin do? 2
For the server owners
Many owner will get bored when they have to set the same positions for every plugin.
But if the plugins can use this API
——want they should do is, use a plugin to save the marks, then other plugins can directly use it.
How to develop with the API?
Download 'MarksAPI.jar' and use it
The core class is MarksManager. The detailed infos please wait for the WIKI.
You may check out the two examples PlayersAsMarks and Teleporter first.
Others
Need your help
You can participate in coding this API, or provide services such as marks reading and writing.
I'm more familiar with C#, and I'm just coding Java with my knowledge of C#. Please criticize.
Welcome Issues and Pull Requests.
You may contact me (in any way) to directly join the project instead of pull requests.
