Closed DefinitlyEvil closed 7 years ago
First are you using JRakNet v2.8.1 or v2.8.2? There was a bug from v2.8.0-v2.8.1 that completely broke the MinecraftIdentifier. Second of all, JRakNet is unable to work with Windows 10 due a bug on Windows 10 that causes conflicts with other servers on the same machine. Try using a different device on the same LAN network. After that, please let me know whether or not it is still not showing up in the server list :)
hey good afternoon! v2.8.2 latest, even tried bleeding-edge snapshot. and PMMP is working normally when using MC:Win10 to join.
But PMMP could work well on same machine... why?? PS: Just tested, still unable to connect using port 19100.
Could you try connecting using a different device, and could I see your server code?
It's open source in DragonetMC organization.
Yes but I need the parts of the code where you are actually using the server. I can't scour through the entire source of the project.
I'm honestly not sure what's wrong, the code works for me on my machine (The code you sent me, minus the code that would not run without the rest of DragonProxy)
Once again, I will ask, have you tried using a separate device on the same LAN network?
@MarfGamer yep I tried, didn't work. :( unable to discover, also unable to connect directly.
PS: WAIT IT WORKS!! both on my PC and my iPhone. idk what happened. xD sry mate
wait, I must use my phone to send some packets(like discovery packets) to let my local PC to discover the server??
No no no no, it would make no difference on the local PC, I wanted to see if the server still worked on a different device. If it didn't, then it was JRakNet. If it it only failed to function on the local PC, then it was not JRakNet but instead Minecraft.
initially, local PC can't discover the server, but after my iPhone sent some discovery packets, both platform could discover the server. xD
That is extremely strange, I will look into that. But just to make sure, everything works on separate devices, correct?
@MarfGamer that's true, yep. ;) I think you shouldn't bind to broadcast address, you should only receive discovery packets from there but you listen on 0.0.0.0
.
I am using Minecraft: Win10 (1.2.2, identifier protocol set to 137)
It didn't even call my listener!?