opper

Copy that. thx <div class='sqltop'>SQL</div><div class='sqlmain'>INSERT INTO creature_template_addon (`entry`, `mount`, `bytes0`, `bytes1`, `bytes2`, `emote`, `moveflags`, `auras`) VALUES('17209','0','16777472','0','4097','0','0','17327 0'); </div> <div class='sqltop'>SQL</div><div class='sqlmain'>DELETE FROM creature_addon WHERE guid = 91885; </div>or <div class='sqltop'>SQL</div><div class='sqlmain'>DELETE FROM creature_addon WHERE guid IN (SELECT guid FROM creature WHERE id = 17209); </div>if editing into the original opvp_sql_mangos.sql

in the opvp_sql_mangos.sql there's a line: <div class='sqltop'>SQL</div><div class='sqlmain'>delete from creature where id = 17209; -- delete the flight master that is spawned by the opvp </div> which has a spawn, creature guid 91885 that will be deleted by the query above but creature guid 91885 also has an entry in creature_addon (guid 91885) which I can't find anywhere else in the sql that removes it? thus get this on startup: ERROR:Creature (GUID: 91885) does not exist but has a record in `creature_addon` is that creature_addon entry suppose to remain there for some reasons or are we suppose to do this? <div class='sqltop'>SQL</div><div class='sqlmain'>DELETE FROM creature_addon WHERE guid IN (SELECT guid FROM creature WHERE id = 17209); </div>

Yes you need to write a patch for that as current revisions (since 60xx?) reads/re-calculate and set (default) reputation flags from dbc everytime a character logs in.

<div class='quotetop'>QUOTE (w12x @ Jul 7 2008, 11:53 AM) <{POST_SNAPBACK}></div> yum yum

Cheers to w12x for making yet another wish coming true