JEI + click disconnect.
fobok1 opened this issue ยท 7 comments
Issue type:
Only keep the issue types that are applicable.
- ๐ Bug
Short description:
Clicking from JEI into (block or portable) logic programmer causes an immediate disconnect from a server.
Expected behaviour:
I expected that the object would appear in the programmer's selection box (as it does in single player) so I could set a variable to that item, and remain connected doing so.
Actual behaviour:
I am immediately disconnected from the server.
Steps to reproduce the problem:
- Open the logic programmer.
- Select item or list (the only ones I tested, there may be others).
- Click on an item in JEI to bring up the recipe/worldgen data.
- Click on the little + icon.
At that point, I am disconnected from the server.
Versions:
Exact versions of the following mods, not just latest.
- This mod: 0.11.10
- CyclopsCore: 0.11.5
- Minecraft: 1.12.2
- Forge: 14.23.2.2627
- Just Enough Items: 4.8.5.159 (also happened with 4.8.5.147)
Log file:
Does this happen with all items? Or just one specific item?
(It looks like an issue with a large NBT tag)
The test for my previous logs was gold ore, I believe, (I was trying to set up ore processing when I initially discovered this), and for the client logs I'll be including here, I did plain smooth stone just as a test. I also tried a few modded items when I submitted my initial report (so, it's possible the original logs I provided are one of those), to see if it was something specific, but I can't remember what ones I tested then.
This is the latest.log from my client. Right at the bottom of the log, you'll see I gave myself a logic programmer (I admit it, I was too lazy to run across my base for a quick test), the very next thing I did was try it and get disconnected. Then exited the game to grab the log.
I don't see anything special in the client logs.
The only relevant information in the server logs is this:
(CPacketTabComplete) was larger than I expected, found 3 bytes extra whilst reading packet 1
This packet is just a vanilla packet, so I don't really know what is going on there.
Can you try reproducing this with just ID+JEI installed? As I'm not able to reproduce this myself here.
Okay, I just went and tested that. The same thing happens again, even with just those installed.
Client latest.log
Server latest.log
Server debug.log
In case it's relevant, I'm connecting to the server through localhost.