You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using forge 1.12.2 and before it was possible to get the modlist of clients connected to the server thanks to the Forge HandShake (see https://wiki.vg/Minecraft_Forge_Handshake#Forge_handshake). With 1.13 the CustomPayload changed and is now using a MinecraftKey instead of a string like "FML|HS", since when the client connects it registers the channel fml:handshake I tried to send an updated version of the 1.12 packet (to the last version of forge 1.15.2) by replacing "FML|HS" by a MinecraftKey created from "fml:handshake" however it didn't work (I didn't get any answer from the client).
Is there any documentation about it? Do you know what could have cause this issue?
Thank you,
Thomas
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity in a long time. If this issue is still relevant and should remain open, please reply with a short explanation (e.g. "I have checked the code and this issue is still relevant because ___." or "Here's a screenshot of this issue on the latest version"). Thank you for your contributions!
Hello,
Using forge 1.12.2 and before it was possible to get the modlist of clients connected to the server thanks to the Forge HandShake (see https://wiki.vg/Minecraft_Forge_Handshake#Forge_handshake). With 1.13 the CustomPayload changed and is now using a MinecraftKey instead of a string like "FML|HS", since when the client connects it registers the channel fml:handshake I tried to send an updated version of the 1.12 packet (to the last version of forge 1.15.2) by replacing "FML|HS" by a MinecraftKey created from "fml:handshake" however it didn't work (I didn't get any answer from the client).
Is there any documentation about it? Do you know what could have cause this issue?
Thank you,
Thomas
The text was updated successfully, but these errors were encountered: