The data is some kind of playerdata but I have no idea in what packet it is. With unintended i meant that a vanilla server.jar would not send data of this kind in that packet. This was confirmed to me by a ex-developer for that server. It cant be accessed by the standard ways of obtaining playerdata in forge and because I dont know in what packet the data is sent, I cant reverse engineer where I could access it. I know that this is strange, but like I said, this is for debugging purposes only and I will find a better and more stable solution for any productions builds, when I know where the data is sent. I know how it looks, so I could just look thought any packets with .contains(), if I had them as a string.