PrismarineJS / PrismarineJS/node-minecraft-protocol

Client not following the correct sequence

Open
#949 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.4k
Forks
290
Avg merge
4d 8h
Merged PRs (30d)
7

Description

[ x] The FAQ doesn't contain a resolution to my issue

Versions

  • minecraft-protocol: ^1.29.1
  • server: vanilla 1.18.1
  • node: v16.8.0

Detailed description of a problem

https://wiki.vg/Protocol_FAQ#What.27s_the_normal_login_sequence_for_a_client.3F

I am trying to debug an issue where when i connect to a proxied server i always initially spawn inside the floor, just to be "teleported" to the correct position microseconds afterwards.

In the flow of packets the client sends the settings -> custom_payload -> held_item_slot -> position_look commands.
While the custom_payload and the settings are expected (although in different order) the other two are kind of unexpected and the position_look command seems to show the issue with the spawning inside the floor:

{ size: 34, name: 'position_look', state: 'play' } { x: 8.5, y: 65, z: 8.5, yaw: -180, pitch: 0, onGround: false }

It is always the same position it seems, at least around that area. The world spawn is nowhere near that position.
I dont really understand why the client is apparently sending its position to the server without even having chunk data at hand.

Although this kind of seems like a client issue, maybe this is triggered by some issue with the packets in the sequence before? Or some missconfiguration on my end?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Protocol FAQ and the reported packet sequence, then compare the proxied connection logs with the expected Minecraft login flow. No source file or test is named; done would require identifying whether the sequence comes from node-minecraft-protocol or the proxy/client and defining a reproducible correction.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.