Closed JanCantCode closed 1 year ago
I also noticed that yesterday, seems like I have messed up some indecies. If you still wan't to inspect the actual data, I recommend using the export feature since this always exports the saved data and not what is displayed on the frontend.
Will investigate
oh alright, thanks for the answer.
do the exportable logs also care about blacklists / whitelists?
also the mod now made me unable to join any server with seemingly random kick messages https://cdn.discordapp.com/attachments/669557283767844894/1106189544455405648/image.png https://cdn.discordapp.com/attachments/669557283767844894/1106189545021636659/image.png https://cdn.discordapp.com/attachments/669557283767844894/1106189544790966343/image.png
do the exportable logs also care about blacklists / whitelists?
Generally, yes
also the mod now made me unable to join any server with seemingly random kick messages
Seems weird, is probably a serialization error. Mind sharing some console errors from your client?
the issue seems to have resolved itsself after several restarts. but no errors appeared in the latest.log when getting kicked btw
Interesting, will try to reproduce it / fix it later. I do have some ideas where to start already though.
Also @JanCantCode (forgot to ask), which version of minecraft and packetlogger are you using?
the newest release, 1.19.4
(from modrinth)
Thanks.
So from what I can tell is that most likely
I will publish a new version in a bit with those fixes and improved error logging. If any of those errors should happen again, the console will contain more useful information.
I noticed something odd with the registry error now. I think the problem is more fundamental than I anticipated. Will first analyze this further before publishing a new version.
Should now be fixed in 1.6.1
issue
when clicking on a packet, in this case a setContainerContent packet, the contents actually belong to a particle spawn packet.
example
i have attempted reloading etc.