Closed Drumheld closed 5 years ago
An existing connection was forcibly closed by the remote host
from what I know is just a generic exception that occurs when a connection abruptly closes. Can you check for an exception that occurs around the same time? Both client and server. Is it reproducible? Does it really only happen with enchanted backpacks?
I will have to check back to the first instance of the crash, but I don't have that log at the moment. It is reproducible, as I had to roll back the world save to recover the lost items in our (thankfully) only other placed backpack with items inside, and the same issue occurred when I tried to re-enchant the same backpack with the same enchantment.
I resolved the issue with the initial world save by removing all backpack mods (server and client) and restoring them after a FML confirm at server launch and destroying the now defunct in-game backpack instances. I replaced the mod into the mod-list and backpacks were again craftable/wearable.
The enchanted backpacks are the only thing that has caused this problem. I enchanted the backpack with Protection IV, held it in my hand, and placed it on the ground. The moment I placed it (and thereafter, whenever anybody entered the chunk facing the direction of the backpack) the client would crash and the server would eject them with the above message.
I removed my shaders preset to ensure it wasn't some kind of local phenomenon having to do with a light source or the enchantment glisten but the crash persisted.
Please provide a mod list
[...] the client would crash and the server would eject them with the above message.
The client crash log would also be very helpful here. I hope you understand that without this information there's nothing we can to fix this bug.
Will reopen when we have a full client (?) crash report we can use.
I enchanted a wearable backpack with Protection IV and then placed it. as soon as the backpack enters the visual screen space of any player, the server kicks that player.