DataDesigner:RAWData - Revision history

Cynnar at 22:36, 4 May 2015

2015-05-04T22:36:18Z

Cynnar at 22:34, 4 May 2015

2015-05-04T22:34:14Z

John adams at 03:22, 11 February 2012

2012-02-11T03:22:06Z

John adams at 03:17, 11 February 2012

2012-02-11T03:17:42Z

John adams at 15:53, 3 February 2012

2012-02-03T15:53:01Z

John adams: /* Populate World Database */

2012-02-03T15:24:02Z

‎Populate World Database

John adams: /* Populate World Database */

2012-02-03T15:23:18Z

‎Populate World Database

John adams at 15:19, 3 February 2012

2012-02-03T15:19:41Z

John adams at 15:55, 26 January 2012

2012-01-26T15:55:22Z

John adams: /* Populate World Database */

2012-01-26T15:53:37Z

‎Populate World Database

← Older revision		Revision as of 22:36, 4 May 2015
Line 217:		Line 217:


−	== Back to [[Content:Database_Designer \| Database Designer]	+	== Back to [[Content:Database_Designer \| Database Designer]] ==

← Older revision		Revision as of 22:34, 4 May 2015
Line 217:		Line 217:


−	== Back to ~~Content:Introduction ==~~	+	== Back to [[Content:Database_Designer \| Database Designer]
−	[[Content:~~Introduction]~~]

← Older revision		Revision as of 03:22, 11 February 2012
Line 144:		Line 144:

	==== SPECIAL NOTE ====		==== SPECIAL NOTE ====
−	The process for populating the EQ2Emulator DB Project database is much different and more complex than above. Our Content Designers should read [[~~DataDesigner~~:~~SelectiveSpawning~~\|this article]] for details on how we do things in a more controlled environment.	+	The process for populating the EQ2Emulator DB Project database is much different and more complex than above. Our Content Designers should read [[DBEditor:MigrateZone\|this article]] for details on how we do things in a more controlled environment.

@@ Line 65: / Line 65: @@
-Why 3124 Spawns?
+'''Why 3124 Spawns?'''
    Because everytime the player moved around the zone, the SOE servers send the data to the client,
    even if it is the same exact spawn in the same exact location, the client gets updates from the Server.
-Why 253 Unique?
+'''Why 253 Unique?'''
    Because out of 3124 spawn "packets", only 253 spawns were different from each other in some way to
    ensure their uniqueness
-Why 253 New?
+'''Why 253 New?'''
    Because this was the first log of Commonlands parsed, all 253 Unique spawns were also new. But, should we
    parse a second log from Commonlands, we might see 253 Unique spawns, but not likely anything "new".
@@ Line 79: / Line 79: @@
 Now, the Data Designer must open the MySQL tables for the RAW data, and evaluate if the parsed data is good, or bad.
 === Analyzing RAW Spawn Data ===
@@ Line 91: / Line 92: @@
 You will want to check all fields, and the multiple spawn-related tables, to ensure all data is this "clean".
 === Verify RAW Spawn Data ===
 After the Spawns look clean, you will need to manually verify the Zones table data matches as well. '''ALL ZONES MUST MATCH THE RAW DATA FROM SOE!''' If any zone data is mismatched, the Parser will not populate your world. You can run a query like this to determine differences in zone data:
-  SELECT * FROM eq2_rawdata.raw_zones WHERE zone_desc NOT IN (SELECT description FROM eq2dev.zones);
+ SELECT
 Where eq2_rawdata is your parser database, and eq2dev is your destination World database.
@@ Line 121: / Line 131: @@
 Once all zones descriptions are cleaned up, you can proceed to Populating the World.
 === Populate World Database ===
@@ Line 134: / Line 145: @@
 ==== SPECIAL NOTE ====
 The process for populating the EQ2Emulator DB Project database is much different and more complex than above. Our Content Designers should read [[DataDesigner:SelectiveSpawning|this article]] for details on how we do things in a more controlled environment.
 === Initial Cleanup ===
@@ Line 189: / Line 201: @@
 '''Spawn Groups'''
 A final note about Cleanup Spawns -- Since the Parser now populates spawn_location_groups (spawns that are linked in groups of 2 or more), I have omitted any spawn that is a member of a group in this "automatic" cleanup process. Spawn Group duplicates will still need to be cleaned up by hand, which will be up to the Content Designer to decide.
 === Enable RAW Zone ===
@@ Line 202: / Line 215: @@
 '''Note:''' The reason zones are "locked" is mostly to prevent Content Designers from entering zones that are not yet validated by the Data Designer. All Content Designers should honor this rule and not attempt to enter zones that are restricted.
 == Back to Content:Introduction ==
 [[Content:Introduction]]

@@ Line 88: / Line 88: @@
 Figure 1
-   [[File:Analyze1.jpg]]
+   [[File:Analyze1.jpg|300px]]
 You will want to check all fields, and the multiple spawn-related tables, to ensure all data is this "clean".
@@ Line 143: / Line 143: @@
 Figure 2
-  [[File:spawn_cleanup1.jpg]]
+  [[File:spawn_cleanup1.jpg|300px]]
 Note there is an excessive amount of "school of fish" spawns. There is no way there are 808 of then in Queen's Colony!
@@ Line 165: / Line 165: @@
 Figure 3
-  [[File:spawn_cleanup2.jpg]]
+  [[File:spawn_cleanup2.jpg|300px]]
 Because Fish spawns are not normally right on top of one another, you can start with a ''Distance Offset'' of 1, which means, if any spawn is within exactly 1' of each other, it is considered a duplicate. Check box it automatically.
@@ Line 179: / Line 179: @@
 Figure 4
-  [[File:spawn_cleanup3.jpg]]
+  [[File:spawn_cleanup3.jpg|300px]]
 The scenario shown in Figure 4 should '''not''' happen anymore in the current DB Editor, but it is always good to check through the list before clicking Delete Duplicates.
@@ Line 195: / Line 195: @@
 Figure 5
-[[File:ZoneAccess.jpg]]
+[[File:ZoneAccess.jpg|300px]]

← Older revision		Revision as of 15:24, 3 February 2012
Line 132:		Line 132:


−	~~'''~~SPECIAL NOTE~~:'''~~ The process for populating the EQ2Emulator DB Project database is much different and more complex than above. Our Content Designers should read [[DataDesigner:SelectiveSpawning\|this article]] for details on how we do things in a more controlled environment.	+	==== SPECIAL NOTE ====
		+	The process for populating the EQ2Emulator DB Project database is much different and more complex than above. Our Content Designers should read [[DataDesigner:SelectiveSpawning\|this article]] for details on how we do things in a more controlled environment.

	=== Initial Cleanup ===		=== Initial Cleanup ===

← Older revision		Revision as of 15:23, 3 February 2012
Line 130:		Line 130:

	Depending on how many spawns you are populating, this process could take a while (hours, upon hours -- do not abort!)		Depending on how many spawns you are populating, this process could take a while (hours, upon hours -- do not abort!)
		+
		+
		+	'''SPECIAL NOTE:''' The process for populating the EQ2Emulator DB Project database is much different and more complex than above. Our Content Designers should read [[DataDesigner:SelectiveSpawning\|this article]] for details on how we do things in a more controlled environment.

	=== Initial Cleanup ===		=== Initial Cleanup ===

@@ Line 122: / Line 122: @@
 Once all zones descriptions are cleaned up, you can proceed to Populating the World.
-=== Populate World Database (Spawns) ===
+=== Populate World Database ===
 Populating the destination World Database is probably the simplest task of all. Simply run the following command:
@@ Line 145: / Line 145: @@
 '''Why did I end up with 808 fish spawns?'''
-  Simply put, whenever a Collector runs passed a fish spawn in the water, the collector grabs the packet because the Server
+  Simply put, whenever a Collector runs passed a fish spawn in the water, the collector grabs the packet
- sent it to the Client (this is how it appears in your client).
+ because the Server sent it to the Client (this is how it appears in your client).
   When the Collector runs out of range of that spawn, or if the node is harvested or the spawn depops, it is removed to
- conserve memory and/or performance.
+  When the Collector runs out of range of that spawn, or if the node is harvested or the spawn depops,
   Then if the collector runs back by the same location again, the packet is re-sent and thus, re-collected.
   The same is true if you are processing 10 logs of the same zone. All different packets of the same exact node
   taken slightly different = 808 fish spawns!

← Older revision		Revision as of 15:55, 26 January 2012
Line 1:		Line 1:
−	'''EQ2Emulator: Data Designer - RAW Data Processing'''	+	'''EQ2Emulator: Data Designer - RAW Spawn Data Processing'''

		+	The Data Designer role is responsible for processing all "raw" content from packet logs, and preparing a zone for the Content Design team to enter. This document will help identify all the tasks currently performed by the Data Designer.

−	The Data Designer role is responsible for processing all "raw" content from packet logs, and preparing a zone for the Content Design team to enter. This document will help identify all the tasks currently performed by the Data Designer.

		+	Note: This article only covers raw Spawn data, and none of the many other types of data we gather from packet logs. Reason being is that this is generally a PacketParser tutorial, and most other raw data will no longer be processed by PacketParser in the future.