LegacyComponentSerializer does not deserialize components properly if formatting code char is capitalized about adventure HOT 4 CLOSED

Yep, I can test and confirm that capitalisation doesn't matter so this is indeed a bug!

from adventure.

Do capital letters after section signs render in the client? If not, then this isn't a bug report and something that can already be achieved by modifying the serializer using the builder to set additional formats.

from adventure.

I quickly tested this (in a lazy way, so if you don't trust the method feel free to double check) - sending a custom brand packet which if I recall correctly the client only supports Legacy in. I tried §etest and §Etest which both appear as "test" in yellow on the vanilla client. So I believe this is indeed a bug.

Also noted on the additional formats, should have probably checked that before coming up with my other solution.

from adventure.

Thanks, also applied your suggested fix to Essentials and it appears to work beautifully. Should hold us over until it gets addressed over here.

from adventure.