The reason is because the server doesn't know how to handle that packet, the simple solution for this is just sending back the packet with blocks of the version of the client, launcher, etc.. You can find those details in the version file. The numbers you send back have to match the ones in the version file or else it will trigger an update. The update will be downloaded from the website URL that is provided in the last block.
I've quoted the solution from another forum where I posted this solution.
Quote:
|
Originally Posted by CodeDragon
As I said in a other thread: You'll have to implement to launcher packets into the login server in order to get it working.
Some server files have it. It's a basic packet.
You'll have to add a new handler to the handler list. With the packet id: 4112
The handler just needs to send the game versions back. Here is a example of the packet:
Code:
namespace Authorization.Packets { class Launcher : Core.Networking.OutPacket {
public Launcher()
: base(4112) {
Append(0); // Format
Append(0); // Launcher Version
Append(0); // Updater Version
Append(0); // Client Version
Append(0); // Sub Version
Append(0); // Option
Append("http://"); // URL
}
}
}
Good luck implementing it. |
As I said, good luck implementing it. None needs to ask money for this easy solution.
