DBEditor:Admin

DBEditor: Admin

The Admin Editor option is not really editing at all, but more of a grouping of Content Management features, such as spawning a zone, or building dialogs. Not all menu options are available to all team members, as some of them are specific to the Project Admin's work, but the ones shown here should be for general use by the Content Design team.

A look into the individual menu items:

Admin

The Admin section are just general lookups and validation options.

Server Stats

This option gives a quick overview of the current Development and Live (EQ2TC) servers; both the players and content. For example:

You can see here the average players on the Test Center server, the quests they have done, highest levels, etc. You can also see who the last 10 players to login were, so you can get an idea if the server is still running

Log Files

This is a special menu meant only to review changes made by team members, or to observe the logging happening on your server at this time (using an AJAX "tail" call to the server's log file).

In this example, you would click on the link for Show DBEditor Logs and it would pull up a directory listing of all current Editor logs. These are every SQL change submitted by a team member via the DB Editor. Clicking on an individual team member's log by week, a simple text display of SQL statements are shown.

NOTE: This is why all work MUST be done via this DB Editor, because the changes made here provide the SQL statements necessary to update everyone elses servers via the Patch Server service!

Validate Scripts

This option will check the Database for LUA script assignments, then chase down the path of the physical file on the developer server hard disk in order to reconcile that every script on the drive is in use in the database, or that every database entry has a valid script file. An example of this is as follows:

Since our Database got wiped of content, you can see in this example we have all the scripts physically on the drive for these spawns, but the tie between the spawn itself, and the file, is broken... so the script file is considered "an orphan". You can fix this by going to the spawn, item, quest, spell or zone editors themselves and re-attaching the script to the proper owner.

More on this later.

Migrate

There are a few Migrate Data options, but the only one available to the Content Designers is Migrate Zone (at this time).

Migrate Zone

This is a huge system, and a very critical one, so I will be covering it on it's own page here - DBEditor:MigrateZone

Purge Zone

THIS IS A VERY DESTRUCTIVE COMMAND!!!

As the name sounds, this command will erase every spawn in a zone, no matter what type. Use this ONLY if you are certain you want to start completely from scratch populating a zone.

Be sure to check with your other team members before purging a zone!

Selecting Purge Zone will bring you to a zone picker. The zones listed are only zones that contain spawns, keeping it simple. Note that the command "Purge All Zones" currently does not do so, because that was deemed far too dangerous to use. It is only an option for the Project Admin while testing this editor and migration scripts.

Once you select to Purge a zone, you are shown a list of spawns that will be deleted, and given one last option to abort. If you click "Purge Zone", they are gone forever.

The Spawn ID's that get purged in this manner DO get reset to unprocessed in the RAW database, 
so they can be re-populated again using Migrate Zone.