Be sure to read this entire post before asking questions as the answer is probably contained within. The consolidated update server is operational, however to ensure that everyone's worlds are correctly updated I had to make some minor changes to the plan.

1. First, you will need World version 0.6.5 to connect to the update server. You can download it here: https://sourceforge.net/project/showfil ... _id=663186

2. Your tables will be cleared, so before you connect to the update server be sure to make a backup if you wish to save anything.

3. The update server port has changed to 9103 to prevent anyone from accidentally updating their tables.

4. OPTIONAL For those of you who don't wish to lose any data you can execute the following queries and it should prevent the server from attempting to apply the updates. Only do this if you are 100% sure your server was up-to-date as of this morning before the update server was brought down.
update table_versions set version=65000;
update table_versions set download_version=65000 where download_version>0;

For those who need a visual example (grin), this is what you set your LoginServer.ini to look like:

[LoginServer]
loginserver=eq2emulator.net
loginport=9100
worldname={your world name}
worldaddress={your PUBLIC dyndns url}
internalworldaddress={your local LAN IP}
worldport={your port (9200 typically)}
locked=false
account={your server account}
password={your server password}
autotableupdates=always
autotableverbose=false
autotabledata=true

[WorldServer]
Defaultstatus=
Unavailzone=

[UpdateServer]
updateserveraddress=updates.eq2emulator.net
updateserverport=9103

[LoginConfig]
ServerMode=StandAlone
ServerPort=9100

Data in BLUE you change to match your own set up. Everything else can stay default.

Not sure if its just me, but after downloading 0.6.5 I am still getting Invalid world Version on 9103.

Check your core tables (like opcodes) to be sure there is data in there. I just told LE about a possible problem, but it was with fresh databases, not updated ones.

I tried it with both my existing tables and now with a wiped database and I have the same problems. here is a lovely little screenshot over everything bad that is going on ;op

Did you grab latest SVN and compile? It should say server version is 0.6.5

Definitely not the right EXE. It should say 0.6.5 Developer Alpha. You got that from the link LE posted?

Yup. I did indeed. That is the Win32 Binary version.

Just downloaded that package, and it is indeed saying 0.6.0 - so maybe I do not understand what's up. Wait for LE to swing back by.

Get the exe from private SVN and it works.

John Adams wrote:Just downloaded that package, and it is indeed saying 0.6.0 - so maybe I do not understand what's up. Wait for LE to swing back by.

Get the exe from private SVN and it works.

Yay! Not stupid and/or insane! Its a red letter day for me!

"Opcode "blahblahblah" is missing from opcode configuration." x1000

That the issue you found with a new database, huh John?

Heh, somehow I got the wrong exe uploaded in that zip file. Updating it now.

Silly Lethal.

You can blame me for keeping you up til 3am fixing the stats on my hot pink pantaloons.

There was a problem with the release. I have uploaded the changes to SF, but it might take a bit for them to add it to their download list. Anyone that downloaded the release this morning will need to grab this new release and run this database query:

update table_versions set download_version=0;

If you dont, you will have missing data.

LethalEncounter wrote:Anyone that downloaded the release this morning will need to grab this new release and run this database query:

update table_versions set download_version=0;

If you dont, you will have missing data.

Except cool people like me, right? who have tons of data we do not want biffed?