So I assume then that the big EQEmu servers must roll with an older version of Debian.

You said before that new distro releases often times break EQEmu and have problems. Is the changelog what will eventually announce support for updated distros? (I assume eventually Ubuntu 19.04 and Debian 10 will be supported?)

Guess the moral of the story is not to jump on board with the lastest Linux distro releases. Lol

I think the issue is not necessarily with Perl but with GCC and how are opcodes are being compiled and ultimately coming down differently down the wire causing garbled issues

I've not investigated the issue myself yet as I've been working on other things but yes, the consensus is to not typically race to the latest and that goes for many things beyond EQEmu because it may not necessarily be stable

I'm still working through some last touches with loginserver work doing a bunch of testing, found a few things I needed to take care of yet. Everything should be published and ready to go by tonight

I started thinking Perl wasn't the problem too, just simply because Ubuntu 18.04 LTS and 19.04 both seemed to run the same version of Perl and performed differently with quests/hails.

As long as part of your testing is connecting from an outside connection and you're able to zone without getting kicked, I'm sure you'll iron everything out. lol. :D

Just FYI I ended up having to spend some extra time taking care of a handful of other things LS related before preparing for release, needless to say there's been a ton of work that's gone into this

https://github.com/EQEmu/Server/compare/lsid

I'll update when things are pushed out

I really do sincerely appreciate all of the time and effort you've spent (and continue to spend) in order to keep EQEmu evolving. I can hardly wait to play with my friend and for him to keep a constant connection. :D

I'm an idiot and I think I just realized what I'm supposed to do with the link you provided. lol...

When updating my files manually, the following files didn't exist at all from the Linux installer, so I manually created them.

/loginserver/
account_management.cpp
loginserver_webserver.cpp
loginserver_command_handler.cpp


/loginserver/login_util
login_schema.sql

/common/
database.cpp

And, probably an error on my part, I attempted to compile everything with the latest version of all the files and it didn't work. lol...

(Edited it to how the red where the terminal put it, for easier reading.)

The link was just showing the sheer magnitude of work and changes gone into it, I never implied pull it down and start monkeying with it

As far as your authentication issues are concerned, I would make sure that your worldserver "address" variable is set to your public address, this can cause weird issues with zoning and handoffs much less able to handoff from Loginserver to worldserver at all

Whoops. I thought I was supposed to test it out. Well, that explains that.

Yeah, at first outside connections weren't able to connect all. A while back, someone here helped me switch it to have both an "address" and a "localaddress" and that allowed both LAN and outside connections to connect. Everything works great until it comes time to zone.

I want to run these changes through a production environment and closely monitor for a while, so I will not be rushing to push this mainline.

If you want to actually try out this loginserver on your server in the interm, I'd be happy to help you get it setup on Discord.

I'm getting ready to go camping in Canada today but I should be able to help in an hour or so if it is a route you'd like to go

I would really like that. :)

Sorry for an off-topic note. Wildfires going on in Ontario, depending on where you're going.

Winnipeg :)

-------------

Should of done that next month, I could of stopped by for coffee, lol. (I'm only 6 hours from there), but too busy this month with things.