Netty

 Implement an uber efficient network engine based on the
 Java NIO framework Netty. This is basically a complete rewrite of the
 Minecraft network engine with many distinct advantages. First and foremost,
 there will no longer be the horrid, and redundant case of 2, or even at
 times, 3 threads per a connection. Instead low level select/epoll based NIO
 is used. The number of threads used for network reading and writing will
 scale automatically to the number of cores for use on your server. In most
 cases this will be around 8 threads for a 4 core server, much better than the
 up to 1000 threads that could be in use at one time with the old engine. To
 facilitate asynchronous packet sending or receiving (currently only chat), a
 thread pool of 16 threads is kept handy. == Plugin incompatibilities As a
 side effect of this change, plugins which rely on very specific
 implementation level details within Minecraft are broken. At this point in
 time, TagAPI and ProtocolLib are affected. If you are a user of ProtocolLib
 you are advised to update to the latest build, where full support is enabled.
 If you are a user of TagAPI, support has not yet been added, so you will need
 to install the updated ProtocolLib so that TagAPI may use its functions. ==
 Stability The code within this commit has been very lightly tested in
 production (300 players for approximately 24 hours), however it is not
 guaranteed to be free from all bugs. If you experence weird connection
 behaviour, reporting the bug and steps to reproduce are advised. You are also
 free to downgrade to the latest recommend build, which is guaranteed to be
 stable. == Summary This commit provides a reduction in threads, which gives
 the CPU / operating system more time to allocate to the main server threads,
 as well as various other side benefits such as chat thread pooling and a
 slight reduction in latency. This commit is licensed under the Creative
 Commons Attribution-ShareAlike 3.0 Unported license.

Conflicts:
	src/main/java/net/minecraft/server/DedicatedServer.java
	src/main/java/org/spigotmc/netty/CipherCodec.java
	src/main/java/org/spigotmc/netty/NettyNetworkManager.java
	src/main/java/org/spigotmc/netty/NettyServerConnection.java
Double dependencies are bad, silly cherry-picks.
Signed-off-by: Steven Downer <grinch@outlook.com>
Adds version number for maven-deploy-plugin

Signed-off-by: XemsDoom <moser.luca@gmail.com>
Changes libigot's repository to the right name

Signed-off-by: XemsDoom <moser.luca@gmail.com>
Save entity counts for randomly spawned creatures to avoid repeatedly traversing over the entity slices
Netty

 Implement an uber efficient network engine based on the
 Java NIO framework Netty. This is basically a complete rewrite of the
 Minecraft network engine with many distinct advantages. First and foremost,
 there will no longer be the horrid, and redundant case of 2, or even at
 times, 3 threads per a connection. Instead low level select/epoll based NIO
 is used. The number of threads used for network reading and writing will
 scale automatically to the number of cores for use on your server. In most
 cases this will be around 8 threads for a 4 core server, much better than the
 up to 1000 threads that could be in use at one time with the old engine. To
 facilitate asynchronous packet sending or receiving (currently only chat), a
 thread pool of 16 threads is kept handy. == Plugin incompatibilities As a
 side effect of this change, plugins which rely on very specific
 implementation level details within Minecraft are broken. At this point in
 time, TagAPI and ProtocolLib are affected. If you are a user of ProtocolLib
 you are advised to update to the latest build, where full support is enabled.
 If you are a user of TagAPI, support has not yet been added, so you will need
 to install the updated ProtocolLib so that TagAPI may use its functions. ==
 Stability The code within this commit has been very lightly tested in
 production (300 players for approximately 24 hours), however it is not
 guaranteed to be free from all bugs. If you experence weird connection
 behaviour, reporting the bug and steps to reproduce are advised. You are also
 free to downgrade to the latest recommend build, which is guaranteed to be
 stable. == Summary This commit provides a reduction in threads, which gives
 the CPU / operating system more time to allocate to the main server threads,
 as well as various other side benefits such as chat thread pooling and a
 slight reduction in latency. This commit is licensed under the Creative
 Commons Attribution-ShareAlike 3.0 Unported license.

Conflicts:
	src/main/java/org/spigotmc/MultiplexingServerConnection.java
	src/main/java/org/spigotmc/netty/CipherCodec.java
	src/main/java/org/spigotmc/netty/NettyNetworkManager.java
	src/main/java/org/spigotmc/netty/NettyServerConnection.java
Forgot to remove PacketEncoder
Signed-off-by: Steven Downer <grinch@outlook.com>
Revert "Adds version number for maven-deploy-plugin"

This reverts commit afecfe063d3cfa28d99e10312a4d7b40f551c2a8.
Add version to maven-deploy-plugin + seal

org.libigot
Make netty configurable.

Signed-off-by: V10lator <v10lator@myway.de>
Conflicts:
	src/main/resources/configurations/bukkit.yml
Fix bukkit.ymls header.
Fix some more bukkit.yml issues.
This changes links to Libigot and tries to fix the snipped commits.

Signed-off-by: V10lator <v10lator@myway.de>
update login
Merge branch 'master' of https://github.com/Libigot/Libigot