Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hive doesn't follow the normal login sequence #214

Open
HashimTheArab opened this issue Nov 24, 2023 · 1 comment
Open

Hive doesn't follow the normal login sequence #214

HashimTheArab opened this issue Nov 24, 2023 · 1 comment

Comments

@HashimTheArab
Copy link
Contributor

The conn expects a ServerToClientHandshake, and a PlayStatus

conn.expect(packet.IDServerToClientHandshake, packet.IDPlayStatus)

Hive does not send the play status, but immediately sends StartGame, resulting in a closed connection

Cubecraft

Handling packet, *packet.ServerToClientHandshake
Handling packet, *packet.PlayStatus
Handling packet, *packet.ResourcePacksInfo
Handling packet, *packet.ResourcePackStack
Handling packet, *packet.StartGame

Hive

Handling packet, *packet.ServerToClientHandshake
conn.receive: Handling packet id 11 (packet.StartGame)
[log.fatal]: [Proxy]: could not join: dial minecraft 10.0.0.92:49308->148.113.162.177:19132: use of closed network connection

@ismaileke
Copy link

Yes, I noticed this too. Why doesn't The Hive follow the normal login sequence?

To solve this problem it is necessary to emulate the behavior of the Minecraft Client

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants