Skip to content

Comments

MiniMessage as standard for V4#391

Open
VQ9 wants to merge 1 commit intotritonmc:v4from
VQ9:v4
Open

MiniMessage as standard for V4#391
VQ9 wants to merge 1 commit intotritonmc:v4from
VQ9:v4

Conversation

@VQ9
Copy link
Contributor

@VQ9 VQ9 commented Apr 9, 2024

For v4 the standard will hopefully by MiniMessage, this is an open discussion for people to comment on I guess. This commit effectively changes the default interpretation to be that minimessage is being used, and a legacy tag has been created to replace the minimessage one.

… v4, MiniMessage formatting will finally be the standard.
@diogotcorreia
Copy link
Member

As I said on Discord:

Thanks! I agree with you, but unfortunately I have to think about backwards compatibility a bit (or at least about migrations), so I can only merge that PR in the end (once I have decided on all the changes to the config files) and written the migrations

I'll keep this PR open, but will only merge it closer to final v4 release.

@diogotcorreia diogotcorreia added type:enhancement Improvement or enhancement to existing functionality module:core Related to the core module labels Apr 22, 2024
@diogotcorreia diogotcorreia added this to the 4.0.0 milestone Apr 22, 2024
@diogotcorreia diogotcorreia added the on hold Halted and will not be worked on at the moment label Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

module:core Related to the core module on hold Halted and will not be worked on at the moment type:enhancement Improvement or enhancement to existing functionality

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants