Database:CoreServerData - Revision history

Cynnar at 20:11, 23 July 2015

2015-07-23T20:11:00Z

Cynnar at 19:56, 23 July 2015

2015-07-23T19:56:42Z

John adams: /* visual_states */

2012-02-09T00:42:05Z

‎visual_states

John adams at 23:59, 8 February 2012

2012-02-08T23:59:53Z

John adams: /* opcodes */

2012-02-08T23:03:20Z

‎opcodes

John adams at 18:51, 8 February 2012

2012-02-08T18:51:44Z

John adams at 16:16, 8 February 2012

2012-02-08T16:16:32Z

John adams: /* Placeholder Data */

2011-08-26T20:20:50Z

‎Placeholder Data

John adams at 19:57, 26 August 2011

2011-08-26T19:57:43Z

John adams: Created page with "== Placeholder Data == Server General variables commands languages name_filter opcodes table_versions transporters rules conditionals"

2011-08-26T19:51:50Z

Created page with "== Placeholder Data == Server General *variables *commands *languages* *name_filter *opcodes *table_versions *transporters *rules *conditionals"

New page

== Placeholder Data ==
Server General
*variables
*commands
*languages*
*name_filter
*opcodes
*table_versions
*transporters
*rules
*conditionals

@@ Line 6: / Line 6: @@
-== appearances ==
+{{Header|Appearances|BackgroundColor=3d78b4|FontColor=ffffff}}
 Appearances are the "pointers" to the graphical representations of every spawn, item, or object in the game. Appearances consist of an '''appearance_id''' and an internal path within the client's assetlib.vpl file where that appearances graphical information can be found.
@@ Line 23: / Line 23: @@
-== commands ==
+{{Header|Commands|BackgroundColor=3d78b4|FontColor=ffffff}}
 Commands are any slash (/) commands that might be entered by the player or the User Interface (UI) itself. For example, '''/who''' is a slash command, and must be in the Commands table in order for it to be executed and/or return results.
@@ Line 63: / Line 63: @@
-== opcodes ==
+{{Header|Opcodes|BackgroundColor=3d78b4|FontColor=ffffff}}
 For this article, we'll just discuss the Core Server Data related to Opcodes. For a detailed overview of Opcodes and what they are used for, see this article on [[Developer:Opcodes|Understanding Opcodes]].
@@ Line 81: / Line 81: @@
-== skills ==
+{{Header|Skills|BackgroundColor=3d78b4|FontColor=ffffff}}
 The Skills table is a list of all known player skills used in the game. It is used mostly for display purposes in placing the proper data in the client UI where appropriate (skill up messages, Persona data, etc)
