VanillaCord v2.0

Well, seven ate nine, as usual. So, here we are, at the big 2.0 — a complete rewrite of VanillaCord using bridge-asm.

As you might have guessed, this release was prompted by the many internal changes to the Minecraft server in 1.20. Most of which that affected VanillaCord were refractorings of existing classes to have them exist as records. VanillaCord will now patch itself to conform to these changes; a strategy that can be easily updated to conform to future changes as well.

So, what's the bridge-asm for? In previous releases, VanillaCord used a mixture of classloading, reflection, and bytecode inspection to patch Minecraft servers, but that was no longer enough. VanillaCord now uses the same code Bridge does to generate a comprehensive class hierarchy to make patching decisions with.

VanillaCord v1.8

Another major update, another VanillaCord breaking change. If you're wanting to patch 1.18, you'd better be ready to repackage Minecraft Server Bundles.

That's right. After 10 long years, the format in which the vanilla Minecraft server is distributed had finally been changed, which means we had to change too. In order to patch a 1.18 server, VanillaCord now has to detect, extract, and load the bundled libraries before it can patch the server. It then performs the task of re-packaging the server-bundle to sustain the input/output format VanillaCord users have come to expect.

Naturally, this could have been done with less code than it was, but my focus was on compatibility. Should Mojang change the bundle format in future versions, it should be theoretically much easier for VanillaCord to be updated while still retaining backwards-compatibility for the previous formats.

VanillaCord v1.7

This is the first major revision to VanillaCord's actual code in several years. This time, by yours truly.

Over the past month, VanillaCord has been made better and faster by using as little reflection as we can get away with at runtime. This is done by altering the helper classes themselves during installation. The newer the Minecraft version, the directer we can make the references.

Oh, and since we're already altering the helper classes, I decided to also remove the incompatibility that caused us to have to maintain two branches in the first place. At the time of this writing, VanillaCord's "Active Branch" supports 11 major Minecraft versions, starting with 1.7.10.

Now with only one branch to maintain, it is no longer necessary to use the launcher that I wrote a couple years ago. We can finally return to the days where there's only one download page to patch 'em all.

Also, this release supports Java 16 and Velocity modern IP forwarding.

VanillaCord Launcher v1.6

This release creates and uses profiles to launch the VanillaCord branches. This means that in theory, the profiles and the list of them can be updated without having to update VanillaCord Launcher.

VanillaCord Launcher v1.5

This release uses Mojang's launcher meta to find and verify the Minecraft Server file downloads. This makes it able to download snapshots, pre-releases, and versions above 1.13.

VanillaCord Launcher v1.4

This is the first release of VanillaCord Launcher.

VanillaCord Duo v1.3

This is the first revision to deviate from the original release structure. It contains both the 1.12 and 1.7.10 branches within the jar. This is the only release to do so in this way, as it was soon to be replaced by VanillaCord Launcher.

Also, it added support for Java 9 and Java 10.

VanillaCord v1.2

This is the second revision of the original release. Quote from SpigotMC's update page:

• Added support for broken Mojang jars

VanillaCord v1.1

This is the first revision of the original release. Quote from SpigotMC's update page:
This forces the servers into offline mode. The online-mode property will only be used for commands (e.g /op which will now lookup the correct uuid if the server is set to online mode)

VanillaCord v1.0

This is the original release of VanillaCord.