Skip to content

Use MiniMessage in favor of legacy color codes - #143

Open
Earth1283 wants to merge 1 commit into
nickuc-com:developfrom
Earth1283:use-minimessage
Open

Use MiniMessage in favor of legacy color codes#143
Earth1283 wants to merge 1 commit into
nickuc-com:developfrom
Earth1283:use-minimessage

Conversation

@Earth1283

Copy link
Copy Markdown

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

@nickuc nickuc added the enhancement New feature or request label Jul 24, 2026
@nickuc

nickuc commented Jul 24, 2026

Copy link
Copy Markdown
Member

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?

@nickuc nickuc mentioned this pull request Jul 24, 2026
@Earth1283

Copy link
Copy Markdown
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants