-
Notifications
You must be signed in to change notification settings - Fork 61
Forge 1.13.2 protocol handshake support #145
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
Conversation
|
[main.rs:218][INFO] Starting steven [lib.rs:390][TRACE] loop process - 1 events, 0.000s about to parse id=1, dir=Clientbound state=Status [main.rs:95][INFO] Detected server protocol version 404 The crashing packet: 0x1b is Disconnect in the Play state: https://wiki.vg/index.php?title=Protocol&oldid=14643#Disconnect_.28play.29 - not correctly transitioning from Login to Play state? And where is the " number? What is sent from the client before server kick? Only two packets on this connection, first is 0x00 handshake login: '\x00\x94\x03\x0elocalhost\x00FML\x00\x04l\x02' https://wiki.vg/index.php?title=Protocol&oldid=14643#Handshake then 0x00 login start with the player's username: https://wiki.vg/index.php?title=Protocol&oldid=14643#Login_Start. Forge 1.13.2 is very beta, MultiMC client doesn't even find it: |
|
Somehow I acquired forge 25.0.198 but the latest on http://files.minecraftforge.net/maven/net/minecraftforge/forge/index_1.13.2.html is 25.0.199, to retest, but the installer takes a while (much longer on 1.13.2 than 1.12.2 and earlier for some reason). This is a beta, discussion: https://www.reddit.com/r/feedthebeast/comments/aqswry/minecraft_forge_1132_beta_is_out/ |
|
java -jar forge-1.13.2-25.0.199-installer.jar select install server, select a clean directory, let it complete, run |
|
Modding is in a weird state for 1.13.2. Apparently there are alternative mod loaders a lot of mods use now. I knew of Fabric due to its 1.14 support (#72) but there is also Rift: https://github.com/DimensionalDevelopment/Rift https://www.curseforge.com/minecraft/mc-mods/rift for 1.13.x only. However both Rift and Fabric are more lightweight than Forge. Do they even have any protocol handshake and/or block ID registration negotiation? |
|
Update on Forge posted by their developers on January 1st, 2020 earlier this month: https://www.minecraftforge.net/forum/topic/79304-112114-and-lts-system/ - in summary, they used the time during 1.13 to pursue a large cleanup and rewrite of Forge, which was finished by 1.14. This introduces a new "long term support" release version, which is 1.14, but 1.15 is the latest and has full support.
https://files.minecraftforge.net/maven/net/minecraftforge/forge/index_1.13.2.html does have Forge 1.13.2 downloads, but it is not supported. How are mods adapting? As an example this mod (a lighting engine): https://www.curseforge.com/minecraft/mc-mods/phosphor:
Sounds like this branch should be instead updated to work with Forge 1.14.x, which would be worth supporting for sure as its the LTS release. (And 1.15.x because it is the current release). Open question, how much does 1.14's Forge handshake differ from the 1.13 incomplete version here? |
|
Although this is incomplete and untested, merging this support as it exists for now to avoid the branch going stale. |

Continuing on #144 (and #134 #88)
Vanilla 1.13.2 (404) protocol for reference: iceiix/steven#67
https://wiki.vg/Protocol https://wiki.vg/index.php?title=Protocol&oldid=14643