Database:Core

Database - Database Core

Return to: Database | Tutorials | Portal | Forum | Project Manager | Bug Tracker

"Core" data is data that is required by any EQ2Emulator server in order to run properly. You do not need items, spawns, or spells to start the World binary, but Core data is absolutely required. Those tables are documented here, and should come with every EQ2Emulator Database Package.

Table	Description
appearances	Required. Everything in the game that is not a part of the zone VPK has an appearance. That is, your character has hair, eyes, clothing, and objects like tables have a surface, items would not show up, etc. Without this data, nothing would appear.
commands	Required. Normally handles /slash command input and UI button commands (which are just hidden slash commands anyway). For a basic server to operate, this data is required. However, commands can be customized for such things as "Steal the Letter" or "Burn Tent" for questing/gathering. Without commands, you could not even see /who was online!
opcodes	Required. Opcodes is the life-blood of the emulator. Data is sent to and from the client/server in "packets" and these opcodes map data in those packets to data structures (*.xml) stored within the server. Without this data, nothing will work.
reference_spell_effects	Important. These values are what generate "spell effects" in the client when someone casts a spell or uses an ability.
skills	Important. In EQ2, a characters ability to progress is goverened by Skills. Without skills, there is no progress. So if a player has a 1H Slashing weapon and there are no Skills loaded, that player will be unable to swing that weapon in combat. Skills should be Required, but the World will run without them.
visual_states	Required. A "visual state" is exactly that; what you see the entity doing. It may be chopping wood, smithing, glowing, or chuckling uncontrollably. Without this data, you could not set a "state" that a spawn is in, and it would just stand there.
zones	Required. The zones table has it's own section from the main Database page, but in summary, you cannot log into any part of the emulator without a zone record. Zones can be customized, however, so while at least 1 zone is Required, the rest are up to you. See Zones for more details.

appearances

Table breakdown

• appearance_id - is the id the client uses/needs.
  
• name - The name of the appearance static objects/boat_temp
  
• min_client_version - lowest client version possible to see the appearance

commands

Table breakdown

• type - Offer the ability to provide a /commands command, where players and admins could list emulator-only commands 0 = standard command, and 1 = Emulator command
  
• command - This is what you type into the client who
  
• subcommand - If the command requires additional command spawn add
  
• handler - used in the server code
  
• required_status - what status level a player must be before he/she can use the command 0 = anyone 100 = GM

Appearances appearance_id - is the id the client uses/needs name - The name of the appearance static objects/boat_temp min_client_version - lowest client version possible to see the appearance

Commands type - Offer the ability to provide a /commands command, where players and admins could list emulator-only commands 0 = standard command, and 1 = Emulator command command - This is what you type into the client (who) subcommand - If the command requires additional command spawn add handler - used in the server code required_status - what status level a player must be before he/she can use the command 0 = anyone 100 = GM

Opcodes version_range_1 - This is the minimum client version that will use this set of opcodes version_range_2 - This is the maximum client version that will use this set of opcodes name - The name of the opcode opcode - The opcode number table_data_version - Need to fill in

Reference Spell Effects category - type - name - misc -

Skills short_name - name - description - skill_type - display -

Visual States visual_state_id - name - min_client_version -

Zones expansion_id - name - file - description - safe_x - safe_y - safe_z - safe_heading - underworld - xp_modifier - min_recommended - Max_recommended - zone_type - always_loaded - city_zone - weather_allowed - min_status - min_level - max_level - start_zone - instance_type - default_reenter_time - default_reset_time - default_lockout_time - force_group_to_zone - lua_script - shutdown_timer - zone_motd - ruleset_id - login_checksum -

As you can see, the list of required data is very small compared to the rest of the database. This should give you a glimpse at just how customizable our server is.