@@ Line 100: / Line 100: @@
-== table_versions ==
+{{Header|Table Versions|BackgroundColor=3d78b4|FontColor=ffffff}}
 This is specific to the EQ2Emulator PatchServer service, and only pertains to Servers that connect to EQ2Emulator.net's [[PublicServices:LoginServer|Public LoginServer Service]]. The data in the `'''table_versions'''` table tracks the current schema (data structure) and it's table data for your Server, and allows your Server to ask for table or data updates provided by the EQ2Emulator Project.
@@ Line 119: / Line 119: @@
-== variables ==
+{{Header|Variables|BackgroundColor=3d78b4|FontColor=ffffff}}
 The `'''variables'''` table holds various data elements unique to your EQ2Emulator Server, like your server MOTD, current in-game date/time, and current lotto #'s and jackpot.
@@ Line 130: / Line 130: @@
-== visual_states ==
+{{Header|Visual States|BackgroundColor=3d78b4|FontColor=ffffff}}
 Visual States are similar to Appearances in the fact that they cause specific effects to occur within the world, such as fog, Mender's banging forges, players emotes, or other visual effects.
@@ Line 146: / Line 146: @@
 To try out Visual States, you can either use the in-game command /animtest {visual_state_id}, or to see it in action on an NPC, target an NPC and type /spawn set visual_state {id} <-- any ID from the list. Note that not all visual_state_id's produce effects, so try a few. Can be fun ;)
-== zones ==
 The `zones` table is the gateway to all things in EQ2Emulator! Without Zones, we have nothing. Every zone that an EQ2 Client supports must be in the zones table. Some data is mandatory, while others are recommended/fun stuff. Still other values are merely for reference, or systems not yet developed.

← Older revision		Revision as of 19:56, 23 July 2015
Line 1:		Line 1:
		+	{{PageHeaderChild\|Content\|Core Server Data}}
		+
		+
	'''EQ2Emulator: Core Server Data'''		'''EQ2Emulator: Core Server Data'''
	The tables listed here are ones that the server cannot function without. These are considered '''Core Data''', and are maintained by the EQ2Emulator Database Project team. You can always get the latest Core Data by connecting your world to our public LoginServer and pulling down updates for the data shown below.		The tables listed here are ones that the server cannot function without. These are considered '''Core Data''', and are maintained by the EQ2Emulator Database Project team. You can always get the latest Core Data by connecting your world to our public LoginServer and pulling down updates for the data shown below.

← Older revision		Revision as of 00:42, 9 February 2012
Line 141:		Line 141:


−	To try out Visual States, target an NPC and type /spawn set visual_state {id} <-- any ID from the list. Note that not all visual_state_id's produce effects, so try a few. Can be fun ;)	+	To try out Visual States, you can either use the in-game command /animtest {visual_state_id}, or to see it in action on an NPC, target an NPC and type /spawn set visual_state {id} <-- any ID from the list. Note that not all visual_state_id's produce effects, so try a few. Can be fun ;)
−

	== zones ==		== zones ==

@@ Line 8: / Line 8: @@
 Appearances come in many categories, such as Static Objects, Armor, Creatures, etc. Below are some examples:
-   id  appearance (path)
+   '''id  appearance (path)'''
   staticobjects/chandalier_iron  -- The graphic for an iron chandalier
   ec/pc/ratonga/ratonga_male     -- The graphic representation of a ratonga male
@@ Line 24: / Line 24: @@
-Commands are made up of a number of components:
+Commands are made up of a number of elements:
-  type           : either 0 or 1  (needs further definition)
+  '''type'''           : either 0 or 1  (needs further definition)
-  command        : the command itself (eg., spawn)
+  '''command'''        : the command itself (eg., spawn)
-  subcommand     : the sub-command (eg., create)
+  '''subcommand'''     : the sub-command (eg., create)
-  handler        : the internal command handler definition to execute the command in World
+  '''handler'''        : the internal command handler definition to execute the command in World
-  required_status: the minimum admin_status required to execute the command (or sub-commands)
+  '''required_status''': the minimum admin_status required to execute the command (or sub-commands)
 Example:
-  type  command  subcommand  handler  required_status
+  '''type  command  subcommand  handler  required_status'''
     spawn                   1            0
     spawn    create        44          100
@@ Line 76: / Line 76: @@
   [[Developer:DataStructures|Understanding Data Structure]]
   [[Developer:DataPackets|Understanding Data Packets]]
 == table_versions ==
-== skills ==
 == variables ==
 == visual_states ==
 == zones ==
 == Back to Content:Introduction ==
 [[Content:Introduction]]

@@ Line 61: / Line 61: @@
 == opcodes ==
-The simplest example of this might be when a player attacks an NPC.
+For this article, we'll just discuss the Core Server Data related to Opcodes. For a detailed overview of Opcodes and what they are used for, see this article on [[Developer:Opcodes|Understanding Opcodes]].
-Steps:
+EQ2Emulator's '''opcodes''' table consists of 4 mandatory elements:
 == table_versions ==

← Older revision		Revision as of 18:51, 8 February 2012
Line 61:		Line 61:

	== opcodes ==		== opcodes ==
		+	The simplest example of this might be when a player attacks an NPC.
		+
		+	In our '''opcodes''' table
		+
		+	Steps:
		+

@@ Line 1: / Line 1: @@
-== EQ2Emulator: Core Server Data ==
+'''EQ2Emulator: Core Server Data'''
-Server General
+The tables listed here are ones that the server cannot function without. These are considered '''Core Data''', and are maintained by the EQ2Emulator Database Project team. You can always get the latest Core Data by connecting your world to our public LoginServer and pulling down updates for the data shown below.
 ==== appearances ====
-==== commands ====
+== appearances ==
-==== opcodes ====
+Appearances are the "pointers" to the graphical representations of every spawn, item, or object in the game. Appearances consist of an '''appearance_id''' and an internal path within the client's assetlib.vpl file where that appearances graphical information can be found.
-==== table_versions ====
-==== skills ====
-==== variables ====
+Appearances come in many categories, such as Static Objects, Armor, Creatures, etc. Below are some examples:
-==== visual_states ====
+  id  appearance (path)
-==== zones ====
+  staticobjects/chandalier_iron  -- The graphic for an iron chandalier

← Older revision		Revision as of 19:57, 26 August 2011
Line 10:		Line 10:
	*rules		*rules
	*conditionals		*conditionals
		+
		+
		+	== Back to Content:Introduction ==
		+	[[Content:Introduction]]