This blog post is about minecraft development with gradle and some of the most crucial tools that make your life much easier.
This post assumes you have a build file similar to the one we had at the end of the first gradle blog post.
Reusing or accessing code from other projects with gradle is very easy. This blog posts dives into publishing dependencies to your local maven repository (or remote) to use it in another project. We also take a short look at online repositories and the small extras you have to account for when your projects are minecraft plugins.
If you are not familiar with gradle yet, have a look at my previous post about gradle basics.
With the introduction of paper plugins, paper decided to drop support for the ConfigurationSerializable interface.
While this interface and the system behind it provided a usable way to de/serialise an object fairly easily, it wasn't ideal by any means.
It was hard to learn and required a lot of boilerplate code to simply de/serialise an object.
So we're going to say goodbye to it. It won't be missed.
This blog post is about logging and writing information to the console in Minecraft. There are a lot of ways to write data to the Minecraft console. And there are a lot of bad or wrong ways to write to the Minecraft console. We'll start by looking at some bad practices, then move on to the built-in plugin logger, and finish with a look at slf4j.
This blog post is about developing Minecraft plugins for Paper and Spigot servers using Gradle. The Minecraft community has built a huge ecosystem for Minecraft around the Gradle build tool. Instead of throwing a sample Gradle file at you, we will go through this step by step. We will start with the basic Gradle layout, set up repositories and dependencies, and move on to plugins.
The minecraft main class, or the class which usually extends JavaPlugin, is nearly always subject of discussions when
it comes to naming.
In this post I try to explain my point of view, and also show my approach on naming them.