Well... rats.
Of course it raises the question of how they got the
official server running...
Edit: Upon further inspection, when I take a look at dictionary.cpp, it\'s trying to select columns from a table named
npc_triggers, which doesn\'t exist in my copy of the database. I executed drop.sql, and it indicated that the following tables had also not been created:
- character_glyphs
- player_quests
- npc_triggers
- traits
- loot_categories
It looks like character_glyphs, player_quests and loot_categories aren\'t used anymore; the only place they\'re referenced is in drop.sql.
When I reran create_all.sql, it complained:
ERROR 1064 (42000) at line 10 in file: \'npc_triggers.sql\': You have an error in
your SQL syntax; check the manual that corresponds to your MySQL server version
for the right syntax to use near \'trigger varchar(255) ,
response_id int(10) unsigned DEFAULT \'0\' ,
prior_resp\' at line 3
When I look at npc_triggers.sql in KWrite, the word \'trigger\' is in boldface, indicating that it\'s a reserved word. If I rename that to \'_trigger\', it accepts the script and creates the table.
The traits table also isn\'t created, because it specifies an invalid default value for \'next_trait\' (it\'s specified as an unsigned integer, but given the value of -1).
When I ran create_all.sql, I saw a few more error messages, but nothing specific. I tried running mysql verbose, piping stdout and stderr to their own files, but got nothing.
(Also, just as an aside, drop.sql doesn\'t get rid of everything when it\'s run. Perhaps that\'s intentional?)
