161e853450
This commit restores that behaviour You may be asking yourself why we are completely ignoring any errors which come this far down the pipeline. The answer is quite simple: Mojang did it The default Mojang pipeline doesn't have any ChannelOutboundHandlerAdapter or similar instances, and thus nothing to handle exceptionCaught So when a channel.write() or channel.flush() fails, the error message is actually just passed straight to the future provided. It is then subsequently discarded, the channel closed, and no one except the user was any the wiser it actually happened! Unfortunately for us, the default exceptionCaught in this class sends a blaring warning to the server admins indicating that it couldn't send a packet to a disconnected user! We don't care about these warnings, if we did something wrong to disconnect the user, it is already logged in the proper location, as are broken sockets tl;dr no need to blare warnings on each write to a broken socket |
||
|---|---|---|
| Bukkit@a621d1683a | ||
| Bukkit-Patches | ||
| CraftBukkit@616c371a77 | ||
| CraftBukkit-Patches | ||
| .gitmodules | ||
| .travis.yml | ||
| applyPatches.sh | ||
| pom.xml | ||
| README.md | ||
| rebuildPatches.sh | ||
| upstreamMerge.sh | ||
Spigot 
High performance Minecraft server implementation
How To
Init a Craftbukkit and Bukkit module : git submodule update --init
Apply Patches : ./applyPatches.sh
Create patch for server
cd Spigot-Server
Add your file for commit : git add <file>
Commit : git commit -m <msg>
cd ..
Create Patch ./rebuildPatches.sh
Create patch for API
cd Spigot-API
Add your file for commit : git add <file>
Commit : git commit -m <msg>
cd ..
Create Patch ./rebuildPatches.sh
Compilation
We use maven to handle our dependencies.
- Install Maven 3
- Clone this repo and:
mvn clean install