PDA

View Full Version : spawns/loot tables not importing with 0.2.3 database

flipper
02-12-2002, 06:21 PM
I'm unable to get Drawde's spawn/loot data into the database. I'm assuming it's due to database strutural changes in 0.2.3.

Someone with smarts please help :D
Trumpcard
02-13-2002, 12:37 AM
I didnt have any problems when i loaded them last night.

Can you be a little more descriptive than 'It doesnt work, help me?'

What are you doing, what responses are you getting back?
Drawde
02-13-2002, 04:36 AM
I think that the old version (0.4) is incompatible with the new EQEmu since the npc_type database struct has changed. There's a post on the Development forum with the new version I finished today (http://www.innersystems.com/~drawde/worlddata0.5.zip)
Trumpcard
02-13-2002, 06:44 AM
That makes sense, since as a regular part of my reloads, I drop the npc_types table, and recreate it. I was probably recreating the 2.2 version of the table, which would explain why I was not getting errors when I was importing the database...

Time for me to update my npc_types table struct.

Drawde, is that the only table struct that looked like it changed to you?
Drawde
02-13-2002, 08:56 AM
As far as I know the only change to the existing tables is the merchant_id value in the npc_types struct. Since all my DB additions seem to import and run OK after adding that value to npc_types, presumably that's all that's been added.
Lurker_005
02-13-2002, 12:38 PM
Drawed, have you noticed that you have entries in lootdrop_entries that cause errors? mysql just skips the lines, but the beeping is anoying ;)

The table key is the combined first and second column, and a few have duplicate items in seperate entries. Here are the lines that are duplicated.
INSERT INTO lootdrop_entries VALUES (1001,10119,1,0,1);
INSERT INTO lootdrop_entries VALUES (1002,15045,1,0,1);
INSERT INTO lootdrop_entries VALUES (1002,15145,1,0,1);
INSERT INTO lootdrop_entries VALUES (1002,15245,1,0,1);
INSERT INTO lootdrop_entries VALUES (1002,15345,1,0,1);
INSERT INTO lootdrop_entries VALUES (1002,15445,1,0,1);
INSERT INTO lootdrop_entries VALUES (1002,15545,1,0,1);
INSERT INTO lootdrop_entries VALUES (1002,15645,1,0,1);
INSERT INTO lootdrop_entries VALUES (1002,15745,1,0,1);
INSERT INTO lootdrop_entries VALUES (1002,15845,1,0,1);
INSERT INTO lootdrop_entries VALUES (1002,19245,1,0,1);
INSERT INTO lootdrop_entries VALUES (1002,19345,1,0,1);
INSERT INTO lootdrop_entries VALUES (1002,19445,1,0,1);
INSERT INTO lootdrop_entries VALUES (313,5021,1,1,1);
INSERT INTO lootdrop_entries VALUES (313,5022,1,1,1);
INSERT INTO lootdrop_entries VALUES (326,5013,1,1,1);
INSERT INTO lootdrop_entries VALUES (326,5021,1,1,1);
INSERT INTO lootdrop_entries VALUES (326,5022,1,1,1);
INSERT INTO lootdrop_entries VALUES (328,5021,1,1,1);
INSERT INTO lootdrop_entries VALUES (328,5022,1,1,1);
INSERT INTO lootdrop_entries VALUES (340,5021,1,1,1);
INSERT INTO lootdrop_entries VALUES (340,5022,1,1,1);
INSERT INTO lootdrop_entries VALUES (3401,5014,1,1,2);
INSERT INTO lootdrop_entries VALUES (349,12590,1,0,1);
INSERT INTO lootdrop_entries VALUES (354,5013,1,1,1);
INSERT INTO lootdrop_entries VALUES (354,5021,1,1,1);
INSERT INTO lootdrop_entries VALUES (354,5022,1,1,1);
INSERT INTO lootdrop_entries VALUES (3542,3012,1,1,1);
INSERT INTO lootdrop_entries VALUES (360,5015,1,1,1);
INSERT INTO lootdrop_entries VALUES (396,10119,1,0,1);
INSERT INTO lootdrop_entries VALUES (431,11909,1,1,1);
INSERT INTO lootdrop_entries VALUES (431,14753,1,1,1);
INSERT INTO lootdrop_entries VALUES (431,9205,1,1,1);
INSERT INTO lootdrop_entries VALUES (444,11936,1,0,1);
INSERT INTO lootdrop_entries VALUES (444,12811,1,0,1);
INSERT INTO lootdrop_entries VALUES (4614,16535,1,0,3);
INSERT INTO lootdrop_entries VALUES (63,1160,1,1,1);
INSERT INTO lootdrop_entries VALUES (69,1160,1,1,1);
INSERT INTO lootdrop_entries VALUES (75,1160,1,1,1);
INSERT INTO lootdrop_entries VALUES (81,1160,1,1,1);