Kezz

Colour with transparency

2

With the new text display entities comes an obvious good use case to stick components everywhere to make stuff pretty. However, I can't use adventure in the entire creation of...

feature: MiniMessageTranslator

1

Closes #971

It's a fairly common thing to want to use the GlobalTranslator to render MiniMessage strings. We should provide a utility class that can create a simple Translator implementation that renders...

It would be nice to be able to set a pre/post processor for _all_ serializers - this could mean we could introduce a common `ComponentSerializer.Builder` interface. For example, it could...

This should potentially default to `Component#compact` as the most common use case for joining is just essentially joining together a list of strings but as components.

Some method (or methods?) that can "wrap" a component serializer, changing the input/output/serialized types as needed. Perhaps something like: ```java ComponentSerializer ComponentSerializer#mapInput(Function mapper) ```

In the image below, the user doesn't have permission for any of the flags this command has. Therefore this shouldn't be shown in tab completion. 

We too often get people who are just on outdated versions, which we can't easily spot. Including version information in debug logging would help spot this

Users of `adventure-platform` are likely to want to use a `ComponentLogger` and the set-up for making a `ComponentLogger` is something that could be provided by `adventure-platform`

This makes IDEs and other linting tools nag at you for not using try-with-resources and for not closing it. It's not really necessary nor particularly useful in this case for...