search

someaddons / connectivity

Minecraft mod connectivity which fixes connection issues
9 stars 0 forks source link

[BUG] Potential Incompatibility - Timeout when joining a second time #11

Closed SirOMGitsYOU closed 2 years ago

SirOMGitsYOU commented 2 years ago

Mod file version connectivity-2.4-1.16.5

Describe the bug A clear and concise description of what When using a large modpack with connectivity in it if you were to try host a forgebukkit/spigot server using one of the various options out there

(Magma, Mohist, Loliserver, Arclight)

To Reproduce Steps to reproduce the behavior:

  1. Use a large modpack (in my test i used https://www.curseforge.com/minecraft/modpacks/a-bit-of-everything-official/files/3574154)
  2. Use LoliServer (https://github.com/Loli-Server/LoliServer1.16 - currently only stable one for 1.16)
  3. boot up the server (remove any clientside mods)
  4. join server, you will successfully join the first time,
  5. disconnect
  6. re-join the server and you will infinitely timeout from here on out.

Expected behavior Not to timeout and the connection timeout to increase (have also increased the timeout to match in all configs relating to the timeout including disabling other mods that change the time out such as randompatches and performant with still replicating issue, only occurs on forgebukkit servers as on normal forge no issues at all)

someaddons commented 2 years ago

I'm making my mods for forge, so only supporting forge not other forge forks with who knows what changes to the base game.

ckhawks commented 2 years ago

I'm having this same problem with a large modpack on Forge 36.2.26. It doesn't seem like it's necessarily linked to joining the server for the second time, as I'm having the same issue trying to connect to the server for the first time since opening the client.

Client log: latest.log Server log: latest.log

edit: nvm I removed the mod on client and server and it's still happening so unrelated to Connectivity. Time to go rip my hair out debugging this

SirOMGitsYOU commented 2 years ago

I'm having this same problem with a large modpack on Forge 36.2.26. It doesn't seem like it's necessarily linked to joining the server for the second time, as I'm having the same issue trying to connect to the server for the first time since opening the client.

Client log: latest.log Server log: latest.log

edit: nvm I removed the mod on client and server and it's still happening so unrelated to Connectivity. Time to go rip my hair out debugging this

Do you have Not Enough Creativity Installed? This issue for us we realised was not related to Forge or Connectivity but is actually a mod called Not Enough Creativity causing a weird packet issue

ckhawks commented 2 years ago

Unfortunately I don't :( I'm sure I have a similar issue with one mod somewhere causing the problem, but I am stuck on how to diagnose it

On Wed, Feb 9, 2022 at 1:15 PM Peter @.***> wrote:

I'm having this same problem with a large modpack on Forge 36.2.26. It doesn't seem like it's necessarily linked to joining the server for the second time, as I'm having the same issue trying to connect to the server for the first time since opening the client.

Client log: latest.log https://github.com/someaddons/connectivity/files/8028489/latest.log Server log: latest.log https://github.com/someaddons/connectivity/files/8028510/latest.log

edit: nvm I removed the mod on client and server and it's still happening so unrelated to Connectivity. Time to go rip my hair out debugging this

Do you have Not Enough Creativity Installed? This issue for us we realised was not related to Forge or Connectivity but is actually a mod called Not Enough Creativity causing a weird packet issue

— Reply to this email directly, view it on GitHub https://github.com/someaddons/connectivity/issues/11#issuecomment-1034106295, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABFV6UFXPQHC4X3KIUMDKYDU2K4NVANCNFSM5KP23PQQ . You are receiving this because you commented.Message ID: @.***>