When version 0.5 is released (probably in a couple of weeks) the following changes regarding the login server will occur:
1. After each new release previous versions of the emu will be not be able to connect to the login server. This is done to ensure that every server that a player can choose is running at least the latest released version for the greatest compatibility with everyone's clients. NOTE: This is referring to server versions, not client versions. Older client versions will still be supported in each new emu release.
2. Servers running in debug mode (developers) will appear yellow in the server list creation when a user creates a character. This is done so that users know that the server is testing the latest code and will be more unstable than the green (non developer) servers. Yellow servers will be up and down more often than their green counterparts but will have the newest features.
3. Server versions will be taken out of the server names displayed on the character select screen. This will allow an addition 5 bytes to be displayed.
4. Updates will be processed first when a World server is starting up. This will ensure that all the latest opcodes and data is being used without having to restart the program.
5. World updates will be handled by a separate program instead of being processed by the Login server. Two separate versions of this update server will exist - one for updating new world servers to the latest stable database version and another for updating development servers to the latest development database. Think of it like EQ2 Live, you have the Live version and then you have the Test server. Same concept.
6. In order to prevent some users from abusing the update feature, each server will only be allowed to download the entire update list (ie populating a new database with all the information) twice per 7 day period. This will allow someone to recreate their entire database one more time per 7 days (the first being when it was created) if they made a mistake and deleted their database.
Login Server changes
- alfa
- Team Member
- Posts: 550
- Joined: Fri Jul 27, 2007 6:24 pm
- Location: France
- Contact:
-
CrabClaw
- Retired
- Posts: 88
- Joined: Wed Aug 01, 2007 10:49 am
- Location: Seattle
Could the current official SQL core be put in the SVN in a \sql directory so people could rebuild their schemas from scratch locally?
Kinda' like an official 'EQ2DB_build_50_Base.sql' locked at a build version? Then people wouldn't have to spam the login server to rebuild the core and only the test server builds would need to do the automatic update to get the hottest and latest updated data.
Kinda' like an official 'EQ2DB_build_50_Base.sql' locked at a build version? Then people wouldn't have to spam the login server to rebuild the core and only the test server builds would need to do the automatic update to get the hottest and latest updated data.
- John Adams
- Retired
- Posts: 9684
- Joined: Thu Jul 26, 2007 6:27 am
- EQ2Emu Server: EQ2Emulator Test Center
- Characters: John
- Location: Arizona
- Contact:
I imagine the DB structure will soon be changing dramatically, and continue to do so as the emulator develops and stabilizes. I wouldn't want to "officialize" any DB schema currently. As mentioned elsewhere, using mysqldump.exe is a simple way to make a local backup of the raw schema before messing with it and ~oops~ deleting it.
I like the changes, LE. Good work you guys, as usual.
I like the changes, LE. Good work you guys, as usual.
John Adams
EQ2Emulator - Project Ghost
"Everything should work now, except the stuff that doesn't" ~Xinux
EQ2Emulator - Project Ghost
"Everything should work now, except the stuff that doesn't" ~Xinux
Who is online
Users browsing this forum: No registered users and 0 guests