Use MiniMessage in favor of legacy color codes

[Earth1283]

This PR switches the legacy color codes (§ and &) to newer MiniMessage colors (such as gradient:#HEXHEX:HEXHEX).

[nickuc]

Hi, @Earth1283!

Thank you once again for your contribution!

I’ll take a closer look at the PR in the next few days.

My concern is how Adventure support will work for older versions, such as Paper 1.8.9, which don’t implement the API in the Player interface.

One idea I had is that, instead of sending the Adventure component to the player in unsupported versions, maybe we should convert them to the legacy color codes first?

[Earth1283]

ViaRewind (the plugin that allows 1.7.x & 1.8x clients to join 1.9+ servers) hooks into ViaVersion, which already handles MiniMessage Deserialization for us, and automatically downsamples the RGB codes to the legacy color codes (§0 through §f), so they won't crash

[nickuc]

ViaRewind (the plugin that allows 1.7.x & 1.8x clients to join 1.9+ servers) hooks into ViaVersion, which already handles MiniMessage Deserialization for us, and automatically downsamples the RGB codes to the legacy color codes (§0 through §f), so they won't crash

My concern is that this might cause a problem on the server side in legacy builds of Paper. The idea is to maintain support for the plugin for v1.7 – v26.2.

We also need to test whether it works properly if the server is using Adventure v5, while we are using Adventure v4.

[lokspel]

Why kotlin and why not just < red >, if it supports and etc?

[nickuc]

Why kotlin and why not just < red >, if it supports and etc?

I agree. It's better to keep the Java code and not replace the existing colors with arbitrary hex values.

[Earth1283]

Addressing these issues, give me a couple days