Bug: Adding to Bisect Hosting server creates a netty error of 23 with a VarInt of max 5

[TitanForgeIndustries]

What Feature Types Apply to This Bug?

System

Other Type

No response

What Type of Bug Is This?

Unexpected Behavior

Mod Loader

Forge

Mod Loader Version

47.4.10

The Aether Version

1.5.2

Is This Bug a Conflict With Another Mod?

No response

Client Log

No response

Crash Report (if applicable)

No response

Steps to Reproduce

Unknown reasoning, when added to a modded server it causes a Netty Exception, which allows ONE player to join then everyone else is cut off from joining.

What You Expect To Happen

Server to load properly, allowing all players to join

What Actually Happened

When player is allowed to join, every other player with the same modpack get the following error:

Internal Exception: io.netty.handler.codec.DecoderException: java.lang.IndexOutOfBoundsException: Index 23 out of bounds for length 5

also encountered: a VarInt too large error, and a packet size error before adding Packet Fixer

Additional Details

As stated, when added to our curseforge modpack, each player has the same following mods, configs, etc. When opening Minecraft and attempting to join the server, it only allows 1 out of 8 players at a time, when the player leaves it allows someone else to join, and so on.

Yes, Max players is set to 20
Packet Fixer IS installed which stopped a prior error, then made way for this error to show.

We did a binary check of the mods in the pack and narrowed it down to this being the issue, with an unknown reason we could not find anywhere else.

Please Read and Confirm The Following

• I have confirmed this bug can be replicated without the use of Optifine.
• I have confirmed this bug is on the most recently supported version of Minecraft.
• I have confirmed the details provided in this report are concise as possible and does not contain vague information (ie. Versions are properly recorded, answers to questions are clear).
• I have confirmed this bug is unique and has not been reported already.
• If playing on a modpack, I have reported this bug to their issue tracker already.
• I have confirmed that I'm reporting a bug in The Aether I, not The Aether II.