Modcraft - The community dedicated to quality WoW modding!
Wrath of the Lich King Modding => Serverside Modding => Topic started by: Reck on June 20, 2014, 02:22:30 am
-
Hi. I've recently added a new creature model to my patch, database & dbc files. However, when I attempt to spawn it, it just comes up with the syntax.
I've ran
INSERT INTO `creature_model_info` VALUES ('37138', '1', '1.5', '0', '0');
through the database, and it still doesn't work.
-
(http://achievecraft.com/cimage/i6012/Achievement+get!/Make+something+pointless!/mca.png)
- how u filed DBCs
- how you filed DB CreatureTempalte
- etc ? ...
-
can you share it maybe see if the model is working or not and did you try to morph to it first to see if the problem is from creature_model_info or not
-
Yea, sorry, I haven't "filed" a support thread/ticket for a long time.
Anyway, yes, I've done all those things, I'm positive that it's done correct, as I've looked at some pre-existing DBC files, and added them to my own as they were in those. And those dbc files were working just fine, and I am successfully able to morph into the creature.
-
Have you put your client dbc accordingly into the server dbc as well?
-
Yes, the exact same creature dbc files are in the server's dbc folder, as the ones in the patch.
-
make sure the Models or and Displayids or correct,
CreatureDisplayiinfo.dbc
CreatureModelData.dbc
CreatureDisplayInfoExtra.dbc (if playerbased type of Npc)
-
I've already checked them, and I see nothing wrong.
-
You've overlooked something. Your inability to provide more details (answering yes, I did that and that is pointless if it's something you overlooked) isn't helpful.
-
Considering it's working perfectly fine, should it not too work on my own core?
-
Not if you did something wrong, which you probably did.
-
One of the dbc files were sort of corrupt. I made a completely new one, and it worked fine.
-
Sometimes there can be error with DBC that was transfered from Server to Clinet side
for example ... with Spell.Dbc throwed into Patch ... i was getting Error instantly after Client start
-
I guess that's what happend here