Closed Taaboy closed 7 years ago
guids are dynamic on retail, and different maps can share same guids because they are hosted on different servers.
In case you're skeptical, you can go ahead and try it. Go to location with creatures that is quiet (no other players). Attach sniffer, kill one single creature. Observe it respawn (hopefully in the same spot). There are areas where all spots are used and it works best.
Look at sniff file, you'll see the respawned creature has a new low id.
Low ID is not used for identification at all.
1 guids are dynamic on retail, Well that might have been true but what i am seeing now and doing find entry and lows for broken isle they seem to be the same guid, but hey i am could be missing and the notepad++ could be missing some finds but @ 6gig of PKTs and had to break them down to smaller and split to opcodes and looking thru the SMSG_UPDATE_OBJECT , it is telling a different story, and if they are dynamic the entry and guid's can be easier to update and remove old from patch / expansion.
2 - different maps can share same guids.= This has map / entry/low all on the one line and example and also there is area and phase that counters that , as Legion has no fix level no more in the latest expansion area and creatures level up to your level as you go thru content.
Excluding 2 areas that are maxed lvl and alot of elites,Surmaur? and Broken Shore.So we can't have different entry's to the creature table for the variable different levels of creatures. So i feel that we should look into the change i am willing to give up the PKT missing the account sensitive data, from pre 7.2.
And atm i can't sniff as sniffer is out of date.
And Why Not use Low ID's / GUID Guid: Full: 0x203CC098806C4F40001DF700006039A1 HEX 6039A1 = 6306209
Please before going this is not true go over the example and if you want more i can gladly help their, and if i am completely wrong atleast we are looking at the data and seeing changes.
Taaboy
I wish what you were saying is true, @Taaboy. It would make everyone lives a LOT easier. But unfortunately, it is not. Low guids don't mean anything useful (to us, at least).
Regarding loot, SMSG_LOOT_RESPONSE is not equivalent to our loot tables. What SMSG_LOOT_RESPONSE tells us is that X drops Y, but doesn't say anything regarding loot modes, drop chances, loot groups, reference loots, etc.
When pursing the data (oppcodes) extracted i have come across some similar entry's with (GUID/low) that match for their spawn locations, way-points and other details, my question is why can't we use the extracted GUID for creature and object tables instead of custom / old guid's that cause a lot of problems when doing sql extraction and inserting into DB. With proper locations and all extracted GUID/low will be unique and so it doesn't clash with other people data and future proofing DB populating
By using the one that extracted there will be no double up's or wrong links to objects , all quest linked to objects will be easier to trace/track down from the extracted data instead of carrying old emu's data that is obselete with obselete creature entry's .
The other data i have been reading is the SMSG_LOOT _RESPONSE
A sample below from Creature entry:121034, http://www.wowhead.com/npc=121034/ravenous-felstalker
Second Example of multi loots http://www.wowhead.com/npc=110909/kolroz-the-everburning
My question is it possible to make a sql builder to extract that data to the creature loot table and the creature/object tables with correct extracted data.
This WPP is a powerful tool with alot of future templates and fast tracking the progression of the DB and Core. And also help with custom emu scripts for custom objects/creatures that most times cause problems.
With the possibility with the latest alter to the DB of AI for individual creature table.
Taaboy