![Wilder Wild [Fabric]](https://media.forgecdn.net/avatars/thumbnails/1201/201/256/256/638777948075313090.png)
Kicked from server/Packet mismatch
Dalethium opened this issue · 5 comments
Description of the Bug Encountered
Occasionally you will get kicked from a server due to a wilder-wild packet.
Steps To Reproduce
NA/inconsistent
Logs
Additional context
I understand that this is relatively vague, but if the latest log is not enough information, please let me know, and I'll try to provide any information you can ask me for.
That’s certainly… strange. It’s related to the leaf particles, specifically the big cluster of maple leaves that spawn and make a leaf litter when they hit the floor.
Would you be able to reproduce this in singleplayer, if it isn’t already?
I loaded up the same world in single player where I was getting kicked, and I didn't appear to get kicked. I will note that I tried disabling the leaves mixin in the configs to try to fix this, but it doesn't appear to have fixed it.
If you're unable to track this down, could we maybe have a config to disable this packet/feature from being sent entirely?
Is it possible there's a null check missing for the resource ID? The stream seems to fail when reading the resource identifier. The resource location could be blank due to another mod in my pack and could cause an unexpected number of bytes? Just a guess from a glance.
Thing is, there’s no reason it should be null- and everywhere it’s called in WW, it’s not null. Otherwise it would crash and this would’ve been fixed a month or two ago when it was in development.