error with the latest dev build

[Z3r0xh]

Describe the bug
console spam

Software brand
NullcordX 3.8.8

Plugins

How To Reproduce
Steps to reproduce the behavior:
Just place the latest dev build and wait for the users to enter

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
Full server log (https://mclo.gs/e6bRQgD)

Additional context

NullcordX now accepts event packets, currently back to 2.4.1

[jonesdevelopment]

I'm currently using 2.4.1

Try the latest dev build from Jenkins:
https://ci.codemc.io/job/retrooper/job/packetevents/lastSuccessfulBuild/

[Z3r0xh]

I'm currently using 2.4.1

Try the latest dev build from Jenkins: https://ci.codemc.io/job/retrooper/job/packetevents/lastSuccessfulBuild/

The one I mean that failed was that one. 2.5.0. I mean I had to downgrade to 2.4.1 again

[jonesdevelopment]

The one I mean that failed was that one. 2.5.0. I mean I had to downgrade to 2.4.1 again

Oh, sorry, I misunderstood.

[Z3r0xh]

The one I mean that failed was that one. 2.5.0. I mean I had to downgrade to 2.4.1 again

Oh, sorry, I misunderstood.

Don't worry :D

[libraryaddict]

So the problem with IJukeboxSong is that a Component can actually be a raw string.
Except I'm not familiar enough with packetevents and the utilities to know how that implementation would look.

A brief look into nms internals seems like a component is written as a raw string if it's simple enough, otherwise it's written as json.
So packetevents could just handle this all as a string but then I don't know how to handle https://github.com/retrooper/packetevents/blob/2.0/api/src/main/java/com/github/retrooper/packetevents/protocol/item/jukebox/JukeboxSongs.java#L47

The actual implemention of jukebox was wrong, because I had naively believed that the vanilla jukebox songs were being sent as I had experienced with the other registries. Turns out you need a datapack installed or the code never fires