World.exe has stoppe working on connection

[Asdaddy1]

So yesterday I found this [REDACTED] and went CRAZY. I was like finally instead of spending 13 years and 4 months into making a client look like the old EQ but now I freaking got the old EQ. So i set everything up and my mind was like "Dude this will be killer!" so i continued, downloaded the client, had the login server ported towards external IP, went to connect to it, BAM it didn't work. So i spent all ay working on it and now I'm depressed. The world.exe will stop working when i try to connect to it with a external world address. Here are my files AKA yes i know it is minilogin but idk if the EQEMULoginServer will work with it because it is EQ Trilogy.

LoginServer

### --- This file tells world.exe what loginserver to connect to.
### --- Leave the account and password field BLANK.

### --- Public Login is un-supported as is LAN playing. We reccomend using the EQEmu.net Loginserver ALWAYS.

### --- NOTE: Starting 6-1-2002, you can no longer use the word "Server" in worldname.
### --- NOTE2: the word "Server" is added to each server automaticly.

# READ README.TXT

[LoginServer]
loginserver=127.0.0.1
worldname=Everquest Classic
account=
password=
locked=false
worldaddress=127.0.0.1 ------- If this were the external IP and i tried to connect it would crash
loginport=5999

[LoginConfig]
ServerMode=Standalone
ServerPort=5999

and here is link to the github https://github.com/erfg12/EQTrilogy-Old

I spent 3 hours looking into the source code and from I can tell ATM it should be working. The login server will tells me that is someone at the server list but when i try to connect to server the client says Failed, it coul be a patch problem *It didn't say it like that* Any ideas? The zones were changed to external IP too

[N0ctrnl]

As was said on the Discord chat - this code isn't supported here. Also, you're going to miss out on a lot of good things using code that old. At the most basic level, the last commit to that github repo was a year ago. Even if it was completely up to date at the time (doubtful), you're still over a year old on code.

I hate to rain on your parade, but this isn't the best way to go about building a server. Any issues you have you're going to have to tackle on your own. That's not a good thing, trust me.

[Asdaddy1]

Oh sorry didn't see that