[HELP] mangos run err [Finish]

[brian0_]

install db

create_mysql.sql

==========================================

mangos install

----------------------------

mangos.sql

UDB_0.12.2_mangos_11792_SD2_2279.sql

403_corepatch_mangos_11793_to_11840.sql

403_updatepack_mangos.sql

404_corepatch_mangos_11841_to_11928.sql

404_updatepack_mangos.sql

3.0.9_acid.sql

mangos_scriptname_full.sql

==========================================

realmd install

-----------------------------

realmd.sql

==========================================

characters

----------------------------

characters.sql

playerbotai_characters_r1.sql

==========================================

scriptdev2

----------------------------

scriptdev2_create_database.sql

scriptdev2_create_structure_mysql.sql

scriptdev2_script_full.sql

==========================================

ERROR

2012-07-08 14:38:39 Spell (id: 33824) have SPELL_EFFECT_QUEST_COMPLETE for quest 10162 , but quest does not have SpecialFlags QUEST_SPECIAL_FLAG_EXPLORATION_OR_EVENT (2) set. Quest SpecialFlags should be corrected to enable this objective.

2012-07-08 14:38:40 Table `achievement_criteria_requirement`.`criteria_id` 12199 does not exist, ignoring.

2012-07-08 14:38:40 Table `achievement_criteria_requirement`.`criteria_id` 12200 does not exist, ignoring.

2012-07-08 14:38:40 Table `achievement_criteria_requirement`.`criteria_id` 12202 does not exist, ignoring.

2012-07-08 19:39:18 Table `gossip_scripts` has buddyEntry = 10 in command 8 for script id 7519, but this creature_template does not exist, skipping.

2012-07-08 19:39:18 Table `gossip_scripts` has buddyEntry = 10 in command 8 for script id 7520, but this creature_template does not exist, skipping.

2012-07-08 19:39:18 Table `gossip_scripts` has buddyEntry = 10 in command 8 for script id 7521, but this creature_template does not exist, skipping.

2012-07-08 19:39:18 Table `gossip_scripts` has buddyEntry = 10 in command 8 for script id 7525, but this creature_template does not exist, skipping.

2012-07-08 19:39:18 Table `gossip_scripts` has invalid data_flags 17 in command 0 for script id 9906, skipping.

2012-07-08 19:39:18 Table gossip_menu for menu 7519, text-id 9118 have script_id 7519 that does not exist in `gossip_scripts`, ignoring

2012-07-08 19:39:18 Table gossip_menu for menu 7520, text-id 9119 have script_id 7520 that does not exist in `gossip_scripts`, ignoring

2012-07-08 19:39:18 Table gossip_menu for menu 7521, text-id 9121 have script_id 7521 that does not exist in `gossip_scripts`, ignoring

2012-07-08 19:39:18 Table gossip_menu for menu 7525, text-id 9125 have script_id 7525 that does not exist in `gossip_scripts`, ignoring

2012-07-08 19:39:18 Creature (Entry: 17827) has gossip_menu_id = 7525 for nonexistent menu

2012-07-08 19:39:18 Creature (Entry: 17885) has gossip_menu_id = 7521 for nonexistent menu

2012-07-08 19:39:18 Creature (Entry: 17890) has gossip_menu_id = 7519 for nonexistent menu

2012-07-08 19:39:18 Creature (Entry: 17893) has gossip_menu_id = 7520 for nonexistent menu

2012-07-08 19:39:18 Creature (Entry: 17894) has gossip_menu_id = 7525 for nonexistent menu

2012-07-08 19:39:18 Gossip menu option (MenuId: 7520) for nonexistent menu

2012-07-08 19:39:18 Table `quest_end_scripts` has invalid data_flags 16 in command 0 for script id 411, skipping.

2012-07-08 19:39:18 Table `db_script_string` has unused string id 2000000210

2012-07-08 19:39:18 Table `db_script_string` has unused string id 2000000237

2012-07-08 19:39:18 Table `db_script_string` has unused string id 2000000272

-------------------------------------------------

I need help

plz

[TheLuda]

The messages simply indicate that your database content has some lose ends, e.g. you have references to non-existing scripts, gossip menus, etc. Perhaps a missing part in the content updates.

[Schmoozerd]

Nah, these errors are mostly caused by "recent" core changes, and UDB didn't yet scope to fix them.

In short this means that a few things that "should" work would now not work, but this is not very much.

[Unkle Nuke]

It is common for the core development to race ahead of the database. The DB guys usually catch up with their next release.

You have three choices. Leave it and wait for the DB update. Fix the errors yourself. Roll the core back to the last revision which the DB says is compatible. I usually opt for the last one with a server I use to just play the game.