1.16.4 new message: No suitable constructor could be found.

[CrystallDEV]

Describe the bug
It seems like ProtocolLib is unable to find the matching constructor for delivering a message to a player. I think this is caused by 1.16.4 adding UUIDs to each message delivered. I tried last week to find a fix for the error and noticed that ChatExtensions#getJsonFormatConstructor is trying to look for a packet constructor with 1 parameter, while the constructor I was able to find requires 3. Changing this fixed the initial error, but caused other errors. I think these are caused by the messages not correctly being built together to match the new constructor.

Im sadly missing the time currently to fix this, so maybe you guys can assist or continue where I stopped.

To Reproduce
Steps to reproduce the behavior:
My PlayerNPCLibrary is using protocollib to spawn in fake player npcs using several packets which are devliered through protocollib (If needed: The code of the library is public in my profile). After logging in for the first time the following error occurs once: https://pastebin.com/yHPJbQJj

Relogging does not trigger the error again and causes the library to work normally.

Version Info
https://pastebin.com/VPVGv9qm