Leaderboard

Are you dragging the client on the connection patcher because you cannot run connection patcher by it self and patch the client.

There is an update coming which is going to do a complete change on the structure of authserver dealing with authentication and the way the client communicates with the server and using a stronger socket for connection, which is also going to change the way latency is handled in a better way after the updates have been done.

For now only the config.wtf file but after the changes have been made to the correct files it will require the database to also change with an update to a sql file.

Well see the port makes the authserver connection stronger but the code I have done makes the socket stronger so when the client and server communicates it looks for a stronger socket connection using the IP and port together which changes the structure altogether. Much better authentication for authserver, which I plan to release to TrinityCore once I am done so it can be committed

I know one thing for sure to make a more secure connection when connecting you always want to use the IP address and the port number together or it has a chance of being picky and not always allowing connection so make sure it looks something like this when dealing with the config.wtf file 192.168.1.100:1119 your IP and port followed closely together. Also when it comes to updating the server especially the auth database it doesn't always update the hash all the time so that is why when you reload the database it works and when you retry it doesn't. I have been working with a solution on this issue for a while now which is close to being done.