ME P2P Tunnel - ME Dual Interface, Server kicks you when opening the ME interface terminal, with over 100 p2p dual interfaces pr dual p2p interface
Devtron3D opened this issue ยท 0 comments
Your GTNH Discord Username
Devtron
Your Pack Version
2.7.2
Your Server
ValhallaMC - GTOH
Java Version
Java 17
Type of Server
Vanilla Forge
Your Actions
opening the ME interface terminal cause the server to do this to my client
I added to my system 5x p2p interfaces, that each connect to 130 p2p interfaces for a total of 128 new standard assembly lines for normal crafting. 5x130 = 650 connections
The p2p interface here is connected to 100 of the outputs, there are 5 of these pattern interfaces
When i connect more than 100 the server kick me with
[01:28:43] [Server thread/ERROR] [FML/]: SimpleChannelHandlerWrapper exception
java.lang.IllegalArgumentException: Sorry AE2 made a 2636290 byte packet by accident!
If i relog and open the interfaces terminal again, same thing happens.
If i disable the assembly line p2p to about 100 pr p2p pattern interface, it works fine
I have tested by separating wireless connectors, p2p dual interfaces and all that, but the only thing that worked was keeping the number at 100 or below, i have connected/disconnected the front and backend of the new assembly array to see if it was an issue with some AE, but the parts that were disconnected work fine when connected again and another part of the crafting array gets disconnected,
I do not know if this is a max for p2p interfaces connected to one main interface or some other error
I can repeat this again and again , so i will leave 30 assembly lines disconnected for now, if a copy of the world is needed, please let me know
server is running 2.7.2 java 17
Crash Report
open_interface_terminal_LOG.txt
This is the section of the server log where I log back in, open the interface terminal, and get kicked
[01:28:43] [Server thread/ERROR] [FML/]: SimpleChannelHandlerWrapper exception
java.lang.IllegalArgumentException: Sorry AE2 made a 2636290 byte packet by accident!
Final Checklist
- I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying the crash still exists will prompt us to investigate and reopen it once we confirm your report.
- I can reproduce this crash consistently by following the exact steps I described above.
- I have asked other people and they confirm they also crash by following the exact steps I described above.