thetxt/oxide
2
8
Fork 5
Code Issues 25 Pull requests Projects Releases 13 Packages 1 Wiki Activity Actions

Disconnecting Players with wrong Minecraft Version #110

New issue
Open
opened 2026-07-14 17:33:24 +02:00 by JRBlockkop · 2 comments
JRBlockkop commented 2026-07-14 17:33:24 +02:00
Contributor
Copy link
No description provided.
thetxt commented 2026-07-15 13:31:34 +02:00
Owner
Copy link

What exactly is the issue? During the handshaking Im sending the right protocol version for the server which prevents the vanilla client from joining. I think this is more of an issue with a client that fails to check the protocol version before connecting. Or am I misunderstanding?

What exactly is the issue? During the handshaking Im sending the right protocol version for the server which prevents the vanilla client from joining. I think this is more of an issue with a client that fails to check the protocol version before connecting. Or am I misunderstanding?
JRBlockkop commented 2026-07-15 16:53:17 +02:00
Author
Contributor
Copy link

Good Point that the Client should check but it doesnt. So the Client relies on the Server to tell if it can join and if you try joining with an other Version you get an crash by the Client. The Vanilla Server just returns grafik So i want to fix it. So my client doesnt crash

Good Point that the Client should check but it doesnt. So the Client relies on the Server to tell if it can join and if you try joining with an other Version you get an crash by the Client. The Vanilla Server just returns ![grafik](/attachments/a73a5101-4a68-4138-a8f8-232c7671ad17) So i want to fix it. So my client doesnt crash
grafik.png
139 KiB
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
#98_improve_collision_detection_of_entities
main
0.8.1
0.8.0
0.7.0
0.6.0
0.5.1
0.5.0
0.4.0
0.3.1
0.3.0
0.2.0
0.1.2
0.1.1
0.1.0
Labels
Clear labels   
complexity
high

  
complexity
low

  
complexity
medium

  
importance
high

  
importance
low

  
importance
medium

  
type
bug
something that should work, but doesn't

  
type
chore
something that should be done at some point, but doesn't really change functionality

  
type
feature suggestion
a feature that should probably be implemented

  
type
missing feature
feature that should really be working by now, but doesn't

No labels
complexity
high
complexity
low
complexity
medium
importance
high
importance
low
importance
medium
type
bug
type
chore
type
feature suggestion
type
missing feature
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
thetxt/oxide#110
No description provided.