
Originally Posted by
fullhawk
I've noticed something odd, and although this tool has worked for me in the past, I'm unclear on how.
To explain, the network.properties file in gameserver and loginserver has values for the host/port of the gameserver. In the config files from the repack, the network.port value for loginserver/bin/configs/network.properties is 8888, and the one from gameserver/bin/configs/network.properties is 8889.
This config tool writes both of these to the same host/port value. This means that when gameserver starts up and tries to bind to that port, it can't because it's already in use. The loginserver already bound that address/port, so the gameserver displays the java stack trace after it finishing loading ai scripts.
If I change the gameserver's network.properties to be 8889 (same value it has from a fresh download), I can start it up without error. The weird thing is, I'm 99% sure I have had it work for me before after running the config tool. I feel like the host/port conflict wasn't always happening.