JCore

What is it?

JCore is a land management, economy, and chat API. It's main part is the land management.

For Server Owners

Plugins may use this plugin to limit their plugins functionality to specific areas. One example is towns. The plugin store the land data in highly compressed binary files. That way you can use a lot of land without the data file growing out of control. A chunk is at maximum 1272 bytes, that means that one Gigabyte is roughly 800 000 chunks.

For Developers

JCore basicly limits the events so that events are only fired to those plugins that owns the land that the event is fired from. For example when a BlockPlaceEvent is fired it will directly send it to the land area(In the plugin referred as Collection) that the block was placed in. Other "Collections" will not receive that event. The event can also be passed to a plot within the collection. For simplicity the plugin does also contains all you need for currency, so there is no need to link with Vault or a currency plugin, JCore does that for you. The same applies to chat.

Questions

Is it very storage consuming?

Well that depends. A chunk is at maximum 1272 bytes, that means that one Gigabyte is roughly 800 000 chunks. So if you intend to claim like 80 million chunks you might start getting problems. Note that area claiming is freeform so a chunk might be smaller than 1272 byte.

Is it very ram consuming

That is optional, the plugin has a land cache. You can configure how many chunks that can at most be contained within it. A chunk is 1272 bytes at most. Note that it takes a little more data while in the ram, but not more than a few bytes extra. The cache does also contain a list of the coordinates of all chunks contained in the save file. This list can't be configured, and it most be there for good efficiency in the cache (It's pointless to search the file for a chunk that isn't there anyway). The size of that list is exactly the amount chunks in the save file time eight. So a file with 800 000 chunks will return in a list that is 64 megabytes big.

Does the plugin creates lag?

Not that I'm aware of. It depends totally on the plugins that use it. It does use any events by itself, it only passes them to the plugin that owns the area that the event was fired from. The saving is handled in it's own threads, and does not interfere with the main mine craft thread in any way. On shutdown there might be a delay while its saving, if a lot of area is claimed it might take a few seconds. If the server is under heavy load when it starts a save thread it might be possible that a slight lag might show. Note that a save thread is not very CPU consuming. The speed of the saving is most often limited to the speed of your hard drive, a modern SSD drive will make the saving go much faster than a old SATA drive.

Developer Section

Backwards capability with old plugins

What if I have made a plugin and want this to work with JCore. Do I need to totally rewrite the plugin? Well in most cases you can just make another plugin the gives the player the permission needed to use the plugin based on his current location. Lets say that you have made a world edit plugin. And you want it to only be used inside the specific collection. Then you can simply just give the permission necessary to use it when the players enter the collection, and then remove it when he steps out.