I will be unable to implement the consolidated update server until next weekend because if I implemented it now it will cause problems with your current tables. The only reliable way to implement this would be to allow the update server to completely recreate the tables so that World can ensure that you have the latest version that your World can support.

So on Sunday Feb 22nd at around 8AM CST I will implement the new update server so those of you with custom data will need to create a data backup. After the backup is complete you have two options:

1. Trick World into believing that is already has the new latest tables by setting the version field for all tables in table_versions to 650.1 for development code, 600 for "stable" released code After you update the tables with either 600 or 650.1 you should be able to connect to the update server correctly. Do this only if you are completely sure that you have the latest updates that your server can use from the current update server.

2. Allow world to recreate all your tables and restore the data from your backup.

Option 1 is recommended, but I also recommend making a backup before attempting either of these to ensure if you make a mistake or I made a mistake on the update server, you have a backup available to fix it.

One step closer woo!!

Just a reminder, this is still planned for Sunday morning!

I have Tess in no-restart mode (will not restart after crash, cuz there aren't any anymore! woot) and set my LoginServer.ini to NEVER update table or data... til this is passed.

I would probably jump off a bridge if I lost Tess data. but, I also backup nightly. so no biggie.

John Adams wrote:cuz there aren't any anymore! woot

Correction, Scatman must be back, cuz Tess crashed again.

~runs~

Haha, i've been thinking about it a lot while I'm stuck on my project. Surely that could've caused it.

LE,

I cannot set Tess's 'version' column to 650.1, because it is an unsigned int field. Is this going to be a problem come tomorrow?

Good point, I'll push that update shortly.

While you're at it, can you drop spawn.ground_spawn? I didn't want to make any updates this weekend if it would mess up what you're doing.

FYI, I never did get a change to the table_versions.version field from int(10) to float or whatever to support the point.

This going to be ok?

I actually changed it back to int because floats were giving me precision errors. Instead, the version is going to have a major version and a minor version associated with it. The major version is the release without the decimals*10: ie 65000 instead of 0.6.5. The minor version is what is bumped whenever you have a database change. The data in your table_versions is major version *100 + minor version.