[Importing Full DBC's into TC2 SQL]

As far as I know ediding dbc is illegal. But if you want learn dbc structure you can check this wiki site http://www.madx.dk/w...x.php?title=DBC

I hope I didnt break any rules.

It's funny that people use the term "Illegal". for these reasons.

Circumventing the operation of the software in any way is against the EULA that everyone clicks I accept in order to even open the wow client.

The MySQL overwrites valuses in the dbc on the fly aka. streaming the data. So in essance you are modifing the dbc files.

The extractor.exe you need to run so that your server has the dbc files to run must also unzip the MoPaq archive, and that is © blizzard.

Let's face is and not run away from the fact that we are all hacking and breaking the EULA.

With that said. Most of us feel that we bought the software so we should be able to develop things we like with it. Not for sale or any form of proffit mind you. but to experiment and learn.

Blizzard has never really cracked down too hard on any one that is not making a proffit off their work, as a matter of fact , most of the origional dev for mangos and others was leaked programming from blizzard and hackers who just wanted to see how it works.

If you are concerned with legality then I would suggest that the sysop and others actually write an MMO from scratch and dev that.

I can say this because I have many MUDS under my belt with origional code and other MUDS that I've assisted on like DiKuMUD and CircleMUD.

Anyway, thanks for the link and I allready have most of the dbc structures

Cheers!

[Importing Full DBC's into TC2 SQL]

In catalogus same systemen holds. As long as you have the "correct" dbc (or hacked dbc).then server will load it from dbc provided. Other option is only adding then cata entries. But imo that isnt easier

So it would be better to develop a server dbc editor, More advanced then the ones currently out there?

If that would make it better / faster to modify things for testing then that's what i can do

--Mifached

[Importing Full DBC's into TC2 SQL]

1) why would you put all the DBC info into SQL, if the game used DBC unless overwritten by the SQL?

(if the DBC and SQL match, then you replace Source by Source, eating time, memory and is just a waste of recourses?)

2) no its not related to "we dont touch DBC files, its plainly related to wasting recources, the TC2_SQL table is OVERWRITING the DBC values, so copying all the DBC values to the SQL makes no sense whatsoever

I understand your point, however pulling all the dbc files into the sql would help when upgrading client cores, example moving to 4.0.6 or 4.1.0.

Tho, with that said it may be a better idea to design a content creator...

Good point Bio,

-Mifached-

[Importing Full DBC's into TC2 SQL]

Ok made a new topic on this, the admins can close this one.

-- Or I'll delete it in a few days --

Thanks again,

--Mifached--