Closed drakray closed 2 years ago
FB does not send any packets besides the single recipemessage packet during crafting (which sends a single recipe id, that would never exceed the protocol limit).
If your recipe book is literally too large and preventing connections, as it appears to be, you can try the older version of FB which has the recipe book nuke, but all recipes are synced on login anyway post 1.13, so you may have problems regardless.
But yeah, fb cannot cause this kind of problem
I'm not sure this is caused by FWB, but I'm out of idea.
I get an error on my server console, saying
[29Nov.2021 19:40:28.449] [Netty Epoll Server IO #3/ERROR] [net.minecraft.network.NettyCompressionEncoder/]: Attempted to send packet over maximum protocol size: 2099300 > 2097152
followed by a VERY large block of text looking like this
I "cleaned" it, to see what it is, and its a list of recipe name They seem to correspond to the recipeBook.recipes entry list from the player.dat file (opened with NBTExplorer)
Some mods have reaaaally long recipe name(environmental, mana-and-artifice, architects_palette) It seems this list is sent twice in the same packet(might be the recipeBook.toBeDisplayed that is also sent) Do you think it's inadvertently caused by FWB, as a result of sending all recipe at once? Something that would otherwise only be a problem when a player unlock every recipe?
Could it be fixed by removing the recipeBook entry altogether? Or splitting the packet in multiple smaller one? It also doesn't seem "compressed", as I could just remove the hexChar, then the newLine, and finally splitting on newLine by modName to get the list in a text file with Notepad++
Any idea?