Open matthewfcarlson opened 4 years ago
Hi, I'm facing the same issue. How could I contribute to fix this? And why did the update was postponed to 1.16 version? Couldn't implement that as a new feature in 1.15.2 ?
I am not.sure if this is fixable at all (skipping all mod handshakes may cause issues), if you want to write this Forge spoofing bypass you are welcome to create a Pull Request :) It's under the 1.16 milestone, because this is the next time I will touch the code. If someone else will create a PR for it, it could be earlier.
Good. Do you know how does the mod handshake works? If I knew I could work on it and create a pull request.
They are described at the wiki.vg article (I think) above. Atm I dont have much time to really check this. I will work on it after the 1.16 release or someone else (Maybe you) have to figure it out and create a PR
Tried it out today.
After adding the "\0FML\0" to the Handshake packet I'll get a 0x1b packet (which normally is not valid in the login procedure) which disconnects the client with {"translate":"disconnect.genericReason","with":["Internal Exception: java.lang.NumberFormatException: For input string: \"\""]}
. I am not quite sure why this happens or what I am doing wrong, but I won't receive any forge handshakes :( trying it out later on
When trying to sign into a forge server, this error presents itself.
https://wiki.vg/Minecraft_Forge_Handshake#Pre-1.13
https://github.com/PrismarineJS/node-minecraft-protocol-forge this is an offering for node-protocol (which doesn't support 1.15 grumble grumble).
I might take a look into implementing this, but we'll see