Networking Issues: Loginserver, eqemu_config, eqhost, USC, login.ini

[Uleat]

The changes that occurred for that fix to go in probably had not been implemented in the stable branch yet..otherwise, it would probably
have been pushed in to fix it.

There are a myriad of ways to update your database:
- create a backup and work from that - only pulling in changes from your working db to your live one as you're ready.
- work from sql files so that you can just reapply the changes whenever needed.

There's a lot of ways to do this and I'm sure there are some really good alternatives out there

[AdrianD]

Alright, I will wait for this fix to hopefully go into stable. This issue been on my checklist for a while. I can live without it. Learning about it was more important.

I haven't made many table schema changes to my DB. I run a query to revert the changes before it's usable or live. Like you said, I have a main DB where I work out of.

Since classic and progression is what I'm trying to accomplish, at least intially, I have large queries to make/separate the data and plug it into the live version for each expansion. They follow a specific order to maximize accuracy.

It would be nice to have a resource to pull expansion information from. As it stands, I have to separate quite a bit "by hand" after my queries have run. I only have to make distinctions once, but 93k items, 65k npcs and 30k spells is a lot even if half of them are distinguished.

Anyways, I'll put this on the backburner for a while and move on to my other issues.

Thanks a bunch for your help and equally, your quick responses. It feels resolved even though it isn't.