Claxtastic

I've been meaning to do this. When one of my players is around and able to graciously volunteer I'll try it and report back. Just tried reproducing on a vanilla server. Ran flawlessly.

I've been meaning to do this. When one of my players is around and able to graciously volunteer I'll try it and report back.

On my own network, same machine that I run my client from as well. 50 down, 6 up. Not great I know. But like I said, this is just a private server of at most 7 people, and I have NEVER encountered these issues before, even when I had 25 down and 2 up. i5 4670, 16 GB of RAM (3.5G given to server) Win 10. Server is also running off of a Samsung 850 EVO SSD.

I did have one of my players do "tracert [myip]" in cmd, and while many requests had low ping (around 25ms) others timed out. I've never had these issues before though running a server. My speeds have actually only gotten better since the last time I ran my server. It is also just strange to me that this ONLY occurs when players are near. We can play for hours just find if we aren't in the same chunk, but once we get in the same chunk and stay there for awhile, the server just dies and eventually times players out.

This issue has been plaguing my private custom modpack server for some time now. It seemed at first as though players would randomly mass timeout, sometimes where even I timeout (I run the server on the same network I play on.) But now it has become pretty obvious that the timeouts only happen when players are near each other. My TPS is fine (better than it has ever been in the past, really) and nothing is printed to the client or server logs when this is happening. That is, nothing other than "Disconnect: Timed Out" and other obvious and unhelpful messages. I have found several old, dead threads regarding timeouts from players being near, but none of them have any solutions. Does anyone know what could be going on here?