aceindy Sherif
Number of posts : 305 Registration date : 2006-11-28
| Subject: [INFO] - Database Structure Sun Jun 10, 2007 10:42 pm | |
| - Dissaster wrote:
worldmap_info: - mapid - name says all - screenid - screen for instance loading usally the same as mapid but not always. - type - 0 - other/default , 2 - instance, 3 battleground - maxplayers - <value> - repop x,y,z,mapid - coords where playered is beeing port when he tries to join an invaild instance. - area_name - <varchar> - flags - 1 - continent, 3 - bg/instance from wow, 9 - TBC instance/bg - cooldown - time needed to pass until next time player can join instance in milisecounds
vendors: - vendorGuid - vendor id - itemGuid - item id - amount - its for stackable items like arrows food etc...
trainerspelloverride: - spellid - spell id - cost - in copper - requiredspell - required spell id - deletespell - id - requiredskill - skillid - requiredskillvalue - req skill level - reqlevel - ...name says all - requiredclass - bitwise for mixed classes (warrior - 1, pally - 2, hunter - 4, rouge - 8, priest - 16, shaman - 64, mage - 128, warlock - 256, druid -
1024,)
traniers: - creatureid - traniner id - skilllineXX - skillline id from skilline.dbc
totemspells: - spellid - totem spell id - spelltocast1 - spell that is beeing casted by totem <look for them on thotbot> - spelltocast2 - same as above - spelltocast3 - ...
quests: this db is preety easy all you need are flags here... classes warrior - 1, pally - 2, hunter - 4, rouge - 8, priest - 16, shaman - 64, mage - 128, warlock - 256, druid - 1024 - scritem - for deliver quests <itemid> - race - i dont remember all of them anyway 77 - ally, 176 for horde - flags (taken from source) QUEST_FLAG_NONE = 0, QUEST_FLAG_DELIVER = 1, QUEST_FLAG_KILL = 2, QUEST_FLAG_SPEAKTO = 4, QUEST_FLAG_REPEATABLE = 8, QUEST_FLAG_EXPLORATION = 16, QUEST_FLAG_TIMED = 32, QUEST_FLAG_REPUTATION = 128,
pvpareas: - areaid - name says all - areaname <varchar> - pvptype - 1 -horde territory, 2 -ally territory, 3 -contested
gameobject_quest_item_binding: its for go's lootable only for certain quest - gameobject_entry - goid - quest_id - <--- - item_id ... - itemcount - chance is always 100% for those go's here you can set how many quest items r droped on loot
gameobject_quest_pickup_relation this one is used for quests that require go interaction - gameobject_entry - goid - quest_id - <--- - required_count
I'll add more info later.
...
areatriggers: - AreaTriggerID - obvious crap (areatriggers.dbc) - type - 1 - instance entrance, 3 - inn, city for resting system, 4 - portal (w/o loadning screen or sth i have it for rutheran portal and wizards sanctum) - mapid - map id for tp - screen - usally same as mapid for loading screen - name <varchar100 latin> - x,y,z - coords for tp - required_honor_rank ... - required_level ... | |
|
MemoryM Addict
Number of posts : 261 Registration date : 2006-12-28
| Subject: Re: [INFO] - Database Structure Sun Jun 10, 2007 11:24 pm | |
| Antrix section is open yay Good Luck for everybody | |
|
aceindy Sherif
Number of posts : 305 Registration date : 2006-11-28
| Subject: Re: [INFO] - Database Structure Mon Jun 11, 2007 1:59 am | |
| I still dream of a master database.... | |
|
Iceman Developer
Number of posts : 462 Registration date : 2006-11-28
| Subject: Re: [INFO] - Database Structure Mon Jun 11, 2007 4:26 am | |
| yeah mister master ... :-/ somehow always soemthing got in way .. | |
|
Dimen Addict
Number of posts : 202 Registration date : 2006-11-28
| Subject: Re: [INFO] - Database Structure Mon Jun 11, 2007 10:22 pm | |
| wow antrix section, lets get to work guys and gl (I am still busy with RL, I always wonder how you guys find time, whats your secret?) | |
|
Sponsored content
| Subject: Re: [INFO] - Database Structure | |
| |
|