add rich message component support to configuration

[yannicklamprecht]

resolves #5449

TODOS:

• Wait for adventure 4.16.0 release
• remove mavenLocal() and migrate to version 4.16.0
• add changes to adventure patch

[Machine-Maker]

We should probably allow the ability to pass custom MiniMessage instances for this for custom tags and whatnot.

[imDaniX]

We should probably allow the ability to pass custom MiniMessage instances for this for custom tags and whatnot.

Having an option to pass custom ComponentSerializer in general would be helpful too.

As a side note, this will currently throw an exception if a user uses § in their string. I'm just thinking that there should be some safe railings for this case (like returning a def/null component), or at least some javadoc info mentioning the behavior.

[yannicklamprecht]

We should probably allow the ability to pass custom MiniMessage instances for this for custom tags and whatnot.

Done.

[lynxplay]

I think it would be great if we split this into

getRichMessage(path)
getRichMessage(path, defaultMini)

getComponent(path, ComponentSerialiser<T, String>, defaultStr)

that way, we also enable easy fetching for alternative formats down the line.

[emilyy-dev]

Generally looks good, my couple concerns are regarding documentation mostly

[lynxplay]

General "lets wait and see" for PaperMC/adventure#1034, as we could use ComponentDecoder over ComponentSerialiser if possible.

I'd give it a couple days, otherwise we'll commodore it down the line.

[emilyy-dev]

Also maybe the patch could/should be promoted to the adventure patch, would like to know if anyone has strong opinions against that

[yannicklamprecht]

General "lets wait and see" for KyoriPowered/adventure#1034, as we could use ComponentDecoder over ComponentSerialiser if possible.

I'd give it a couple days, otherwise we'll commodore it down the line.

Waiting another week or month will not kill it. So just wait for the decoder.

[Machine-Maker]

Should we add set methods as well? I don't think there are for other specific types, but since we aren't hooking Component into the snakeyaml type system, maybe some set methods would be good?

[yannicklamprecht]

Should we add set methods as well? I don't think there are for other specific types, but since we aren't hooking Component into the snakeyaml type system, maybe some set methods would be good?

Addressed with 72031ae

[yannicklamprecht]

Should we fixup this onto the adventure commit?

[lynxplay]

Yea 👍 add yourself as coauthor but yea

[yannicklamprecht]

Yea 👍 add yourself as coauthor but yea

Done.

addressed

addressed